Web Performance Working Group - Activity in 2026
No matches.
TR publications
-
5 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
-
Device Memory API published as a Discontinued Draft. History of Device Memory API
-
Long Tasks API published as a Discontinued Draft. History of Long Tasks API
-
Participants
-
1 participant joined.
-
Helmut Januschka (W3C Invited Experts) joined.
-
-
1 participant left.
-
Patrick Hamann (Fastly) left.
-
GitHub
w3c/long-animation-frames
-
1 issue closed.
-
Usage example near the top of the spec repeats the `observer.observe` code w3c/long-animation-frames#24, by @noamr.
-
-
5 pull requests opened.
-
Register entry type with Performance Timeline and editorial cleanups w3c/long-animation-frames#44, by @noamr.
-
Fix firstUIEventTimestamp, src quoting, paintTime duration, and detached windows w3c/long-animation-frames#43, by @noamr.
-
Specify WebIDL promise invoker naming and call-site source locations w3c/long-animation-frames#42, by @noamr.
-
Fix classic script timing and URL exposure w3c/long-animation-frames#41, by @noamr.
-
Do not record or report long animation frames for hidden documents w3c/long-animation-frames#40, by @noamr.
-
-
8 pull requests merged.
-
Register entry type with Performance Timeline and editorial cleanups w3c/long-animation-frames#44.
-
Fix firstUIEventTimestamp, src quoting, paintTime duration, and detached windows w3c/long-animation-frames#43.
-
Specify WebIDL promise invoker naming and call-site source locations w3c/long-animation-frames#42.
-
Fix a few script-related bugs w3c/long-animation-frames#41.
-
Do not record or report long animation frames for hidden documents w3c/long-animation-frames#40.
-
Add sourceLine and sourceColumn to PerformanceScriptTiming w3c/long-animation-frames#29, by @noamr.
-
Remove duplicate observer registration in initial usage example w3c/long-animation-frames#26, by @noamr.
-
Add styleDuration, layoutDuration, forcedStyleDuration, and forcedLayoutDuration w3c/long-animation-frames#30.
-
-
2 pull requests received 14 new comments.
-
Add styleDuration, layoutDuration, forcedStyleDuration, and forcedLayoutDuration w3c/long-animation-frames#30 (12 comments by @noamr, @yoavweiss)
-
Fix classic script timing and URL exposure w3c/long-animation-frames#41 (2 comments by @noamr, @yoavweiss)
-
w3c/device-memory
-
1 pull request opened.
-
Delete .github/workflows/auto-publish.yml w3c/device-memory#71, by @caribouW3.
-
-
1 pull request merged.
-
Delete .github/workflows/auto-publish.yml w3c/device-memory#71, by @yoavweiss.
-
w3c/longtasks
-
1 pull request opened.
-
Delete .github/workflows/auto-publish.yml w3c/longtasks#144, by @caribouW3.
-
-
1 pull request merged.
-
Delete .github/workflows/auto-publish.yml w3c/longtasks#144, by @yoavweiss.
-
w3c/hr-time
-
2 issues received 2 new comments.
-
Security and privacy considerations for DOMHighResTimeStamp resolution w3c/hr-time#79 (1 comment by @isma29332-coder)
-
1 pull request received 1 new comment.
-
change: Expose Performance interface to AudioWorklet w3c/hr-time#169 (1 comment by @mjwilson-google)
-
w3c/event-timing
-
2 issues opened.
-
483d73a8dda153139d3c6b9d1ac7b469af65fafb w3c/event-timing#174, by @moh5544.
-
Broken links in Event Timing API w3c/event-timing#172, by @dontcallmedom-bot.
-
-
2 issues closed.
-
483d73a8dda153139d3c6b9d1ac7b469af65fafb w3c/event-timing#174.
-
Broken links in Event Timing API w3c/event-timing#172.
-
-
2 issues received 4 new comments.
-
Add (more) WPT test coverage for synthetic events. w3c/event-timing#171 (2 comments by @adityareddy-dev)
-
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/resource-timing
-
1 issue received 1 new comment.
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/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/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)
-
TR publications
-
1 document published.
-
Largest Contentful Paint published as a Working Draft. History of Largest Contentful Paint
-
Participants
-
1 participant joined.
-
Matt Kubej (Shopify) joined.
-
-
1 participant left.
-
Dan Shappir (W3C Invited Experts) left.
-
-
1 organization left.
-
MITRE Corporation left.
-
GitHub
w3c/navigation-timing
-
1 issue opened.
-
Why is test-navigation-type-reload.html supposed to pass? w3c/navigation-timing#216, by @jdm.
-
-
1 issue closed.
-
(Re-)Expose redirectCount, redirectStart and redirectEnd for TAO opted-in cross-origin redirects w3c/navigation-timing#215.
-
-
1 issue received 1 new comment.
-
(Re-)Expose redirectCount, redirectStart and redirectEnd for TAO opted-in cross-origin redirects w3c/navigation-timing#215 (1 comment by @yoavweiss)
-
-
1 pull request received 2 new comments.
-
Add a landing attribute to PerformanceNavigationTiming w3c/navigation-timing#161 (2 comments by @nicjansma, @tunetheweb)
-
w3c/resource-timing
-
1 issue opened.
-
Clarify Resource Timing semantics for Early Hints preloads w3c/resource-timing#435, by @krzksz.
-
-
1 issue received 16 new comments.
-
Clarify Resource Timing semantics for Early Hints preloads w3c/resource-timing#435 (16 comments by @krzksz, @mmocny, @noamr, @tunetheweb, @yoavweiss)
-
-
1 pull request closed.
-
Remove index.html from gh-pages w3c/resource-timing#426.
-
-
1 pull request received 2 new comments.
w3c/requestidlecallback
-
2 pull requests received 2 new comments.
-
Intialize timeout to 0 and replace 'is present' check with comparison w3c/requestidlecallback#106 (1 comment by @mmocny)
-
w3c/largest-contentful-paint
-
1 issue opened.
-
Proposal: allow authors to identify primary visual content for LCP w3c/largest-contentful-paint#172, by @isimansur.
-
-
1 issue closed.
-
Proposal: allow authors to identify primary visual content for LCP w3c/largest-contentful-paint#172.
-
-
1 issue received 1 new comment.
-
Proposal: allow authors to identify primary visual content for LCP w3c/largest-contentful-paint#172 (1 comment by @mmocny)
-
-
1 pull request merged.
-
Editorial: Refactor algorithms to export computing the new LCP candidate w3c/largest-contentful-paint#171.
-
-
3 pull requests received 7 new comments.
-
Editorial: Refactor algorithms to export computing the new LCP candidate w3c/largest-contentful-paint#171 (4 comments by @mmocny, @shaseley, @yoavweiss)
-
w3c/long-animation-frames
-
1 issue opened.
-
Support Long Animation Frames API in Web Workers w3c/long-animation-frames#38, by @joone.
-
w3c/reporting
-
1 pull request received 2 new comments.
-
Change Report and ReportBody interfaces to dicts. w3c/reporting#258 (2 comments by @hamishwillee, @mmocny)
-
w3c/hr-time
-
1 pull request closed.
-
2 pull requests received 4 new comments.
-
change: Update 'relative high resolution time' to use the principal realm. w3c/hr-time#168 (2 comments by @mmocny, @Ms2ger)
-
w3c/performance-timeline
-
1 pull request received 1 new comment.
-
Remove PerformanceEntry.id and rephrase id generation. w3c/performance-timeline#219 (1 comment by @mmocny)
-
w3c/beacon
-
1 issue received 5 new comments.
-
Option to request beacon be compressed w3c/beacon#72 (5 comments by @andydavies, @annevk, @yoavweiss)
-
Lifecycle
-
1 charter extension.
-
Charter extended until 1 August 2026.
-
GitHub
w3c/navigation-timing
-
1 issue opened.
-
(Re-)Expose redirectCount, redirectStart and redirectEnd for TAO opted-in cross-origin redirects w3c/navigation-timing#215, by @yoavweiss.
-
-
2 issues received 7 new comments.
-
(Re-)Expose redirectCount, redirectStart and redirectEnd for TAO opted-in cross-origin redirects w3c/navigation-timing#215 (6 comments by @achristensen07, @annevk, @noamr, @yoavweiss)
-
-
1 pull request received 1 new comment.
-
Add a landing attribute to PerformanceNavigationTiming w3c/navigation-timing#161 (1 comment by @mmocny)
-
w3c/requestidlecallback
-
1 pull request received 2 new comments.
-
Editorial: Use the HTML spec's timers infrastructure for `timeout` w3c/requestidlecallback#98 (2 comments by @mmocny, @shaseley)
-
w3c/largest-contentful-paint
-
2 pull requests opened.
-
Editorial: Refactor algorithms to export computing the new LCP candidate w3c/largest-contentful-paint#171, by @shaseley.
-
Correct indentation for setting paintedImages as newCandidate w3c/largest-contentful-paint#170, by @shubhamg13.
-
-
1 pull request merged.
-
Correct indentation for setting paintedImages as newCandidate w3c/largest-contentful-paint#170.
-
-
3 pull requests received 11 new comments.
-
Editorial: Refactor algorithms to export computing the new LCP candidate w3c/largest-contentful-paint#171 (7 comments by @mmocny, @shaseley)
-
Correct indentation for setting paintedImages as newCandidate w3c/largest-contentful-paint#170 (3 comments by @shubhamg13, @w3cbot, @yoavweiss)
-
w3c/resource-timing
-
1 issue opened.
-
Should we be exposing same-origin redirects? w3c/resource-timing#434, by @yoavweiss.
-
-
3 pull requests closed.
-
Add http method to ResourceTiming interface w3c/resource-timing#375.
-
Explainer for Content-type w3c/resource-timing#361.
-
Add a note about "stalled" or "blocked" time w3c/resource-timing#169.
-
-
4 pull requests received 4 new comments.
-
Conform 'current time' definition to the current hr-time spec w3c/resource-timing#236 (1 comment by @mmocny)
w3c/performance-timeline
-
1 issue received 1 new comment.
-
API shape for monitoring new navigation-like entries such as App History, BFCache, etc w3c/performance-timeline#182 (1 comment by @nicjansma)
-
-
1 pull request closed.
-
Add support for accessing cross-frame entries. w3c/performance-timeline#202.
-
-
1 pull request received 1 new comment.
w3c/reporting
-
3 pull requests closed.
-
Add note about capability URLs w3c/reporting#162.
-
Limit report delivery per page w3c/reporting#142.
-
Add note about custom metadata and spam prevention w3c/reporting#85.
-
-
2 pull requests received 2 new comments.
w3c/paint-timing
-
1 issue opened.
-
1 issue received 5 new comments.
-
"Mark Paint Time" starts before paint starts, but ends after paint ends, without clear specification of this timing. w3c/paint-timing#126 (5 comments by @mmocny, @shaseley, @yoavweiss)
-
w3c/user-timing
-
1 issue closed.
-
The PerformanceMark Constructor steps can be simplified. w3c/user-timing#128.
-
-
1 issue received 1 new comment.
-
The PerformanceMark Constructor steps can be simplified. w3c/user-timing#128 (1 comment by @shubhamg13)
-
-
1 pull request closed.
-
1 pull request received 2 new comments.
-
Resuse the existing definition of `convert a mark to a timestamp` for `PerformanceMark` w3c/user-timing#129 (2 comments by @nicjansma, @shubhamg13)
-
w3c/web-performance
-
1 pull request received 1 new comment.
-
feat: improve bikeshed-conversion skill score 84% → 97% w3c/web-performance#69 (1 comment by @yogesh-tessl)
-
w3c/network-error-logging
-
1 issue opened.
-
Proposal: Introduce Fine-Grained Sampling Controls for 4xx HTTP Status Codes in NEL w3c/network-error-logging#208, by @zenmiao7.
-
Participants
-
1 chair appointed.
-
Nic Jansma became a chair.
-
GitHub
w3c/web-performance
-
1 issue opened.
-
Discussing a potential performance.isProfiling() method w3c/web-performance#68, by @rubennorte.
-
-
1 issue received 5 new comments.
-
Discussing a potential performance.isProfiling() method w3c/web-performance#68 (5 comments by @mmocny, @rubennorte, @yoavweiss)
-
-
1 pull request opened.
-
feat: improve bikeshed-conversion skill score 84% → 97% w3c/web-performance#69, by @yogesh-tessl.
-
w3c/user-timing
-
2 issues closed.
-
3 issues received 4 new comments.
-
Add entry to the performance entry buffer in `mark()` and `measure()` seems excessive w3c/user-timing#126 (2 comments by @mmocny, @shubhamg13)
-
Allow marks and measures to be shown in developer tooling without adding it to the performance timeline w3c/user-timing#68 (1 comment by @mmocny)
-
Add a non-normative format for the `detail` param that allows developers to customize the presentation of timings in devtools w3c/user-timing#111 (1 comment by @mmocny)
-
w3c/resource-timing
-
1 issue opened.
-
Relation to the `PerformanceEntry` interface missing w3c/resource-timing#433, by @shubhamg13.
-
-
1 issue received 3 new comments.
-
Relation to the `PerformanceEntry` interface missing w3c/resource-timing#433 (3 comments by @mmocny, @shubhamg13)
-
w3c/paint-timing
-
1 issue opened.
-
Evaluate changing Mark Paint Timing to flushPaintTimings actually at paint time. w3c/paint-timing#125, by @mmocny.
-
-
1 issue received 2 new comments.
-
Evaluate changing Mark Paint Timing to flushPaintTimings actually at paint time. w3c/paint-timing#125 (2 comments by @mmocny, @noamr)
-
w3c/device-memory
-
1 issue received 1 new comment.
w3c/navigation-timing
-
2 issues received 4 new comments.
-
Using navigationStart as a baseline may expose cross-origin timing information w3c/navigation-timing#160 (3 comments by @mmocny, @noamr, @yoavweiss)
-
[Editorial] The referencing of "not restored reasons" is broken w3c/navigation-timing#208 (1 comment by @gabrielmamede)
-
w3c/largest-contentful-paint
-
2 issues received 2 new comments.
-
What is the behavior when paints emit from inside the Shadow DOM? w3c/largest-contentful-paint#152 (1 comment by @mmocny)
-
w3c/performance-timeline
-
1 issue closed.
-
Consider changing sorted ordering of performance entry to be based on "end time" rather than startTime. w3c/performance-timeline#224.
-
-
2 issues received 2 new comments.
-
API shape for monitoring new navigation-like entries such as App History, BFCache, etc w3c/performance-timeline#182 (1 comment by @mmocny)
-
Consider changing sorted ordering of performance entry to be based on "end time" rather than startTime. w3c/performance-timeline#224 (1 comment by @mmocny)
-
w3c/network-error-logging
-
1 issue received 1 new comment.
w3c/event-timing
-
2 issues opened.
-
Evaluate replacing `keyCode` with `code`. w3c/event-timing#170, by @mmocny.
-
`pointerdown` event should always be reported in its own paint, without buffering. w3c/event-timing#169, by @mmocny.
-
-
2 issues received 3 new comments.
-
`pointerdown` event should always be reported in its own paint, without buffering. w3c/event-timing#169 (2 comments by @mmocny)
-
-
1 pull request received 17 new comments.
-
Progress towards #164: Major spec refactoring & clean up InteractionId assignment. w3c/event-timing#165 (17 comments by @canova, @francovs, @mmocny)
-
w3c/element-timing
-
1 issue closed.
-
Support Element Timing on Containers w3c/element-timing#79.
-
-
1 issue received 1 new comment.
TR publications
-
4 documents published.
-
Resource Timing published as a Candidate Recommendation Draft. History of Resource Timing
-
Largest Contentful Paint published as a Working Draft. History of Largest Contentful Paint
-
Server Timing published as a Working Draft. History of Server Timing
-
Long Animation Frames API published as a First Public Working Draft. History of Long Animation Frames API
-
Participants
-
1 chair stepped down.
-
Nic Jansma stepped down as a chair.
-
-
1 participant joined.
-
Nic Jansma (W3C Invited Experts) joined.
-
-
2 participants left.
-
Yury Leonychev (Rakuten Group, Inc.) left.
-
Nic Jansma (W3C Invited Experts) left.
-
GitHub
w3c/network-error-logging
-
1 issue opened.
-
Question on CR Timeline w3c/network-error-logging#207, by @yks0000.
-
-
1 issue closed.
-
Broken links in Network Error Logging w3c/network-error-logging#205.
-
-
1 pull request opened.
-
Fix a broken link w3c/network-error-logging#206, by @guohuideng2024.
-
-
1 pull request merged.
-
Fix a broken link w3c/network-error-logging#206.
-
-
1 pull request received 3 new comments.
w3c/server-timing
-
1 issue closed.
-
Broken links in Server Timing w3c/server-timing#103.
-
-
1 pull request opened.
-
fix a broken link. w3c/server-timing#105, by @guohuideng2024.
-
-
1 pull request merged.
-
fix a broken link. w3c/server-timing#105.
-
-
1 pull request received 1 new comment.
w3c/reporting
-
1 issue opened.
-
Add specification for the `default` reporting endpoint w3c/reporting#291, by @hamishwillee.
-
w3c/user-timing
-
2 issues opened.
-
The PerformanceMark Constructor steps can be simplified. w3c/user-timing#128, by @shubhamg13.
-
Add entry to the performance entry buffer in `mark()` and `measure()` seems excessive w3c/user-timing#126, by @shubhamg13.
-
-
1 issue received 1 new comment.
-
Add entry to the performance entry buffer in `mark()` and `measure()` seems excessive w3c/user-timing#126 (1 comment by @shubhamg13)
-
-
2 pull requests opened.
-
Resuse the existing definition of `convert a mark to a timestamp` for `PerformanceMark` w3c/user-timing#129, by @shubhamg13.
-
Make a note of new location of the explainer w3c/user-timing#127, by @guohuideng2024.
-
-
1 pull request merged.
-
Make a note of new location of the explainer w3c/user-timing#127.
-
w3c/resource-timing
-
1 pull request opened.
-
Add `dfn-id` to algorithms w3c/resource-timing#432, by @shubhamg13.
-
-
1 pull request merged.
-
Add `dfn-id` to algorithms w3c/resource-timing#432.
-
-
1 pull request received 1 new comment.
w3c/largest-contentful-paint
-
1 issue closed.
-
Non-human visible size changes should not impact LCP w3c/largest-contentful-paint#158.
-
-
3 issues received 17 new comments.
-
Consider exposing LCP `duration` value relative to navigation-specific time origin. w3c/largest-contentful-paint#159 (2 comments by @mmocny, @mormubis)
-
Background purposed images is not properly defined in the spec w3c/largest-contentful-paint#28 (2 comments by @mmocny)
-
1 pull request merged.
-
Add minimal change threshold w3c/largest-contentful-paint#160.
-
-
1 pull request received 3 new comments.
w3c/long-animation-frames
-
1 issue opened.
-
Specify how LoAF behaves for tasks without a `Document` w3c/long-animation-frames#36, by @noamr.
-
-
1 issue closed.
-
Specify how LoAF behaves for tasks without a `Document` w3c/long-animation-frames#36.
-
-
1 issue received 7 new comments.
-
Specify how LoAF behaves for tasks without a `Document` w3c/long-animation-frames#36 (7 comments by @mmocny, @noamr, @smaug----, @yoavweiss)
-
-
1 pull request opened.
-
Treat "fire an event" and script execution blocks as "tasks" if outside document-associated task w3c/long-animation-frames#37, by @noamr.
-
-
1 pull request merged.
-
Treat "fire an event" and script execution blocks as "tasks" if outside document-associated task w3c/long-animation-frames#37.
-
-
1 pull request received 13 new comments.
-
Treat "fire an event" and script execution blocks as "tasks" if outside document-associated task w3c/long-animation-frames#37 (13 comments by @noamr, @yoavweiss)
-
w3c/device-memory
-
1 issue reopened.
-
Apple's WebKit team's feedback w3c/device-memory#24, by @tunetheweb.
-
-
1 issue received 13 new comments.
-
Apple's WebKit team's feedback w3c/device-memory#24 (13 comments by @annevk, @jyasskin, @marcoscaceres, @tunetheweb)
-
w3c/event-timing
-
1 issue closed.
-
1 issue received 2 new comments.
-
"first-input" dispatch logic in the spec doesn't match the tests and the Chromium implementation w3c/event-timing#142 (2 comments by @canova, @mmocny)
-
-
1 pull request received 3 new comments.
-
Progress towards #164: Major spec refactoring & clean up InteractionId assignment. w3c/event-timing#165 (3 comments by @mmocny)
-
w3c/longtasks
-
2 issues closed.
-
Add support for Web Workers w3c/longtasks#142.
-
Provide an option for overriding the 50ms threshold w3c/longtasks#14.
-
-
2 issues received 2 new comments.
TR publications
-
14 documents published.
-
Resource Timing published as a Candidate Recommendation Draft. History of Resource Timing
-
User Timing published as a Candidate Recommendation Draft. History of User Timing
-
Device Memory API published twice as a Working Draft. History of Device Memory API
-
Largest Contentful Paint published 3 times as a Working Draft. History of Largest Contentful Paint
-
High Resolution Time published twice as a Working Draft. History of High Resolution Time
-
Paint Timing published as a Working Draft. History of Paint Timing
-
Event Timing API published as a Working Draft. History of Event Timing API
-
Long Tasks API published as a Working Draft. History of Long Tasks API
-
Server Timing published twice as a Working Draft. History of Server Timing
-
GitHub
w3c/device-memory
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Small tweaks to the README w3c/device-memory#59, by @tunetheweb.
-
Fix WebIDL definitions w3c/device-memory#58, by @tidoust.
-
-
3 pull requests merged.
-
Small tweaks to the README w3c/device-memory#59.
-
Fix WebIDL definitions w3c/device-memory#58.
-
Reorganise the spec w3c/device-memory#57.
-
-
1 pull request received 11 new comments.
-
Reorganise the spec w3c/device-memory#57 (11 comments by @domfarolino, @guohuideng2024, @miketaylr, @tunetheweb)
-
w3c/performance-timeline
-
2 issues opened.
-
Add PerformanceObserver option for "per-paint" reporting. w3c/performance-timeline#228, by @mmocny.
-
Consider changing sorted ordering of performance entry to be based on "end time" rather than startTime. w3c/performance-timeline#224, by @mmocny.
-
-
2 issues received 5 new comments.
-
Consider changing sorted ordering of performance entry to be based on "end time" rather than startTime. w3c/performance-timeline#224 (4 comments by @mmocny, @nicjansma)
-
Add PerformanceObserver option for "per-paint" reporting. w3c/performance-timeline#228 (1 comment by @mmocny)
-
-
3 pull requests opened.
-
Fix broken anchor references w3c/performance-timeline#227, by @yoavweiss.
-
Fix `supportedentrytypes` anchor w3c/performance-timeline#226, by @tunetheweb.
-
Fix up attribute dfns w3c/performance-timeline#225, by @yoavweiss.
-
-
3 pull requests merged.
-
Fix broken anchor references w3c/performance-timeline#227.
-
Fix `supportedentrytypes` anchor w3c/performance-timeline#226.
-
Fix up attribute dfns w3c/performance-timeline#225.
-
-
1 pull request received 1 new comment.
w3c/largest-contentful-paint
-
4 issues opened.
-
Define element "intersectionRect" to include "clientContentRect" as per "effective visual size" w3c/largest-contentful-paint#168, by @mmocny.
-
Sequence for Sub Step for Step 8 for `4.3. Determine the effective visual size of an element` broken w3c/largest-contentful-paint#167, by @shubhamg13.
-
Broken links in Largest Contentful Paint w3c/largest-contentful-paint#165, by @dontcallmedom-bot.
-
LCP does not exclude whitespace-only text elements like FCP w3c/largest-contentful-paint#163, by @shaseley.
-
-
4 issues closed.
-
Sequence for Sub Step for Step 8 for `4.3. Determine the effective visual size of an element` broken w3c/largest-contentful-paint#167.
-
Broken links in Largest Contentful Paint w3c/largest-contentful-paint#165.
-
For backward/forward navigation, should LCP be updated for JS API w3c/largest-contentful-paint#156.
-
LargestContentfulPaint has both `renderTime` and `paintTime` via the mixin. Are they different? w3c/largest-contentful-paint#145.
-
-
7 issues received 11 new comments.
-
Sequence for Sub Step for Step 8 for `4.3. Determine the effective visual size of an element` broken w3c/largest-contentful-paint#167 (3 comments by @shubhamg13, @tunetheweb)
-
LCP does not exclude whitespace-only text elements like FCP w3c/largest-contentful-paint#163 (2 comments by @mmocny, @shaseley)
-
Non-human visible size changes should not impact LCP w3c/largest-contentful-paint#158 (2 comments by @mmocny, @yoavweiss)
-
Define element "intersectionRect" to include "clientContentRect" as per "effective visual size" w3c/largest-contentful-paint#168 (1 comment by @mmocny)
-
Broken links in Largest Contentful Paint w3c/largest-contentful-paint#165 (1 comment by @tunetheweb)
-
LargestContentfulPaint has both `renderTime` and `paintTime` via the mixin. Are they different? w3c/largest-contentful-paint#145 (1 comment by @mmocny)
-
Consider exposing LCP `duration` value relative to navigation-specific time origin. w3c/largest-contentful-paint#159 (1 comment by @mmocny)
-
-
6 pull requests opened.
-
Fix Sequence for Sub-Steps for Step 8 of `4.3. Determine the effectie visual size of an element` w3c/largest-contentful-paint#169, by @shubhamg13.
-
Update limiations for bfcache and soft navs w3c/largest-contentful-paint#166, by @tunetheweb.
-
[lcp]: Fix spec wording to make renderTime non-optional. w3c/largest-contentful-paint#164, by @mmocny.
-
Fix the CI build w3c/largest-contentful-paint#162, by @yoavweiss.
-
Change editors and affiliation w3c/largest-contentful-paint#161, by @yoavweiss.
-
Add minimal change threshold w3c/largest-contentful-paint#160, by @yoavweiss.
-
-
5 pull requests merged.
-
Fix Sequence for Sub-Steps for Step 8 of `4.3. Determine the effectie visual size of an element` w3c/largest-contentful-paint#169.
-
Update limiations for bfcache and soft navs w3c/largest-contentful-paint#166.
-
[lcp]: Fix spec wording to make renderTime non-optional. w3c/largest-contentful-paint#164.
-
Change editors and affiliation w3c/largest-contentful-paint#161.
-
Fix the CI build w3c/largest-contentful-paint#162.
-
-
3 pull requests received 32 new comments.
-
Update limiations for bfcache and soft navs w3c/largest-contentful-paint#166 (16 comments by @mmocny, @tunetheweb, @yoavweiss)
-
Add minimal change threshold w3c/largest-contentful-paint#160 (15 comments by @Bas-moz, @mmocny, @tunetheweb, @yoavweiss)
-
Fix Sequence for Sub-Steps for Step 8 of `4.3. Determine the effectie visual size of an element` w3c/largest-contentful-paint#169 (1 comment by @w3cbot)
-
w3c/event-timing
-
2 issues opened.
-
Broken links in Event Timing API w3c/event-timing#167, by @dontcallmedom-bot.
-
2 issues closed.
-
Broken links in Event Timing API w3c/event-timing#167.
-
-
4 issues received 11 new comments.
-
Consider removing `duration` rounding to 8ms after shipping PaintTimingMixin (which marks coarsened paint/presentationTime) w3c/event-timing#168 (6 comments by @mmocny, @tunetheweb)
-
Spec "fallbackTime" for cases where we don't need to wait for paint (modal dialog, visibilitychange...) w3c/event-timing#154 (2 comments by @canova, @mmocny)
-
-
2 pull requests opened.
-
Update from api.csswg.org/bikeshed to spec-generator w3c/event-timing#166, by @kfranqueiro.
-
Progress towards #164: Major spec refactoring & clean up InteractionId assignment. w3c/event-timing#165, by @mmocny.
-
-
1 pull request merged.
-
Update from api.csswg.org/bikeshed to spec-generator w3c/event-timing#166.
-
-
2 pull requests received 31 new comments.
-
Progress towards #164: Major spec refactoring & clean up InteractionId assignment. w3c/event-timing#165 (27 comments by @mmocny, @shaseley)
-
Update from api.csswg.org/bikeshed to spec-generator w3c/event-timing#166 (4 comments by @kfranqueiro, @mmocny, @w3cbot)
-
w3c/paint-timing
-
2 issues opened.
-
`first-paint` marking steps are missing important details. Should it consider paintable or not. w3c/paint-timing#122, by @shubhamg13.
-
Consider adding `renderTime` to `PaintTimingMixin` interface w3c/paint-timing#121, by @mmocny.
-
-
2 issues closed.
-
LargestContentfulPaint and PaintTiming are separate specs w3c/paint-timing#43.
-
Add attribution information about what triggers paint w3c/paint-timing#44.
-
-
3 issues received 11 new comments.
-
Consider adding `renderTime` to `PaintTimingMixin` interface w3c/paint-timing#121 (8 comments by @Bas-moz, @mmocny, @noamr)
-
`first-paint` marking steps are missing important details. Should it consider paintable or not. w3c/paint-timing#122 (2 comments by @noamr, @shubhamg13)
-
LargestContentfulPaint and PaintTiming are separate specs w3c/paint-timing#43 (1 comment by @mmocny)
-
-
2 pull requests opened.
-
Fix broken anchor references w3c/paint-timing#124, by @yoavweiss.
-
Add steps for reporting `first-paint` w3c/paint-timing#123, by @shubhamg13.
-
-
1 pull request merged.
-
Fix broken anchor references w3c/paint-timing#124.
-
-
1 pull request received 13 new comments.
-
Add steps for reporting `first-paint` w3c/paint-timing#123 (13 comments by @caribouW3, @noamr, @shubhamg13, @w3cbot, @yoavweiss)
-
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 @martinalderson)
-
-
2 pull requests opened.
-
Fix up broken links in Fetch and HTML w3c/resource-timing#431, by @yoavweiss.
-
Add 'attribute' keyword to IDL attribute dfns for Bikeshed w3c/resource-timing#430, by @yoavweiss.
-
-
1 pull request merged.
-
Fix up broken links in Fetch and HTML w3c/resource-timing#431.
-
w3c/long-animation-frames
-
1 issue received 2 new comments.
-
[LoAF] Allow for annotations for long animation frame to further help debugging w3c/long-animation-frames#3 (2 comments by @guohuideng2024, @kurtextrem)
-
-
3 pull requests opened.
-
Replace Makefile with spec-prod and fix bikeshed link errors w3c/long-animation-frames#35, by @yoavweiss.
-
Replace Makefile with spec-prod and fix bikeshed link errors w3c/long-animation-frames#34, by @yoavweiss.
-
Fix Bikeshed API endpoint in Makefile w3c/long-animation-frames#33, by @yoavweiss.
-
-
2 pull requests merged.
-
Replace Makefile with spec-prod and fix bikeshed link errors w3c/long-animation-frames#34.
-
Replace Makefile with spec-prod and fix bikeshed link errors w3c/long-animation-frames#35.
-
-
1 pull request closed.
-
Fix Bikeshed API endpoint in Makefile w3c/long-animation-frames#33.
-
-
3 pull requests received 4 new comments.
-
Replace Makefile with spec-prod and fix bikeshed link errors w3c/long-animation-frames#35 (2 comments by @noamr, @yoavweiss)
-
Add styleDuration, layoutDuration, forcedStyleDuration, and forcedLayoutDuration w3c/long-animation-frames#30 (1 comment by @yoavweiss)
-
w3c/user-timing
-
9 pull requests opened.
-
Remove "conditions" w3c/user-timing#125, by @guohuideng2024.
-
Sync conditional-tracing-explainer.md from gh-pages branch w3c/user-timing#124, by @guohuideng2024.
-
Move to an approach without "track" objects. w3c/user-timing#123, by @guohuideng2024.
-
Better describe `attachTrack` w3c/user-timing#122, by @guohuideng2024.
-
Revert "PerformanceObserver.attachTrack() remains." w3c/user-timing#121, by @guohuideng2024.
-
PerformanceObserver.attachTrack() remains. w3c/user-timing#120, by @guohuideng2024.
-
Add 'attribute' keyword to IDL attribute dfns for Bikeshed w3c/user-timing#119, by @yoavweiss.
-
Conversion to bikeshed w3c/user-timing#118, by @yoavweiss.
-
Conditional tracing w3c/user-timing#117, by @yoavweiss.
-
-
9 pull requests merged.
-
Remove "conditions" w3c/user-timing#125.
-
Sync conditional-tracing-explainer.md from gh-pages branch w3c/user-timing#124.
-
Move to an approach without "track" objects. w3c/user-timing#123.
-
Better describe `attachTrack` w3c/user-timing#122.
-
Revert "PerformanceObserver.attachTrack() remains." w3c/user-timing#121.
-
PerformanceObserver.attachTrack() remains. w3c/user-timing#120.
-
Conversion to bikeshed w3c/user-timing#118.
-
Conditional tracing w3c/user-timing#117.
-
A formal and more detailed explainer on the "conditional tracing" w3c/user-timing#116.
-
-
5 pull requests received 7 new comments.
-
Move to an approach without "track" objects. w3c/user-timing#123 (2 comments by @guohuideng2024, @tunetheweb)
-
Sync conditional-tracing-explainer.md from gh-pages branch w3c/user-timing#124 (1 comment by @guohuideng2024)
-
A formal and more detailed explainer on the "conditional tracing" w3c/user-timing#116 (1 comment by @noamr)
-
w3c/hr-time
-
3 pull requests opened.
-
Fix broken anchor references w3c/hr-time#175, by @yoavweiss.
-
Add 'attribute' keyword to IDL attribute dfns for Bikeshed w3c/hr-time#174, by @yoavweiss.
-
Reinstate ids of anchors used by other specifications w3c/hr-time#173, by @dontcallmedom.
-
-
2 pull requests merged.
-
Fix broken anchor references w3c/hr-time#175.
-
Reinstate ids of anchors used by other specifications w3c/hr-time#173.
-
w3c/element-timing
-
1 issue opened.
-
Broken links in Element Timing API w3c/element-timing#90, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken links in Element Timing API w3c/element-timing#90.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Update from api.csswg.org/bikeshed to spec-generator w3c/element-timing#89, by @kfranqueiro.
-
-
1 pull request merged.
-
Update from api.csswg.org/bikeshed to spec-generator w3c/element-timing#89.
-
-
1 pull request received 2 new comments.
-
Update from api.csswg.org/bikeshed to spec-generator w3c/element-timing#89 (2 comments by @mmocny, @w3cbot)
-
w3c/web-performance
-
1 pull request received 4 new comments.
-
Web Performance Working Group 2026 Charter w3c/web-performance#67 (4 comments by @caribouW3, @marcoscaceres, @yoavweiss)
-
w3c/longtasks
-
1 pull request opened.
-
Update from api.csswg.org/bikeshed to spec-generator w3c/longtasks#143, by @kfranqueiro.
-
-
1 pull request merged.
-
Update from api.csswg.org/bikeshed to spec-generator w3c/longtasks#143.
-
-
1 pull request received 2 new comments.
-
Update from api.csswg.org/bikeshed to spec-generator w3c/longtasks#143 (2 comments by @w3cbot, @yoavweiss)
-
w3c/server-timing
-
1 issue opened.
-
Broken links in Server Timing w3c/server-timing#103, by @dontcallmedom-bot.
-
-
2 pull requests opened.
-
Add 'attribute' keyword to IDL attribute dfns for Bikeshed w3c/server-timing#104, by @yoavweiss.
-
Change editors w3c/server-timing#102, by @yoavweiss.
-
-
2 pull requests merged.
-
Add 'attribute' keyword to IDL attribute dfns for Bikeshed w3c/server-timing#104.
-
Change editors w3c/server-timing#102.
-
-
1 pull request received 2 new comments.
-
Add 'attribute' keyword to IDL attribute dfns for Bikeshed w3c/server-timing#104 (2 comments by @mmocny, @yoavweiss)
-
w3c/navigation-timing
-
1 pull request opened.
-
Add 'attribute' keyword to IDL attribute dfns for Bikeshed w3c/navigation-timing#214, by @yoavweiss.
-
w3c/beacon
-
1 pull request opened.
-
Bikeshed conversion w3c/beacon#86, by @yoavweiss.
-
-
1 pull request merged.
-
Bikeshed conversion w3c/beacon#86.
-
w3c/network-error-logging
-
1 issue opened.
-
Broken links in Network Error Logging w3c/network-error-logging#205, by @dontcallmedom-bot.
-
-
2 issues closed.
-
Broken links in Network Error Logging w3c/network-error-logging#199.
-
include_subdomains description missing DNS-only limitation w3c/network-error-logging#201.
-
-
2 pull requests merged.
-
Fix broken links. w3c/network-error-logging#204.
-
include_subdomains limited to dns phase w3c/network-error-logging#203.
-
-
1 pull request received 1 new comment.
w3c/reporting
-
1 issue received 2 new comments.
TR publications
-
7 documents published.
-
User Timing published as a Candidate Recommendation Draft. History of User Timing
-
Resource Timing published as a Candidate Recommendation Draft. History of Resource 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
-
Event Timing API published twice as a Working Draft. History of Event Timing API
-
Largest Contentful Paint published as a Working Draft. History of Largest Contentful Paint
-
Participants
-
1 participant joined.
-
Marko Ilic (Microsoft Corporation) joined.
-
-
1 participant left.
-
Caio Gondim (The New York Times) left.
-
GitHub
w3c/network-error-logging
-
2 pull requests opened.
-
Fix broken links. w3c/network-error-logging#204, by @guohuideng2024.
-
include_subdomains limited to dns phase w3c/network-error-logging#203, by @yoavweiss.
-
-
1 pull request closed.
-
spec: Add note about DNS-only limitation for include_subdomains w3c/network-error-logging#200.
-
-
1 pull request received 2 new comments.
w3c/event-timing
-
2 issues opened.
-
Broken links in Event Timing API w3c/event-timing#161, by @dontcallmedom-bot.
-
1 issue closed.
-
Broken links in Event Timing API w3c/event-timing#161.
-
-
1 issue reopened.
-
Add `targetSelector` attribute to Event Timing API (for cases where target is detached) w3c/event-timing#126, by @jasonwilliams.
-
-
3 issues received 9 new comments.
-
Add `targetSelector` attribute to Event Timing API (for cases where target is detached) w3c/event-timing#126 (5 comments by @jasonwilliams, @mmocny, @tunetheweb)
-
Clean up Event Timing spec, especially InteractionID assignment steps, and add WPT for Event Timing reporting order. w3c/event-timing#164 (3 comments by @francovs, @mmocny)
-
"first-input" dispatch logic in the spec doesn't match the tests and the Chromium implementation w3c/event-timing#142 (1 comment by @mmocny)
-
-
2 pull requests opened.
-
Cleanup typos and references (before larger spec change). w3c/event-timing#163, by @mmocny.
-
Fix #161: Fix broken links for Event types. w3c/event-timing#162, by @mmocny.
-
-
2 pull requests merged.
-
Cleanup typos and references (before larger spec change). w3c/event-timing#163.
-
Fix #161: Fix broken links for Event types. w3c/event-timing#162.
-
-
2 pull requests received 2 new comments.
-
Cleanup typos and references (before larger spec change). w3c/event-timing#163 (1 comment by @mmocny)
-
w3c/web-performance
-
1 pull request opened.
-
Web Performance Working Group 2026 Charter w3c/web-performance#67, by @nicjansma.
-
-
1 pull request received 7 new comments.
-
Web Performance Working Group 2026 Charter w3c/web-performance#67 (7 comments by @caribouW3, @nicjansma, @tunetheweb, @yoavweiss)
-
w3c/performance-timeline
-
1 issue opened.
-
Not you guys too… w3c/performance-timeline#222, by @6h5pfs5xrm-spec.
-
-
2 issues closed.
-
Not you guys too… w3c/performance-timeline#222.
-
Copyrights w3c/performance-timeline#221.
-
-
2 issues received 2 new comments.
-
PerformanceEntry.id is shadowed by PerformanceElementTiming.id. w3c/performance-timeline#218 (1 comment by @mmocny)
-
-
1 pull request opened.
-
Change editor w3c/performance-timeline#223, by @yoavweiss.
-
-
1 pull request merged.
-
Change editor w3c/performance-timeline#223.
-
-
1 pull request received 1 new comment.
-
Remove PerformanceEntry.id and rephrase id generation. w3c/performance-timeline#219 (1 comment by @mmocny)
-
w3c/user-timing
-
1 pull request opened.
-
A formal and more detailed explainer on the "conditional tracing" w3c/user-timing#116, by @guohuideng2024.
-
-
1 pull request merged.
-
Create conditional-tracing-explainer.md w3c/user-timing#112.
-
-
2 pull requests received 2 new comments.
-
A formal and more detailed explainer on the "conditional tracing" w3c/user-timing#116 (1 comment by @noamr)
-
w3c/device-memory
-
1 pull request received 13 new comments.
-
Reorganise the spec w3c/device-memory#57 (13 comments by @domfarolino, @guohuideng2024, @tunetheweb)
-
w3c/navigation-timing
-
3 pull requests opened.
-
Missing quote w3c/navigation-timing#213, by @yoavweiss.
-
Fix up autopublish w3c/navigation-timing#212, by @yoavweiss.
-
Change affiliations w3c/navigation-timing#211, by @yoavweiss.
-
-
3 pull requests merged.
-
Missing quote w3c/navigation-timing#213.
-
Fix up autopublish w3c/navigation-timing#212.
-
Change affiliations w3c/navigation-timing#211.
-
w3c/hr-time
-
1 pull request opened.
-
Change affiliation w3c/hr-time#172, by @yoavweiss.
-
-
1 pull request merged.
-
Change affiliation w3c/hr-time#172.
-
-
1 pull request received 2 new comments.
-
change: Expose Performance interface to AudioWorklet w3c/hr-time#169 (2 comments by @mjwilson-google, @padenot)
-
w3c/largest-contentful-paint
-
2 issues opened.
-
Consider exposing LCP `duration` value relative to navigation-specific time origin. w3c/largest-contentful-paint#159, by @mmocny.
-
Non-human visible size changes should not impact LCP w3c/largest-contentful-paint#158, by @yoavweiss.
-
-
1 issue closed.
-
Report LCP algorithm should limit to single largest paint candidate, per report w3c/largest-contentful-paint#135.
-
-
2 issues received 4 new comments.
-
Non-human visible size changes should not impact LCP w3c/largest-contentful-paint#158 (3 comments by @mmocny, @smfr, @tunetheweb)
-
Consider exposing LCP `duration` value relative to navigation-specific time origin. w3c/largest-contentful-paint#159 (1 comment by @mmocny)
-
-
1 pull request merged.
-
Fix #135: report one candidate per paint w3c/largest-contentful-paint#154.
-
-
1 pull request received 10 new comments.
-
Fix #135: report one candidate per paint w3c/largest-contentful-paint#154 (10 comments by @Bas-moz, @mmocny, @shaseley, @smfr, @tunetheweb)
-
w3c/long-animation-frames
-
2 issues opened.
-
Consider making task-end-time "no visible effect" easier to integrate with for other specs. w3c/long-animation-frames#32, by @mmocny.
-
Editorial: links included as plaintext in heading. w3c/long-animation-frames#31, by @mmocny.
-
w3c/requestidlecallback
-
1 issue opened.
-
Use default of 0 for timeout option w3c/requestidlecallback#105, by @annevk.
-
-
1 issue received 2 new comments.
-
2 pull requests opened.
-
[DO NOT MERGE] Test w3c/requestidlecallback#107, by @shaseley.
-
Intialize timeout to 0 and replace 'is present' check with comparison w3c/requestidlecallback#106, by @shaseley.
-
-
1 pull request closed.
-
[DO NOT MERGE] Test w3c/requestidlecallback#107.
-
-
1 pull request received 3 new comments.
-
Intialize timeout to 0 and replace 'is present' check with comparison w3c/requestidlecallback#106 (3 comments by @dontcallmedom, @shaseley, @yoavweiss)
-
w3c/reporting
-
1 issue opened.
-
Potentially trustworthy URL's for responses not adhered to w3c/reporting#290, by @theIDinside.
-
-
1 issue closed.
-
Potentially trustworthy URL's for responses not adhered to w3c/reporting#290.
-
-
3 issues received 10 new comments.
-
Potentially trustworthy URL's for responses not adhered to w3c/reporting#290 (8 comments by @farre, @theIDinside, @TimvdLippe)
-
w3c/resource-timing
-
1 issue opened.
-
PerformanceResourceTiming transferSize getter steps does not consider cross origin resources. w3c/resource-timing#423, by @colelao.
-
-
1 issue closed.
-
PerformanceResourceTiming transferSize getter steps does not consider cross origin resources. w3c/resource-timing#423.
-
-
1 issue received 12 new comments.
-
PerformanceResourceTiming transferSize getter steps does not consider cross origin resources. w3c/resource-timing#423 (12 comments by @annevk, @colelao, @nicjansma, @noamr)
-
-
6 pull requests opened.
-
Add gh-pages as a target w3c/resource-timing#429, by @yoavweiss.
-
Fix up publishing w3c/resource-timing#428, by @yoavweiss.
-
Change affiliation w3c/resource-timing#427, by @yoavweiss.
-
Remove index.html from gh-pages w3c/resource-timing#426, by @yoavweiss.
-
Remove spurious </p> w3c/resource-timing#425, by @noamr.
-
Clarify informative notes about cross-origin w3c/resource-timing#424, by @noamr.
-
-
5 pull requests merged.
-
Add gh-pages as a target w3c/resource-timing#429.
-
Fix up publishing w3c/resource-timing#428.
-
Change affiliation w3c/resource-timing#427.
-
Remove spurious </p> w3c/resource-timing#425.
-
Clarify informative notes about cross-origin w3c/resource-timing#424.
-
-
1 pull request received 15 new comments.
-
Clarify informative notes about cross-origin w3c/resource-timing#424 (15 comments by @annevk, @noamr, @yoavweiss)
-
TR publications
-
2 documents published.
-
Device Memory API published as a Working Draft. History of Device Memory API
-
Paint Timing published as a Working Draft. History of Paint Timing
-
Participants
-
1 participant joined.
-
Thomas BERTET (Datadog) joined.
-
-
1 participant left.
-
Ben Michel (Datadog) left.
-
GitHub
w3c/long-animation-frames
-
1 issue received 1 new comment.
-
Feature Request: Summary of script-attribution for non-attributed scripts w3c/long-animation-frames#23 (1 comment by @mmocny)
-
-
1 pull request opened.
-
Add styleDuration, layoutDuration, forcedStyleDuration, and forcedLayoutDuration w3c/long-animation-frames#30, by @yoavweiss.
-
-
1 pull request received 4 new comments.
-
Add styleDuration, layoutDuration, forcedStyleDuration, and forcedLayoutDuration w3c/long-animation-frames#30 (4 comments by @emilio, @noamr, @yoavweiss)
-
w3c/device-memory
-
1 issue closed.
-
Update recommended upper and lower bounds w3c/device-memory#50.
-
-
1 issue received 8 new comments.
-
Update recommended upper and lower bounds w3c/device-memory#50 (8 comments by @guohuideng2024, @mmocny, @tomayac, @tunetheweb)
-
-
2 pull requests opened.
-
Reorganise the spec w3c/device-memory#57, by @tunetheweb.
-
Emphasize the bounds can be dymanically adjusted by implements w3c/device-memory#53, by @guohuideng2024.
-
-
1 pull request merged.
-
Emphasize the bounds can be dymanically adjusted by implements w3c/device-memory#53.
-
-
1 pull request received 3 new comments.
-
Emphasize the bounds can be dymanically adjusted by implements w3c/device-memory#53 (3 comments by @guohuideng2024, @tunetheweb)
-
w3c/network-error-logging
-
2 issues opened.
-
include_subdomains description missing DNS-only limitation w3c/network-error-logging#201, by @Slonser.
-
Broken links in Network Error Logging w3c/network-error-logging#199, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Remove "request headers" and "response headers" from NEL spec w3c/network-error-logging#194.
-
-
1 issue received 1 new comment.
-
Remove "request headers" and "response headers" from NEL spec w3c/network-error-logging#194 (1 comment by @yoavweiss)
-
-
5 pull requests opened.
-
Update w3c.json w3c/network-error-logging#202, by @caribouW3.
-
spec: Add note about DNS-only limitation for include_subdomains w3c/network-error-logging#200, by @Slonser.
-
Change editors w3c/network-error-logging#198, by @yoavweiss.
-
Move to bikeshed w3c/network-error-logging#197, by @yoavweiss.
-
Convert to bikeshed w3c/network-error-logging#196, by @yoavweiss.
-
-
4 pull requests merged.
-
Update w3c.json w3c/network-error-logging#202.
-
Change editors w3c/network-error-logging#198.
-
Move to bikeshed w3c/network-error-logging#197.
-
Remove "request headers" and "response headers" from NEL w3c/network-error-logging#195.
-
-
1 pull request closed.
-
Convert to bikeshed w3c/network-error-logging#196.
-
w3c/performance-timeline
-
1 issue opened.
-
Copyrights w3c/performance-timeline#221, by @ahfuckit.
-
w3c/largest-contentful-paint
-
1 issue opened.
-
The fact that LCP entries are buffered is not mentioned in the spec w3c/largest-contentful-paint#157, by @tunetheweb.
-
-
1 issue received 3 new comments.
-
The fact that LCP entries are buffered is not mentioned in the spec w3c/largest-contentful-paint#157 (3 comments by @mmocny, @tunetheweb)
-
w3c/web-performance
-
1 issue reopened.
-
Consider deprecating primer w3c/web-performance#54, by @tunetheweb.
-
-
1 issue received 3 new comments.
-
Consider deprecating primer w3c/web-performance#54 (3 comments by @Bas-moz, @tunetheweb, @yoavweiss)
-
w3c/paint-timing
-
1 pull request opened.
-
Fix typos w3c/paint-timing#120, by @tunetheweb.
-
-
1 pull request merged.
-
Fix typos w3c/paint-timing#120.
-
w3c/reporting
-
1 pull request merged.
-
Remove optional URL from generate a report w3c/reporting#289.
-
-
2 pull requests received 4 new comments.
-
Remove optional URL from generate a report w3c/reporting#289 (3 comments by @domfarolino, @yoavweiss)
-