Web Performance Working Group - Activity
No matches.
TR publications
-
3 documents published.
-
Paint Timing published twice as a Working Draft. History of Paint Timing
-
Event Timing API published as a Working Draft. History of Event Timing API
-
Participants
-
1 participant joined.
-
Helmut Januschka (W3C Invited Experts) joined.
-
GitHub
w3c/long-animation-frames
-
1 pull request received 12 new comments.
-
Add styleDuration, layoutDuration, forcedStyleDuration, and forcedLayoutDuration w3c/long-animation-frames#30 (12 comments by @noamr, @yoavweiss)
-
w3c/paint-timing
-
1 issue opened.
-
Attribute images painted by pseudo-elements to their originating element w3c/paint-timing#132, by @jdapena.
-
-
1 issue received 1 new comment.
-
Attribute images painted by pseudo-elements to their originating element w3c/paint-timing#132 (1 comment by @jdapena)
-
-
2 pull requests opened.
-
Add `paintable` definition to iframe w3c/paint-timing#133, by @shubhamg13.
-
Add existing `contentful-image` reference w3c/paint-timing#131, by @shubhamg13.
-
-
2 pull requests merged.
-
Add `paintable` definition to iframe w3c/paint-timing#133.
-
Add existing `contentful-image` reference w3c/paint-timing#131.
-
-
2 pull requests received 7 new comments.
-
Add `paintable` definition to iframe w3c/paint-timing#133 (5 comments by @noamr, @shubhamg13, @w3cbot)
-
w3c/event-timing
-
1 issue opened.
-
Broken links in Event Timing API w3c/event-timing#172, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken links in Event Timing API w3c/event-timing#172.
-
-
1 issue received 2 new comments.
-
Proposal: DOM event identifier which can map to EventTimingPerformance entry w3c/event-timing#108 (2 comments by @adityareddy-dev, @mmocny)
-
-
1 pull request opened.
-
Fix #172: Fix broken links to Pointer Events w3c/event-timing#173, by @yoavweiss.
-
-
1 pull request merged.
-
Fix #172: Fix broken links to Pointer Events w3c/event-timing#173.
-
w3c/performance-timeline
-
1 issue received 1 new comment.
-
Should a new PerformanceObserver with buffered:true require buffered entries synchronously? w3c/performance-timeline#231 (1 comment by @nhelfman)
-
w3c/navigation-timing
-
2 issues closed.
-
Clarify how PerformanceTiming.responseStart relates to Early Hint responses w3c/navigation-timing#181.
-
Extend Navigation Timing API to include back/forward cache NotRestoredReasons w3c/navigation-timing#171.
-
-
2 issues received 2 new comments.
-
Clarify how PerformanceTiming.responseStart relates to Early Hint responses w3c/navigation-timing#181 (1 comment by @tunetheweb)
-
Extend Navigation Timing API to include back/forward cache NotRestoredReasons w3c/navigation-timing#171 (1 comment by @tunetheweb)
-
w3c/element-timing
-
1 issue received 1 new comment.
w3c/hr-time
-
1 pull request received 1 new comment.
-
change: Expose Performance interface to AudioWorklet w3c/hr-time#169 (1 comment by @mjwilson-google)
-
w3c/largest-contentful-paint
-
1 issue closed.
-
`<img>` in `timing-eligible` says nothing about `contentful` w3c/largest-contentful-paint#177.
-
-
1 issue received 2 new comments.
-
What is the behavior when paints emit from inside the Shadow DOM? w3c/largest-contentful-paint#152 (2 comments by @fbuecklers, @mmocny)
-
w3c/web-performance
-
1 pull request opened.
-
Fix up index w3c/web-performance#75, by @yoavweiss.
-
-
1 pull request merged.
-
Fix up index w3c/web-performance#75.
-
TR publications
-
4 documents published.
-
Resource Timing published as a Candidate Recommendation Draft. History of Resource Timing
-
Paint Timing published as a Working Draft. History of Paint Timing
-
High Resolution Time published as a Working Draft. History of High Resolution Time
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Participants
-
4 participants joined.
-
Viktoria Zlatinova (Microsoft Corporation) joined.
-
Jennifer Strickland (W3C Invited Experts) joined.
-
Dan Gayle (Shopify) joined.
-
Cameron Brown (Google LLC) joined.
-
-
5 participants left.
-
Jennifer Strickland (W3C Invited Experts) left.
-
Abin Paul (W3C Invited Experts) left.
-
Peter Perlepes (W3C Invited Experts) left.
-
Michelle Vu (W3C Invited Experts) left.
-
Tim Kadlec (W3C Invited Experts) left.
-
GitHub
w3c/largest-contentful-paint
-
1 issue opened.
-
`<img>` in `timing-eligible` says nothing about `contentful` w3c/largest-contentful-paint#177, by @shubhamg13.
-
-
1 issue closed.
-
The definition of `effective visual size` is circular w3c/largest-contentful-paint#143.
-
-
5 issues received 12 new comments.
-
Usage of textNode is overloaded w3c/largest-contentful-paint#175 (5 comments by @mmocny, @shaseley, @shubhamg13)
-
`<img>` in `timing-eligible` says nothing about `contentful` w3c/largest-contentful-paint#177 (3 comments by @mmocny, @shubhamg13)
-
The definition of `effective visual size` is circular w3c/largest-contentful-paint#143 (2 comments by @mmocny, @shubhamg13)
-
Background purposed images is not properly defined in the spec w3c/largest-contentful-paint#28 (1 comment by @shubhamg13)
-
Define element "intersectionRect" to include "clientContentRect" as per "effective visual size" w3c/largest-contentful-paint#168 (1 comment by @shubhamg13)
-
-
2 pull requests opened.
-
Add a note for full page background image w3c/largest-contentful-paint#178, by @shubhamg13.
-
Exempt video elements from the low-content image heuristic w3c/largest-contentful-paint#176, by @hjanuschka.
-
-
3 pull requests received 8 new comments.
-
Exempt video elements from the low-content image heuristic w3c/largest-contentful-paint#176 (3 comments by @mmocny, @shaseley)
-
Generalize `request` variable name w3c/largest-contentful-paint#173 (3 comments by @mmocny, @shubhamg13)
-
Add a note for full page background image w3c/largest-contentful-paint#178 (2 comments by @shubhamg13, @w3cbot)
-
w3c/hr-time
-
1 pull request merged.
-
Add 'attribute' keyword to IDL attribute dfns for Bikeshed w3c/hr-time#174.
-
-
1 pull request received 1 new comment.
-
change: Expose Performance interface to AudioWorklet w3c/hr-time#169 (1 comment by @mjwilson-google)
-
w3c/web-performance
-
1 issue received 1 new comment.
-
https://www.w3.org/webperf/ homepage looks unstylized w3c/web-performance#71 (1 comment by @nicjansma)
-
-
2 pull requests opened.
-
Add WebPerfWG minutes for September 24th, 2026 w3c/web-performance#74, by @nicjansma.
-
Add WebPerfWG minutes for September 10th, 2026 w3c/web-performance#73, by @nicjansma.
-
-
2 pull requests merged.
-
Add WebPerfWG minutes for September 24th, 2026 w3c/web-performance#74.
-
Add WebPerfWG minutes for September 10th, 2026 w3c/web-performance#73.
-
w3c/performance-timeline
-
1 issue opened.
-
Should a new PerformanceObserver with buffered:true require buffered entries synchronously? w3c/performance-timeline#231, by @mmocny.
-
-
1 issue received 5 new comments.
-
Should a new PerformanceObserver with buffered:true require buffered entries synchronously? w3c/performance-timeline#231 (5 comments by @mmocny)
-
w3c/paint-timing
-
1 issue opened.
-
contentful text doesn't need to check opacity w3c/paint-timing#129, by @shubhamg13.
-
-
1 issue received 4 new comments.
-
contentful text doesn't need to check opacity w3c/paint-timing#129 (4 comments by @jasonwilliams, @noamr, @shubhamg13)
-
-
2 pull requests opened.
-
Add `border-image-source` to `contentful` list w3c/paint-timing#128, by @shubhamg13.
-
1 pull request merged.
-
Add `border-image-source` to `contentful` list w3c/paint-timing#128.
-
-
2 pull requests received 5 new comments.
-
Omit opacity for `text node` in contentful definition as it is already included in paintable definition w3c/paint-timing#130 (3 comments by @jasonwilliams, @shubhamg13, @w3cbot)
-
Add `border-image-source` to `contentful` list w3c/paint-timing#128 (2 comments by @shubhamg13, @w3cbot)
-
w3c/reporting
-
2 pull requests opened.
-
Close <section> element in network-reporting.bs w3c/reporting#293, by @apasel422.
-
Recommend sf-token for structured field endpoint parameters w3c/reporting#292, by @apasel422.
-
-
2 pull requests merged.
-
Recommend sf-token for structured field endpoint parameters w3c/reporting#292.
-
Close <section> element in network-reporting.bs w3c/reporting#293.
-
-
1 pull request received 4 new comments.
-
Recommend sf-token for structured field endpoint parameters w3c/reporting#292 (4 comments by @apasel422, @clelland)
-
w3c/timing-entrytypes-registry
-
1 issue opened.
-
Make this a Living Spec w3c/timing-entrytypes-registry#26, by @tunetheweb.
-
-
1 issue closed.
-
Missing `visibility-state` entry type w3c/timing-entrytypes-registry#18.
-
-
5 pull requests opened.
-
Add Soft Nav entries w3c/timing-entrytypes-registry#25, by @tunetheweb.
-
Add visibility-state w3c/timing-entrytypes-registry#24, by @tunetheweb.
-
Misc spec edits w3c/timing-entrytypes-registry#23, by @tunetheweb.
-
Remove index.html w3c/timing-entrytypes-registry#22, by @tunetheweb.
-
Add Container Timing w3c/timing-entrytypes-registry#21, by @tunetheweb.
-
-
6 pull requests merged.
-
Add Soft Nav entries w3c/timing-entrytypes-registry#25.
-
Misc spec edits w3c/timing-entrytypes-registry#23.
-
Add visibility-state w3c/timing-entrytypes-registry#24.
-
Remove index.html w3c/timing-entrytypes-registry#22.
-
Add Container Timing w3c/timing-entrytypes-registry#21.
-
Convert to Bikeshed w3c/timing-entrytypes-registry#20.
-
-
1 pull request closed.
-
Export `availableFromTimeline` w3c/timing-entrytypes-registry#2.
-
-
3 pull requests received 5 new comments.
w3c/event-timing
-
1 issue opened.
-
Add (more) WPT test coverage for synthetic events. w3c/event-timing#171, by @mmocny.
-
w3c/resource-timing
-
1 pull request opened.
-
Add Relation to `PerformanceEntry` w3c/resource-timing#436, by @shubhamg13.
-
-
1 pull request merged.
-
Add 'attribute' keyword to IDL attribute dfns for Bikeshed w3c/resource-timing#430.
-
-
1 pull request received 2 new comments.
w3c/navigation-timing
-
2 issues received 6 new comments.
-
Using navigationStart as a baseline may expose cross-origin timing information w3c/navigation-timing#160 (3 comments by @noamr, @yoavweiss)
-
Interaction between cross-document view transitions and Navigation Timing w3c/navigation-timing#217 (3 comments by @mmocny, @noamr, @yoavweiss)
-
-
1 pull request opened.
-
Rotate the `obsolete` watermark w3c/navigation-timing#219, by @shubhamg13.
-
-
2 pull requests merged.
-
Add 'attribute' keyword to IDL attribute dfns for Bikeshed w3c/navigation-timing#214.
-
Switch to newer versions of obsoleted HTTP RFCs w3c/navigation-timing#218.
-
-
1 pull request received 2 new comments.
w3c/long-animation-frames
-
1 pull request opened.
-
Fix references to window w3c/long-animation-frames#39, by @noamr.
-
-
1 pull request merged.
-
Fix references to window w3c/long-animation-frames#39.
-
w3c/element-timing
-
1 pull request opened.
-
Fix broken `PaintTimingMixin/paint timing` reference w3c/element-timing#91, by @shubhamg13.
-
-
1 pull request merged.
-
Fix broken `PaintTimingMixin/paint timing` reference w3c/element-timing#91.
-
-
1 pull request received 2 new comments.
-
Fix broken `PaintTimingMixin/paint timing` reference w3c/element-timing#91 (2 comments by @shubhamg13, @w3cbot)
-
w3c/user-timing
-
1 pull request merged.
-
Add 'attribute' keyword to IDL attribute dfns for Bikeshed w3c/user-timing#119.
-
Lifecycle
-
1 charter started.
-
Chartered until 1 August 2028.
-
TR publications
-
1 document published.
-
Largest Contentful Paint published as a Working Draft. History of Largest Contentful Paint
-
GitHub
w3c/timing-entrytypes-registry
-
1 issue closed.
-
Broken references in Timing Entry Names Registry w3c/timing-entrytypes-registry#17.
-
-
1 pull request opened.
-
Convert to Bikeshed w3c/timing-entrytypes-registry#20, by @tunetheweb.
-
-
1 pull request merged.
-
Correct LOAF spec link w3c/timing-entrytypes-registry#19.
-
-
1 pull request received 2 new comments.
w3c/largest-contentful-paint
-
1 issue opened.
-
Usage of textNode is overloaded w3c/largest-contentful-paint#175, by @shubhamg13.
-
-
1 issue received 3 new comments.
-
Usage of textNode is overloaded w3c/largest-contentful-paint#175 (3 comments by @clelland, @shubhamg13)
-
-
2 pull requests opened.
-
Drop hardcoded anchor for "visual viewport" to fix link w3c/largest-contentful-paint#174, by @tidoust.
-
Generalize `request` variable name w3c/largest-contentful-paint#173, by @shubhamg13.
-
-
1 pull request merged.
-
Drop hardcoded anchor for "visual viewport" to fix link w3c/largest-contentful-paint#174.
-
-
2 pull requests received 4 new comments.
-
Generalize `request` variable name w3c/largest-contentful-paint#173 (3 comments by @shubhamg13, @w3cbot)
-
Drop hardcoded anchor for "visual viewport" to fix link w3c/largest-contentful-paint#174 (1 comment by @mmocny)
-
w3c/performance-timeline
-
2 issues opened.
-
Soft Nav API performance entries does not specify a buffer size w3c/performance-timeline#230, by @tunetheweb.
-
`visibility-state` performance entries does not specify a buffer size w3c/performance-timeline#229, by @tunetheweb.
-
-
2 issues closed.
-
Soft Nav API performance entries does not specify a buffer size w3c/performance-timeline#230.
-
`visibility-state` performance entries does not specify a buffer size w3c/performance-timeline#229.
-
-
2 issues received 3 new comments.
-
`visibility-state` performance entries does not specify a buffer size w3c/performance-timeline#229 (2 comments by @noamr, @tunetheweb)
-
Soft Nav API performance entries does not specify a buffer size w3c/performance-timeline#230 (1 comment by @tunetheweb)
-
w3c/web-performance
-
1 issue opened.
-
https://www.w3.org/webperf/ homepage looks unstylized w3c/web-performance#71, by @nicjansma.
-
-
6 issues closed.
-
Outdated links in header of working group home page w3c/web-performance#61.
-
Consider deprecating primer w3c/web-performance#54.
-
API to detect bad performance/dropped frames/jank w3c/web-performance#39.
-
Cleanup specs w3c/web-performance#35.
-
Performance considerations for spec developers? w3c/web-performance#28.
-
Consider performance tools aimed at the ESM JavaScript loading w3c/web-performance#40.
-
-
6 issues received 12 new comments.
-
https://www.w3.org/webperf/ homepage looks unstylized w3c/web-performance#71 (6 comments by @caribouW3, @mmocny, @nicjansma, @tunetheweb)
-
Convert old Respec specs to Bikeshed w3c/web-performance#25 (2 comments by @marcoscaceres, @nicjansma)
-
-
2 pull requests opened.
-
Add WebPerfWG minutes for August 27th, 2026 w3c/web-performance#72, by @nicjansma.
-
Add WebPerfWG minutes for August 13th, 2026 w3c/web-performance#70, by @nicjansma.
-
-
3 pull requests merged.
-
Add WebPerfWG minutes for August 27th, 2026 w3c/web-performance#72.
-
Add WebPerfWG minutes for August 13th, 2026 w3c/web-performance#70.
-
Web Performance Working Group 2026 Charter w3c/web-performance#67.
-
-
1 pull request received 1 new comment.
w3c/hr-time
-
1 issue opened.
-
morning w3c/hr-time#176, by @meipaulyboy513-ship-it.
-
-
1 issue closed.
-
morning w3c/hr-time#176.
-
-
1 issue received 2 new comments.
-
1 pull request received 1 new comment.
-
change: Expose Performance interface to AudioWorklet w3c/hr-time#169 (1 comment by @mjwilson-google)
-
w3c/device-memory
-
2 issues opened.
-
Exposing the amount of RAM is an irresovlable privacy threat w3c/device-memory#62, by @baybal.
-
Letting developers to know how much RAM they can waste is a bad incentive w3c/device-memory#61, by @baybal.
-
-
2 issues received 16 new comments.
-
Exposing the amount of RAM is an irresovlable privacy threat w3c/device-memory#62 (10 comments by @baybal, @guohuideng2024, @rniwa, @tunetheweb)
-
Letting developers to know how much RAM they can waste is a bad incentive w3c/device-memory#61 (6 comments by @anniesullie, @baybal, @pmeenan, @tunetheweb)
-
w3c/navigation-timing
-
1 issue opened.
-
Interaction between cross-document view transitions and Navigation Timing w3c/navigation-timing#217, by @yoavweiss.
-
-
2 issues closed.
-
[Editorial] The referencing of "not restored reasons" is broken w3c/navigation-timing#208.
-
Why is test-navigation-type-reload.html supposed to pass? w3c/navigation-timing#216.
-
-
3 issues received 4 new comments.
-
Why is test-navigation-type-reload.html supposed to pass? w3c/navigation-timing#216 (2 comments by @jdm, @nicjansma)
-
[Editorial] The referencing of "not restored reasons" is broken w3c/navigation-timing#208 (1 comment by @shubhamg13)
-
The "Obsolete" label is rendered in a seemingly random place w3c/navigation-timing#149 (1 comment by @shubhamg13)
-
-
1 pull request opened.
-
Switch to newer versions of obsoleted HTTP RFCs w3c/navigation-timing#218, by @tidoust.
-
-
1 pull request received 1 new comment.
-
Add a landing attribute to PerformanceNavigationTiming w3c/navigation-timing#161 (1 comment by @mmocny)
-
w3c/paint-timing
-
1 pull request opened.
-
Highlight the terminoligies aka make paintedImages and paintedTextNodes explicit w3c/paint-timing#127, by @shubhamg13.
-
-
1 pull request closed.
-
Highlight the terminoligies aka make paintedImages and paintedTextNodes explicit w3c/paint-timing#127.
-
-
1 pull request received 4 new comments.
-
Highlight the terminoligies aka make paintedImages and paintedTextNodes explicit w3c/paint-timing#127 (4 comments by @noamr, @shubhamg13, @w3cbot)
-
w3c/long-animation-frames
-
1 issue received 1 new comment.
w3c/resource-timing
-
1 issue received 1 new comment.
-
Resource initiator information to enable creation of dependency trees w3c/resource-timing#263 (1 comment by @guohuideng2024)
-