Web Performance Working Group - Activity in 2025
No matches.
TR publications
-
4 documents published.
-
Resource Timing published twice as a Candidate Recommendation Draft. History of Resource Timing
-
Device Memory API published as a Working Draft. History of Device Memory API
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Participants
-
2 participants joined.
-
Jennifer Strickland (W3C Invited Experts) joined.
-
Sam Maddock (Salesforce) joined.
-
GitHub
w3c/hr-time
-
1 issue received 1 new comment.
w3c/reporting
-
1 pull request opened.
-
Remove optional URL from generate a report w3c/reporting#289, by @domfarolino.
-
w3c/network-error-logging
-
1 issue opened.
-
Remove "request headers" and "response headers" from NEL spec w3c/network-error-logging#194, by @guohuideng2024.
-
-
1 issue received 2 new comments.
-
Distribute NEL policies with DNS w3c/network-error-logging#173 (2 comments by @SulemanAhmadd, @valenting)
-
-
1 pull request opened.
-
Remove "request headers" and "response headers" from NEL w3c/network-error-logging#195, by @guohuideng2024.
-
w3c/largest-contentful-paint
-
1 issue opened.
-
For backward/forward navigation, should LCP be updated for JS API w3c/largest-contentful-paint#156, by @shubhamg13.
-
-
2 issues received 3 new comments.
-
For backward/forward navigation, should LCP be updated for JS API w3c/largest-contentful-paint#156 (2 comments by @shubhamg13, @tunetheweb)
-
LargestContentfulPaint has both `renderTime` and `paintTime` via the mixin. Are they different? w3c/largest-contentful-paint#145 (1 comment by @mmocny)
-
w3c/device-memory
-
1 issue closed.
-
Expose CPU clock speed and GPU info in the same manner as device memory w3c/device-memory#15.
-
-
1 issue received 1 new comment.
-
Expose CPU clock speed and GPU info in the same manner as device memory w3c/device-memory#15 (1 comment by @tunetheweb)
-
-
2 pull requests opened.
-
Review spec w3c/device-memory#52, by @tunetheweb.
-
Update header name to Sec-CH-Device-Memory w3c/device-memory#51, by @tunetheweb.
-
-
2 pull requests merged.
-
Review spec w3c/device-memory#52.
-
Update header name to Sec-CH-Device-Memory w3c/device-memory#51.
-
-
2 pull requests received 5 new comments.
-
Update header name to Sec-CH-Device-Memory w3c/device-memory#51 (2 comments by @miketaylr, @tunetheweb)
w3c/resource-timing
-
1 pull request opened.
-
Update w3c.json w3c/resource-timing#422, by @caribouW3.
-
-
2 pull requests merged.
-
Update w3c.json w3c/resource-timing#422.
-
Add SW static routing API timing information to resource timing w3c/resource-timing#415.
-
-
2 pull requests received 3 new comments.
-
Add SW static routing API timing information to resource timing w3c/resource-timing#415 (2 comments by @quasi-mod)
-
w3c/resource-timing#421 (1 comment by @w3cbot)
-
w3c/navigation-timing
-
1 issue closed.
-
Add `confidence` field to PerformanceNavigationTiming w3c/navigation-timing#202.
-
-
1 pull request merged.
-
Add `confidence` field to PerformanceNavigationTiming w3c/navigation-timing#210.
-
-
1 pull request received 11 new comments.
-
Add `confidence` field to PerformanceNavigationTiming w3c/navigation-timing#210 (11 comments by @mwjacksonmsft, @yoavweiss)
-
Lifecycle
-
1 charter extension.
-
Charter extended until 1 June 2026.
-
TR publications
-
2 documents published.
-
Paint Timing published as a Working Draft. History of Paint Timing
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Past meetings
Participants
-
4 participants joined.
-
Sangwhan Moon (Google LLC) joined.
-
Ari Chivukula (Google LLC) joined.
-
Takashi Toyoshima (Google LLC) joined.
-
Benjamin Kelly (Meta) joined.
-
GitHub
w3c/resource-timing
-
1 issue opened.
-
Render-blocking status of a CSS preload which is subsequently requested while in flight w3c/resource-timing#420, by @tunetheweb.
-
-
2 issues received 5 new comments.
-
Resource initiator information to enable creation of dependency trees w3c/resource-timing#263 (3 comments by @guohuideng2024, @martinalderson, @mmocny)
-
Render-blocking status of a CSS preload which is subsequently requested while in flight w3c/resource-timing#420 (2 comments by @tunetheweb, @yoavweiss)
-
-
1 pull request received 3 new comments.
-
Add SW static routing API timing information to resource timing w3c/resource-timing#415 (3 comments by @quasi-mod, @yoavweiss)
-
w3c/navigation-timing
-
2 issues received 6 new comments.
-
Extending the NavigationTimingType w3c/navigation-timing#184 (4 comments by @gilbertococchi, @tunetheweb)
-
Using navigationStart as a baseline may expose cross-origin timing information w3c/navigation-timing#160 (2 comments by @noamr, @RByers)
-
-
2 pull requests opened.
-
Add `confidence` field to PerformanceNavigationTiming w3c/navigation-timing#210, by @mwjacksonmsft.
-
Remove references to browsing context w3c/navigation-timing#209, by @tunetheweb.
-
-
1 pull request merged.
-
Remove references to browsing context w3c/navigation-timing#209.
-
-
1 pull request received 3 new comments.
-
Add `confidence` field to PerformanceNavigationTiming w3c/navigation-timing#210 (3 comments by @yoavweiss)
-
w3c/network-error-logging
-
1 issue opened.
-
Does NEL work in Electron applications w3c/network-error-logging#193, by @zenmiao7.
-
-
1 issue closed.
-
Does NEL work in Electron applications w3c/network-error-logging#193.
-
-
3 issues received 5 new comments.
-
Clarify NEL's purpose, and a question w3c/network-error-logging#192 (3 comments by @Sora2455, @Synchro)
-
w3c/largest-contentful-paint
-
2 issues opened.
-
A page should be able to express that it is no longer interested in LCP w3c/largest-contentful-paint#153, by @smfr.
-
What is the behavior when paints emit from inside the Shadow DOM? w3c/largest-contentful-paint#152, by @jasonwilliams.
-
-
5 issues received 9 new comments.
-
What is `size` for a repeating background image? w3c/largest-contentful-paint#151 (3 comments by @mmocny, @smfr, @tunetheweb)
-
Need a new DOM concept for user-driven events rather than using `isTrusted` w3c/largest-contentful-paint#105 (2 comments by @mmocny, @tunetheweb)
-
Report LCP algorithm should limit to single largest paint candidate, per report w3c/largest-contentful-paint#135 (2 comments by @caribouW3, @tunetheweb)
-
What is `loadTime` for an Image element added to the DOM after loading? w3c/largest-contentful-paint#146 (1 comment by @tunetheweb)
-
What is the behavior when paints emit from inside the Shadow DOM? w3c/largest-contentful-paint#152 (1 comment by @mmocny)
-
-
2 pull requests opened.
-
deploy: f1e014ef73fb05deaee46a7354f7a5fb4a53d0fa w3c/largest-contentful-paint#155, by @israelblankzalex-cyber.
-
Fix #135: report one candidate per paint w3c/largest-contentful-paint#154, by @mmocny.
-
-
1 pull request closed.
-
deploy: f1e014ef73fb05deaee46a7354f7a5fb4a53d0fa w3c/largest-contentful-paint#155.
-
-
1 pull request reopened.
-
deploy: f1e014ef73fb05deaee46a7354f7a5fb4a53d0fa w3c/largest-contentful-paint#155, by @israelblankzalex-cyber.
-
-
1 pull request received 13 new comments.
-
Fix #135: report one candidate per paint w3c/largest-contentful-paint#154 (13 comments by @mmocny, @shaseley)
-
w3c/paint-timing
-
1 pull request opened.
-
Enhance presentation-timestamps.md with new sections w3c/paint-timing#119, by @noamr.
-
-
1 pull request merged.
-
Enhance presentation-timestamps.md with new sections w3c/paint-timing#119.
-
-
1 pull request received 2 new comments.
-
Enhance presentation-timestamps.md with new sections w3c/paint-timing#119 (2 comments by @mmocny, @noamr)
-
w3c/hr-time
-
1 issue opened.
-
wan w3c/hr-time#171, by @tersayang3552.
-
-
1 issue closed.
-
wan w3c/hr-time#171.
-
-
1 pull request received 2 new comments.
-
change: Expose Performance interface to AudioWorklet w3c/hr-time#169 (2 comments by @mjwilson-google)
-
TR publications
-
2 documents published.
-
Paint Timing published as a Working Draft. History of Paint Timing
-
Event Timing API published as a Working Draft. History of Event Timing API
-
Participants
-
2 participants joined.
-
Elad Alon (Google LLC) joined.
-
Robert Liu (Google LLC) joined.
-
-
1 participant left.
-
Jennifer Strickland (W3C Invited Experts) left.
-
GitHub
w3c/largest-contentful-paint
-
2 issues received 7 new comments.
-
What is `size` for a repeating background image? w3c/largest-contentful-paint#151 (6 comments by @mmocny, @smfr)
-
w3c/event-timing
-
2 issues received 7 new comments.
-
Add `targetSelector` attribute to Event Timing API (for cases where target is detached) w3c/event-timing#126 (5 comments by @jasonwilliams, @mmocny, @samuelmaddock)
-
-
1 pull request merged.
-
Fix 126: Add targetIdentifier to PerformanceEventTiming w3c/event-timing#160.
-
-
1 pull request received 3 new comments.
-
Fix 126: Add targetIdentifier to PerformanceEventTiming w3c/event-timing#160 (3 comments by @mmocny, @shaseley)
-
w3c/device-memory
-
1 issue opened.
-
Update recommended upper and lower bounds w3c/device-memory#50, by @tomayac.
-
w3c/network-error-logging
-
1 issue opened.
-
Clarify NEL's purpose, and a question w3c/network-error-logging#192, by @Synchro.
-
-
1 issue received 1 new comment.
w3c/hr-time
-
1 pull request received 1 new comment.
w3c/navigation-timing
-
2 issues received 3 new comments.
-
Extending the NavigationTimingType w3c/navigation-timing#184 (2 comments by @fergald, @gilbertococchi)
-
[Editorial] The referencing of "not restored reasons" is broken w3c/navigation-timing#208 (1 comment by @mmocny)
-
w3c/paint-timing
-
1 pull request opened.
-
Update editor information for Noam Rosenthal w3c/paint-timing#118, by @noamr.
-
-
1 pull request merged.
-
Update editor information for Noam Rosenthal w3c/paint-timing#118.
-
w3c/web-performance
-
3 issues opened.
-
983698.com w3c/web-performance#66, by @Trile9502.
-
Trilevn w3c/web-performance#65, by @Trile9502.
-
T w3c/web-performance#64, by @Trile9502.
-
-
3 issues closed.
-
983698.com w3c/web-performance#66.
-
Trilevn w3c/web-performance#65.
-
T w3c/web-performance#64.
-
-
1 issue reopened.
-
Trilevn w3c/web-performance#65, by @Trile9502.
-
w3c/longtasks
-
1 issue received 1 new comment.
w3c/user-timing
-
1 issue received 2 new comments.
-
Add a non-normative format for the `detail` param that allows developers to customize the presentation of timings in devtools w3c/user-timing#111 (2 comments by @jackfranklin, @tunetheweb)
-
w3c/resource-timing
-
1 issue received 1 new comment.
-
Add service worker static routing API information to resource timing w3c/resource-timing#389 (1 comment by @yoshisatoyanagisawa)
-
TR publications
-
3 documents published.
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Paint Timing published as a Working Draft. History of Paint Timing
-
Largest Contentful Paint published as a Working Draft. History of Largest Contentful Paint
-
Participants
-
1 participant joined.
-
Franco Vieira de Souza (Apple Inc.) joined.
-
-
2 participants left.
-
Benjamin De Kosnik (Mozilla Foundation) left.
-
Domenic Denicola (Google LLC) left.
-
GitHub
w3c/largest-contentful-paint
-
13 issues opened.
-
What is `size` for a repeating background image? w3c/largest-contentful-paint#151, by @smfr.
-
"has dispatched scroll event" should only reflect user scrolls w3c/largest-contentful-paint#150, by @smfr.
-
`paintTextNodes` definition doesn't work for paintable pseudo-elements w3c/largest-contentful-paint#149, by @smfr.
-
Impact of animations on LCP is not specified w3c/largest-contentful-paint#148, by @smfr.
-
LCP is affected by `will-change: transform` w3c/largest-contentful-paint#147, by @smfr.
-
What is `loadTime` for an Image element added to the DOM after loading? w3c/largest-contentful-paint#146, by @smfr.
-
LargestContentfulPaint has both `renderTime` and `paintTime` via the mixin. Are they different? w3c/largest-contentful-paint#145, by @smfr.
-
"with element’s transforms applied" links to transform streams, not CSS transforms w3c/largest-contentful-paint#144, by @smfr.
-
The definition of `effective visual size` is circular w3c/largest-contentful-paint#143, by @smfr.
-
"Text nodes" aren't really text nodes, right? w3c/largest-contentful-paint#142, by @smfr.
-
How to compute opacity in "eligible to be largest contentful paint" w3c/largest-contentful-paint#141, by @smfr.
-
Clarify "the intersection rect algorithm" w3c/largest-contentful-paint#140, by @smfr.
-
Clarify how to compare sizes w3c/largest-contentful-paint#139, by @smfr.
-
-
2 issues closed.
-
"has dispatched scroll event" should only reflect user scrolls w3c/largest-contentful-paint#150.
-
Clarify how to compare sizes w3c/largest-contentful-paint#139.
-
-
13 issues received 47 new comments.
-
LargestContentfulPaint has both `renderTime` and `paintTime` via the mixin. Are they different? w3c/largest-contentful-paint#145 (9 comments by @noamr, @smfr)
-
Clarify "the intersection rect algorithm" w3c/largest-contentful-paint#140 (7 comments by @mmocny, @smfr)
-
"Text nodes" aren't really text nodes, right? w3c/largest-contentful-paint#142 (7 comments by @mmocny, @smfr)
-
How to compute opacity in "eligible to be largest contentful paint" w3c/largest-contentful-paint#141 (4 comments by @mmocny, @smfr)
-
LCP is affected by `will-change: transform` w3c/largest-contentful-paint#147 (4 comments by @mmocny, @smfr, @tunetheweb)
-
What is `loadTime` for an Image element added to the DOM after loading? w3c/largest-contentful-paint#146 (3 comments by @smfr)
-
Impact of animations on LCP is not specified w3c/largest-contentful-paint#148 (3 comments by @mmocny, @smfr)
-
The definition of `effective visual size` is circular w3c/largest-contentful-paint#143 (3 comments by @mmocny)
-
"with element’s transforms applied" links to transform streams, not CSS transforms w3c/largest-contentful-paint#144 (2 comments by @mmocny, @smfr)
-
Need a new DOM concept for user-driven events rather than using `isTrusted` w3c/largest-contentful-paint#105 (1 comment by @smfr)
-
"has dispatched scroll event" should only reflect user scrolls w3c/largest-contentful-paint#150 (1 comment by @smfr)
-
The spec still links to the removed renderTime attribute w3c/largest-contentful-paint#133 (1 comment by @smfr)
-
-
1 pull request opened.
-
Update code example in README following renderTime changes w3c/largest-contentful-paint#138, by @tunetheweb.
-
-
1 pull request merged.
-
Update code example in README following renderTime changes w3c/largest-contentful-paint#138.
-
-
1 pull request received 2 new comments.
-
Update code example in README following renderTime changes w3c/largest-contentful-paint#138 (2 comments by @noamr, @tunetheweb)
-
w3c/navigation-timing
-
1 issue opened.
-
[Editorial] The referencing of "not restored reasons" is broken w3c/navigation-timing#208, by @lukewarlow.
-
-
1 issue closed.
-
NavigationTimingType enum need updates as HTML spec changed w3c/navigation-timing#185.
-
-
3 issues received 18 new comments.
-
Extending the NavigationTimingType w3c/navigation-timing#184 (16 comments by @domenic, @fergald, @gilbertococchi, @tunetheweb, @yoavweiss)
-
Proposal: add timestamp for when "activation" or "dismissal" starts w3c/navigation-timing#193 (1 comment by @nicjansma)
-
Add `confidence` field to PerformanceNavigationTiming w3c/navigation-timing#202 (1 comment by @nicjansma)
-
-
1 pull request opened.
-
Remove references to "prerender" w3c/navigation-timing#207, by @tunetheweb.
-
-
1 pull request merged.
-
Remove references to "prerender" w3c/navigation-timing#207.
-
w3c/event-timing
-
2 issues opened.
-
Consider decoupling first-input logic from `set event timing entry duration` w3c/event-timing#159, by @francovs.
-
"has dispatched input event" wording is misleading w3c/event-timing#158, by @smfr.
-
-
3 issues received 4 new comments.
-
Add `targetSelector` attribute to Event Timing API (for cases where target is detached) w3c/event-timing#126 (2 comments by @mmocny)
-
Consider decoupling first-input logic from `set event timing entry duration` w3c/event-timing#159 (1 comment by @mmocny)
-
-
1 pull request opened.
-
Fix 126: Add targetIdentifier to PerformanceEventTiming w3c/event-timing#160, by @mmocny.
-
-
1 pull request received 19 new comments.
-
Fix 126: Add targetIdentifier to PerformanceEventTiming w3c/event-timing#160 (19 comments by @mmocny, @noamr, @shaseley)
-
w3c/resource-timing
-
1 issue opened.
-
Clarify nextHopProtocol value for cached fetch, part 2 w3c/resource-timing#419, by @nicjansma.
-
-
2 issues closed.
-
Expose Content-Encoding to ResourceTiming w3c/resource-timing#381.
-
Resource Initiator Information Reporting w3c/resource-timing#380.
-
-
1 issue reopened.
-
Expose Content-Encoding to ResourceTiming w3c/resource-timing#381, by @yoavweiss.
-
-
3 issues received 16 new comments.
-
Add service worker static routing API information to resource timing w3c/resource-timing#389 (11 comments by @quasi-mod, @sisidovski, @yoavweiss, @yoshisatoyanagisawa)
-
Expose Content-Encoding to ResourceTiming w3c/resource-timing#381 (3 comments by @annevk, @yoavweiss)
-
Resource Initiator Information Reporting w3c/resource-timing#380 (2 comments by @mmocny, @yoavweiss)
-
-
1 pull request closed.
-
Expose Content-Encoding to resource-timing w3c/resource-timing#385.
-
-
1 pull request received 3 new comments.
-
Expose Content-Encoding to resource-timing w3c/resource-timing#385 (3 comments by @annevk, @yoavweiss)
-
w3c/element-timing
-
2 issues received 9 new comments.
-
How should Element Timing interact with Shadow DOM? w3c/element-timing#3 (8 comments by @frehner, @jasonwilliams, @jdapena, @justinfagnani, @mmocny, @nolanlawson, @yoavweiss)
-
Clarify Element Timing's handling of pseudo-elements w3c/element-timing#74 (1 comment by @brendankenny)
-
w3c/paint-timing
-
1 issue opened.
-
The spec never says when "Mark paint timing" is called w3c/paint-timing#115, by @smfr.
-
-
1 issue closed.
-
The spec never says when "Mark paint timing" is called w3c/paint-timing#115.
-
-
1 issue received 3 new comments.
-
The spec never says when "Mark paint timing" is called w3c/paint-timing#115 (3 comments by @noamr, @smfr)
-
-
2 pull requests opened.
-
Fix headings for Paint Timing Mixin w3c/paint-timing#117, by @noamr.
-
Add informative note about how PaintTimingMixin works w3c/paint-timing#116, by @noamr.
-
-
2 pull requests merged.
-
Fix headings for Paint Timing Mixin w3c/paint-timing#117.
-
Add informative note about how PaintTimingMixin works w3c/paint-timing#116.
-
-
1 pull request received 1 new comment.
w3c/reporting
-
1 issue closed.
-
Strip URL of CSP is not reused w3c/reporting#283.
-
-
1 pull request merged.
-
Reuse Strip URL in Generate a Report w3c/reporting#288.
-
-
1 pull request closed.
-
Add WPT metadata to spec w3c/reporting#282.
-
-
2 pull requests received 3 new comments.
w3c/user-timing
-
1 issue received 1 new comment.
-
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/web-performance
-
2 issues opened.
-
Bgc w3c/web-performance#63, by @Trile9502.
-
T w3c/web-performance#62, by @Trile9502.
-
-
1 issue reopened.
-
T w3c/web-performance#62, by @Trile9502.
-
TR publications
-
3 documents published.
-
Resource Timing published twice as a Candidate Recommendation Draft. History of Resource Timing
-
Largest Contentful Paint published as a Working Draft. History of Largest Contentful Paint
-
Participants
-
1 participant joined.
-
Michael Jackson (Microsoft Corporation) joined.
-
-
4 participants left.
-
Douglas Creager (Microsoft Corporation) left.
-
Mahesh Bharadava (Skynet Technologies) left.
-
Nolan Lawson (Salesforce) left.
-
Shuo Feng (Mozilla Foundation) left.
-
GitHub
w3c/reporting
-
1 issue opened.
-
The Reporting API defines "user agent" which collides with the infra definition w3c/reporting#287, by @yoavweiss.
-
-
1 issue closed.
-
1 issue received 1 new comment.
-
The Reporting API defines "user agent" which collides with the infra definition w3c/reporting#287 (1 comment by @yoavweiss)
-
-
1 pull request opened.
-
Reuse Strip URL in Generate a Report w3c/reporting#288, by @yoavweiss.
-
w3c/largest-contentful-paint
-
2 issues opened.
-
Report in LargestImage and LargestText paints in addition to LCP w3c/largest-contentful-paint#137, by @andydavies.
-
Report LCP algorithm should limit to single largest paint candidate, per report w3c/largest-contentful-paint#135, by @mmocny.
-
-
1 issue closed.
-
The spec still links to the removed renderTime attribute w3c/largest-contentful-paint#133.
-
-
5 issues received 14 new comments.
-
The spec still links to the removed renderTime attribute w3c/largest-contentful-paint#133 (4 comments by @mmocny, @noamr, @smfr)
-
Intrinsic size calculation includes areas of images that are cropped out using object-fit:cover w3c/largest-contentful-paint#134 (3 comments by @clelland, @mmocny)
-
Report in LargestImage and LargestText paints in addition to LCP w3c/largest-contentful-paint#137 (3 comments by @andydavies, @mmocny)
-
Report LCP algorithm should limit to single largest paint candidate, per report w3c/largest-contentful-paint#135 (3 comments by @mmocny)
-
LCP PerformanceEntry should Extend from PerformanceElementTiming entry w3c/largest-contentful-paint#127 (1 comment by @mmocny)
-
-
1 pull request opened.
-
Fix renderTime reference w3c/largest-contentful-paint#136, by @noamr.
-
-
1 pull request merged.
-
Fix renderTime reference w3c/largest-contentful-paint#136.
-
-
1 pull request received 2 new comments.
w3c/network-error-logging
-
1 issue opened.
-
HTTP error responses implementations inconsistent with spec w3c/network-error-logging#191, by @tunetheweb.
-
w3c/hr-time
-
1 issue opened.
-
Qq t w3c/hr-time#170, by @meipaulyboy513-ship-it.
-
-
1 issue closed.
-
Qq t w3c/hr-time#170.
-
-
1 pull request received 5 new comments.
-
change: Expose Performance interface to AudioWorklet w3c/hr-time#169 (5 comments by @mjwilson-google, @yoavweiss)
-
w3c/event-timing
-
1 issue received 4 new comments.
-
Consider documenting the INP algorithm (as a non-normative section of Event Timing spec) w3c/event-timing#157 (4 comments by @andydavies, @mmocny)
-
w3c/resource-timing
-
1 issue closed.
-
List of initiatorType types w3c/resource-timing#364.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Edit the list of possible initiatorType values. w3c/resource-timing#418.
-
-
1 pull request received 1 new comment.
-
w3c/resource-timing#416 (1 comment by @w3cbot)
-
w3c/device-memory
-
1 issue closed.
-
Consider reporting device class, rather than reporting device specs w3c/device-memory#49.
-
-
1 issue received 2 new comments.
-
Consider reporting device class, rather than reporting device specs w3c/device-memory#49 (2 comments by @sagudev, @yoavweiss)
-
w3c/element-timing
-
1 pull request opened.
-
Use new [Reflect] instead of spec prose w3c/element-timing#88, by @lukewarlow.
-
-
1 pull request merged.
-
Use new [Reflect] instead of spec prose w3c/element-timing#88.
-
-
1 pull request received 1 new comment.
w3c/web-performance
-
1 pull request merged.
-
W3C WebPerf 2023 Charter w3c/web-performance#58.
-
Participants
-
2 participants joined.
-
Cory Caywood (Rakuten Group, Inc.) joined.
-
Adrian de la Rosa (Datadog) joined.
-
-
1 participant left.
-
Rick Klein (Datadog) left.
-
GitHub
w3c/resource-timing
-
1 issue received 1 new comment.
-
Add service worker static routing API information to resource timing w3c/resource-timing#389 (1 comment by @quasi-mod)
-
-
1 pull request received 7 new comments.
-
Edit the list of possible initiatorType values. w3c/resource-timing#418 (7 comments by @guohuideng2024, @noamr)
-
w3c/largest-contentful-paint
-
1 issue opened.
-
Intrinsic size calculation includes areas of images that are cropped out using object-fit:cover w3c/largest-contentful-paint#134, by @andydavies.
-
-
1 issue received 3 new comments.
-
Intrinsic size calculation includes areas of images that are cropped out using object-fit:cover w3c/largest-contentful-paint#134 (3 comments by @clelland, @mmocny, @yoavweiss)
-
w3c/device-memory
-
1 issue opened.
-
Consider reporting device class, rather than reporting device specs w3c/device-memory#49, by @sagudev.
-
w3c/event-timing
-
1 issue opened.
-
Consider documenting the INP algorithm (as a non-normative section of Event Timing spec) w3c/event-timing#157, by @mmocny.
-
-
2 issues received 5 new comments.
-
Default buffering of Event Timing Entries is based on durationThreshold: 104 -- even for Interactions. w3c/event-timing#124 (3 comments by @andydavies, @mmocny, @tunetheweb)
-
Consider documenting the INP algorithm (as a non-normative section of Event Timing spec) w3c/event-timing#157 (2 comments by @mmocny)
-
w3c/reporting
-
1 issue opened.
-
Missing values for Report in dictionary w3c/reporting#286, by @TimvdLippe.
-
-
1 pull request received 1 new comment.
TR publications
-
3 documents published.
-
Resource Timing published as a Candidate Recommendation Draft. History of Resource Timing
-
Reporting API published twice as a Working Draft. History of Reporting API
-
Participants
-
1 participant joined.
-
Shengtao Xiao (Ant Group Co., Ltd.) joined.
-
-
2 participants left.
-
Sen Yang (Alibaba Group) left.
-
Binghui Chen (Alibaba Group) left.
-
-
1 organization joined.
-
Ant Group Co., Ltd. joined.
-
GitHub
w3c/resource-timing
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Edit the list of possible initiatorType values. w3c/resource-timing#418, by @guohuideng2024.
-
Edit the list of possible initiatorType values w3c/resource-timing#417, by @guohuideng2024.
-
-
1 pull request merged.
-
Expose a filtered content-encoding value to resource timing w3c/resource-timing#411.
-
-
1 pull request closed.
-
Edit the list of possible initiatorType values w3c/resource-timing#417.
-
-
2 pull requests received 4 new comments.
-
Edit the list of possible initiatorType values. w3c/resource-timing#418 (2 comments by @guohuideng2024)
-
Add SW static routing API timing information to resource timing w3c/resource-timing#415 (2 comments by @quasi-mod, @yoavweiss)
-
w3c/element-timing
-
1 issue closed.
-
Wrong Web IDL type for URLs in Element Timing API w3c/element-timing#83.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Convert the type of PerformanceElementTiming url attribute to USVString w3c/element-timing#87, by @canova.
-
-
1 pull request merged.
-
Convert the type of PerformanceElementTiming url attribute to USVString w3c/element-timing#87.
-
-
1 pull request received 1 new comment.
-
Convert the type of PerformanceElementTiming url attribute to USVString w3c/element-timing#87 (1 comment by @mmocny)
-
w3c/user-timing
-
2 issues received 2 new comments.
-
Extending 'Recommended mark names' to allow user agents to detect media timeouts w3c/user-timing#110 (1 comment by @nicjansma)
-
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/reporting
-
1 issue opened.
-
Strip URL of CSP is not reused w3c/reporting#283, by @TimvdLippe.
-
-
2 issues received 8 new comments.
-
Report body interfaces w3c/reporting#216 (6 comments by @domenic, @hamishwillee, @tidoust, @TimvdLippe)
-
-
3 pull requests opened.
-
Fix up URL stripping w3c/reporting#285, by @yoavweiss.
-
Remove the Report and ReportBody interfaces w3c/reporting#284, by @yoavweiss.
-
Add WPT metadata to spec w3c/reporting#282, by @TimvdLippe.
-
-
1 pull request merged.
-
Remove the Report and ReportBody interfaces w3c/reporting#284.
-
-
2 pull requests received 4 new comments.
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/event-timing
-
1 issue received 2 new comments.
-
Delayed dispatch mechanism of `pointerdown` and `keydown` events doesn't work well w3c/event-timing#145 (2 comments by @canova, @mmocny)
-
TR publications
-
7 documents published.
-
Performance Timeline published as a Candidate Recommendation Draft. History of Performance Timeline
-
Event Timing API published as a Working Draft. History of Event Timing API
-
requestIdleCallback() published as a Working Draft. History of requestIdleCallback()
-
Paint Timing published as a Working Draft. History of Paint Timing
-
Reporting API published as a Working Draft. History of Reporting API
-
Largest Contentful Paint published as a Working Draft. History of Largest Contentful Paint
-
Network Error Logging published as a Working Draft. History of Network Error Logging
-
Participants
-
2 participants joined.
-
Nazım Can Altınova (Mozilla Foundation) joined.
-
Yury Leonychev (Rakuten Group, Inc.) joined.
-
-
1 participant left.
-
Noli Fernan Perez (Rakuten Group, Inc.) left.
-
GitHub
w3c/resource-timing
-
1 issue closed.
-
Big difference between `redirectEnd` and `fetchStart` w3c/resource-timing#413.
-
-
4 issues received 7 new comments.
-
Expose Content-Encoding to ResourceTiming w3c/resource-timing#381 (4 comments by @annevk, @guohuideng2024)
-
Add service worker static routing API information to resource timing w3c/resource-timing#389 (1 comment by @davehunt)
-
Big difference between `redirectEnd` and `fetchStart` w3c/resource-timing#413 (1 comment by @nicjansma)
-
-
1 pull request opened.
-
Add SW static routing API timing information to resource timing w3c/resource-timing#415, by @quasi-mod.
-
-
2 pull requests received 7 new comments.
-
Expose a filtered content-encoding value to resource timing w3c/resource-timing#411 (4 comments by @annevk, @guohuideng2024)
-
Add SW static routing API timing information to resource timing w3c/resource-timing#415 (3 comments by @quasi-mod, @yoshisatoyanagisawa)
-
w3c/reporting
-
2 pull requests opened.
-
Add strip URL as an exported algorithm w3c/reporting#281, by @yoavweiss.
-
Export named parameters for "generate and queue a report" w3c/reporting#279, by @yoavweiss.
-
-
2 pull requests merged.
-
Add strip URL as an exported algorithm w3c/reporting#281.
-
Export named parameters for "generate and queue a report" w3c/reporting#279.
-
w3c/event-timing
-
1 issue opened.
-
All cases of right click event dispatch is not spec'd - `contextmenu` event should be handled w3c/event-timing#155, by @canova.
-
-
1 issue closed.
-
3 issues received 8 new comments.
-
Change the `pendingKeydowns` list and change keyboard `interactionId` assignment to be eager. w3c/event-timing#153 (5 comments by @canova, @mmocny)
-
All cases of right click event dispatch is not spec'd - `contextmenu` event should be handled w3c/event-timing#155 (2 comments by @canova)
-
Spec "fallbackTime" for cases where we don't need to wait for paint (modal dialog, visibilitychange...) w3c/event-timing#154 (1 comment by @mmocny)
-
-
1 pull request opened.
-
Add `contextmenu` to interactionId computation and handle the right click cases w3c/event-timing#156, by @canova.
-
-
1 pull request merged.
-
Add `contextmenu` to interactionId computation and handle the right click cases w3c/event-timing#156.
-
-
1 pull request received 7 new comments.
-
Add `contextmenu` to interactionId computation and handle the right click cases w3c/event-timing#156 (7 comments by @canova, @mmocny)
-
w3c/performance-timeline
-
1 pull request opened.
-
Use "invoke" properly w3c/performance-timeline#220, by @domenic.
-
-
1 pull request merged.
-
Use "invoke" properly w3c/performance-timeline#220.
-
-
1 pull request received 1 new comment.
w3c/paint-timing
-
2 issues opened.
-
`PerformancePaintTiming` needs its own `toJSON()` method w3c/paint-timing#113, by @canova.
-
FCP not getting logged due to Implementation differences w3c/paint-timing#112, by @yudeeeth.
-
-
1 issue closed.
-
`PerformancePaintTiming` needs its own `toJSON()` method w3c/paint-timing#113.
-
-
1 issue received 4 new comments.
-
FCP not getting logged due to Implementation differences w3c/paint-timing#112 (4 comments by @clelland, @jasonwilliams, @mmocny, @yudeeeth)
-
-
1 pull request opened.
-
Add `toJSON` to `PerformancePaintTiming` w3c/paint-timing#114, by @canova.
-
-
1 pull request merged.
-
Add `toJSON` to `PerformancePaintTiming` w3c/paint-timing#114.
-
-
1 pull request received 1 new comment.
w3c/element-timing
-
2 issues closed.
-
8 issues received 12 new comments.
-
Rather than add tagging attributes to elements, allow to "get timings for all elements" via flag. w3c/element-timing#68 (3 comments by @DerGernTod, @jdapena, @mmocny)
-
Element Timings and below-the-fold content report arbitrary timings and not useful intersectionRect. w3c/element-timing#42 (2 comments by @mmocny)
-
w3c/largest-contentful-paint
-
1 issue opened.
-
The spec still links to the removed renderTime attribute w3c/largest-contentful-paint#133, by @saschanaz.
-
-
1 issue closed.
-
https://w3c.github.io/largest-contentful-paint/ points to an version from Jan 2024 w3c/largest-contentful-paint#130.
-
-
3 issues received 9 new comments.
-
The spec still links to the removed renderTime attribute w3c/largest-contentful-paint#133 (5 comments by @mmocny, @noamr, @saschanaz)
-
renderTime should be CORS-protected, not TAO-protected w3c/largest-contentful-paint#111 (3 comments by @sefeng211, @tunetheweb)
-
https://w3c.github.io/largest-contentful-paint/ points to an version from Jan 2024 w3c/largest-contentful-paint#130 (1 comment by @canova)
-
-
1 pull request opened.
-
Fix the "Multiple elements have the same id" bikeshed error w3c/largest-contentful-paint#132, by @canova.
-
-
1 pull request merged.
-
Fix the "Multiple elements have the same id" bikeshed error w3c/largest-contentful-paint#132.
-
-
1 pull request received 6 new comments.
-
Fix the "Multiple elements have the same id" bikeshed error w3c/largest-contentful-paint#132 (6 comments by @canova, @clelland, @mmocny, @yoavweiss)
-
w3c/network-error-logging
-
1 issue closed.
-
Redefine network request in terms of Fetch w3c/network-error-logging#181.
-
-
1 issue received 2 new comments.
-
Handle type mismatches in NEL header more gracefully w3c/network-error-logging#85 (2 comments by @clelland, @nicjansma)
-
-
1 pull request merged.
-
Issue #181 - Redefine network request in terms of Fetch w3c/network-error-logging#182.
-
-
1 pull request received 3 new comments.
-
Issue #181 - Redefine network request in terms of Fetch w3c/network-error-logging#182 (3 comments by @clelland, @miketaylr)
-
TR publications
-
1 document published.
-
Event Timing API published as a Working Draft. History of Event Timing API
-
Participants
-
3 participants joined.
-
Taylore Givens (Microsoft Corporation) joined.
-
Monica CHINTALA (Microsoft Corporation) joined.
-
Luis Flores (Microsoft Corporation) joined.
-
-
3 participants left.
-
Sergey Chernyshev (Cloudflare) left.
-
Andrew Galloni (Cloudflare) left.
-
Lucas Pardue (Cloudflare) left.
-
-
1 organization left.
-
Cloudflare left.
-
GitHub
w3c/event-timing
-
3 issues opened.
-
Change the `pendingKeydowns` list and change keyboard `interactionId` assignment to be eager. w3c/event-timing#153, by @mmocny.
-
Consider supporting native drag & drop as an interactionId (and first-input candidate). w3c/event-timing#152, by @mmocny.
-
1 issue closed.
-
Move some definition of interactionID to UI Events w3c/event-timing#114.
-
-
1 issue received 3 new comments.
-
Default buffering of Event Timing Entries is based on durationThreshold: 104 -- even for Interactions. w3c/event-timing#124 (3 comments by @mmocny, @tunetheweb)
-
-
1 pull request merged.
-
Update list of editors and former editors w3c/event-timing#148.
-
w3c/element-timing
-
1 issue received 2 new comments.
-
Support Element Timing on Containers w3c/element-timing#79 (2 comments by @bkardell, @jasonwilliams)
-
-
1 pull request opened.
-
Fix typo "o a 4 second" w3c/element-timing#86, by @bkardell.
-
-
1 pull request merged.
-
Fix typo "o a 4 second" w3c/element-timing#86.
-
w3c/reporting
-
1 issue closed.
-
Setup auto-publishing w3c/reporting#207.
-
-
2 issues received 2 new comments.
-
Generate Test Report: cannot check if something is a JSON object w3c/reporting#273 (1 comment by @mmocny)
w3c/largest-contentful-paint
-
2 issues opened.
-
Should file drop count as a user interaction? w3c/largest-contentful-paint#131, by @tunetheweb.
-
https://w3c.github.io/largest-contentful-paint/ points to an version from Jan 2024 w3c/largest-contentful-paint#130, by @sefeng211.
-
-
1 issue closed.
-
Expose LCP renderTime in non-TAO cross-origin images, when it doesn't reflect the image decoding time w3c/largest-contentful-paint#91.
-
-
3 issues received 5 new comments.
-
Expose LCP renderTime in non-TAO cross-origin images, when it doesn't reflect the image decoding time w3c/largest-contentful-paint#91 (3 comments by @noamr, @yoavweiss)
-
https://w3c.github.io/largest-contentful-paint/ points to an version from Jan 2024 w3c/largest-contentful-paint#130 (1 comment by @mmocny)
-
Should file drop count as a user interaction? w3c/largest-contentful-paint#131 (1 comment by @mmocny)
-
w3c/resource-timing
-
1 issue received 2 new comments.
-
Would like a precise way to map PerformanceTimings to FetchEvent w3c/resource-timing#259 (2 comments by @noamr)
-
w3c/long-animation-frames
-
1 pull request opened.
-
Add sourceLine and sourceColumn to PerformanceScriptTiming w3c/long-animation-frames#29, by @joone.
-
TR publications
-
3 documents published.
-
Event Timing API published twice as a Working Draft. History of Event Timing API
-
Network Error Logging published as a Working Draft. History of Network Error Logging
-
Participants
-
2 participants left.
-
Benjamin Kelly (Meta) left.
-
Sia Karamalegos (Shopify) left.
-
GitHub
w3c/navigation-timing
-
1 pull request closed.
-
workerStart and redirects w3c/navigation-timing#131.
-
w3c/event-timing
-
1 issue opened.
-
`keypress` doesn't expose an `interactionId` but there is a web platform test for it w3c/event-timing#149, by @canova.
-
-
4 issues closed.
-
Consider evolving "first-input" to "first interaction" w3c/event-timing#139.
-
Should Section 2.2 reference 'considered for Event Timing' w3c/event-timing#56.
-
Broken references in Event Timing API w3c/event-timing#137.
-
-
7 issues received 11 new comments.
-
`keypress` doesn't expose an `interactionId` but there is a web platform test for it w3c/event-timing#149 (4 comments by @canova, @mmocny)
-
Should Section 2.2 reference 'considered for Event Timing' w3c/event-timing#56 (2 comments by @hawkinsw, @mmocny)
-
Audit the list of events which Event Timing api should report (and consider adding focus/blur) w3c/event-timing#130 (1 comment by @mmocny)
-
Spec should clarify value of `renderingTimestamp` whenever there is no next rendering opportunity. w3c/event-timing#123 (1 comment by @mmocny)
-
"has dispatched input event" should only be set for trusted events w3c/event-timing#121 (1 comment by @mmocny)
-
-
2 pull requests opened.
-
Fixes #139: First Input is First Event with InteractionId w3c/event-timing#151, by @mmocny.
-
Fixes #137: Change definition of target attribute w3c/event-timing#150, by @mmocny.
-
-
2 pull requests merged.
-
Fixes #139: First Input is First Event with InteractionId w3c/event-timing#151.
-
Fixes #137: Change definition of target attribute w3c/event-timing#150.
-
-
3 pull requests received 34 new comments.
-
Fixes #139: First Input is First Event with InteractionId w3c/event-timing#151 (29 comments by @canova, @mmocny, @shaseley)
-
Fixes #137: Change definition of target attribute w3c/event-timing#150 (4 comments by @canova, @mmocny)
-
w3c/reporting
-
1 issue received 2 new comments.
w3c/resource-timing
-
1 issue opened.
-
Resource Timing Buffer/Secondary Buffer properties have vague location w3c/resource-timing#414, by @ADKaster.
-
-
5 issues received 9 new comments.
-
Expose Content-Encoding to ResourceTiming w3c/resource-timing#381 (4 comments by @guohuideng2024, @pmeenan)
-
Big difference between `redirectEnd` and `fetchStart` w3c/resource-timing#413 (1 comment by @nicjansma)
-
Resource initiator information to enable creation of dependency trees w3c/resource-timing#263 (1 comment by @guohuideng2024)
-
Would like a precise way to map PerformanceTimings to FetchEvent w3c/resource-timing#259 (1 comment by @monica-ch)
-
w3c/largest-contentful-paint
-
1 issue closed.
-
renderTime should be CORS-protected, not TAO-protected w3c/largest-contentful-paint#111.
-
-
2 issues received 3 new comments.
-
Oversized transparent divs manipulate LCP calculation w3c/largest-contentful-paint#129 (2 comments by @mmocny)
-
renderTime should be CORS-protected, not TAO-protected w3c/largest-contentful-paint#111 (1 comment by @yoavweiss)
-
w3c/performance-timeline
-
1 issue opened.
-
PerformanceEntry.id is shadowed by PerformanceElementTiming.id. w3c/performance-timeline#218, by @powdercloud.
-
-
1 issue received 2 new comments.
-
PerformanceEntry.id is shadowed by PerformanceElementTiming.id. w3c/performance-timeline#218 (2 comments by @mmocny, @npm1)
-
-
1 pull request opened.
-
Remove PerformanceEntry.id and rephrase id generation. w3c/performance-timeline#219, by @powdercloud.
-
-
1 pull request received 2 new comments.
-
Remove PerformanceEntry.id and rephrase id generation. w3c/performance-timeline#219 (2 comments by @powdercloud)
-
w3c/element-timing
-
1 issue received 1 new comment.
-
Rather than add tagging attributes to elements, allow to "get timings for all elements" via flag. w3c/element-timing#68 (1 comment by @DerGernTod)
-
w3c/network-error-logging
-
1 issue opened.
-
Sample rate calculation contains logical error w3c/network-error-logging#189, by @PontusHanssen.
-
-
1 issue closed.
-
Sample rate calculation contains logical error w3c/network-error-logging#189.
-
-
1 pull request opened.
-
Correct sample rate calculation comparison w3c/network-error-logging#190, by @PontusHanssen.
-
-
1 pull request merged.
-
Correct sample rate calculation comparison w3c/network-error-logging#190.
-
-
1 pull request received 1 new comment.
TR publications
-
10 documents published.
-
Performance Timeline published as a Candidate Recommendation Draft. History of Performance Timeline
-
Resource Timing published as a Candidate Recommendation Draft. History of Resource Timing
-
User Timing published as a Candidate Recommendation Draft. History of User Timing
-
Event Timing API published as a Working Draft. History of Event Timing API
-
Paint Timing published as a Working Draft. History of Paint Timing
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Network Error Logging published 4 times as a Working Draft. History of Network Error Logging
-
Participants
-
3 participants joined.
-
Joone Hur (Microsoft Corporation) joined.
-
Brian Strauch (Meta) joined.
-
Mike Taylor (Google LLC) joined.
-
GitHub
w3c/event-timing
-
5 issues opened.
-
`interactionId`s of keyboard simulated clicks are not spec'd w3c/event-timing#147, by @canova.
-
"first-input" dispatch logic doesn't update the `interactionId` of `pointerdown` entries w3c/event-timing#146, by @canova.
-
Delayed dispatch mechanism of `pointerdown` and `keydown` events doesn't work well w3c/event-timing#145, by @canova.
-
Is interactionId `unsigned long long` or `unsigned long`? w3c/event-timing#143, by @canova.
-
"first-input" dispatch logic in the spec doesn't match the tests and the Chromium implementation w3c/event-timing#142, by @canova.
-
-
2 issues closed.
-
Consider removing pointermove (and interactionType and pointerIsDragSet) w3c/event-timing#140.
-
Is interactionId `unsigned long long` or `unsigned long`? w3c/event-timing#143.
-
-
7 issues received 25 new comments.
-
"first-input" dispatch logic doesn't update the `interactionId` of `pointerdown` entries w3c/event-timing#146 (7 comments by @canova, @mmocny)
-
"first-input" dispatch logic in the spec doesn't match the tests and the Chromium implementation w3c/event-timing#142 (6 comments by @canova, @mmocny)
-
Delayed dispatch mechanism of `pointerdown` and `keydown` events doesn't work well w3c/event-timing#145 (5 comments by @canova, @mmocny)
-
`interactionId`s of keyboard simulated clicks are not spec'd w3c/event-timing#147 (2 comments by @canova, @mmocny)
-
Is interactionId `unsigned long long` or `unsigned long`? w3c/event-timing#143 (2 comments by @canova, @mmocny)
-
Consider removing pointermove (and interactionType and pointerIsDragSet) w3c/event-timing#140 (2 comments by @canova, @mmocny)
-
-
2 pull requests opened.
-
Update list of editors and former editors w3c/event-timing#148, by @mmocny.
-
Remove pointermove, interactionType, and pointerIsDragSet from the interactionId computation w3c/event-timing#144, by @canova.
-
-
1 pull request merged.
-
1 pull request received 1 new comment.
-
Remove pointermove, interactionType, and pointerIsDragSet from the interactionId computation w3c/event-timing#144 (1 comment by @canova)
-
w3c/resource-timing
-
1 issue opened.
-
Big difference between `redirectEnd` and `fetchStart` w3c/resource-timing#413, by @andrew-samson.
-
-
1 issue closed.
-
Specify the behaviors of requestStart and responseStart for Prefetch w3c/resource-timing#360.
-
-
4 issues received 6 new comments.
-
Specify the behaviors of requestStart and responseStart for Prefetch w3c/resource-timing#360 (2 comments by @mmocny, @tunetheweb)
-
Expose a way to link a call to fetch to an individual PerformanceResourceTiming object w3c/resource-timing#102 (1 comment by @costela)
-
1 pull request opened.
-
Update auto-publish.yml w3c/resource-timing#412, by @caribouW3.
-
-
1 pull request merged.
-
Update auto-publish.yml w3c/resource-timing#412.
-
-
2 pull requests received 12 new comments.
-
Expose a filtered content-encoding value to resource timing w3c/resource-timing#411 (11 comments by @guohuideng2024, @noamr)
-
w3c/performance-timeline
-
1 issue received 5 new comments.
-
Consider changing the spec text to allow `buffered` with `entryTypes` w3c/performance-timeline#215 (5 comments by @mmocny, @noamr)
-
-
2 pull requests opened.
-
Update auto-publish.yml w3c/performance-timeline#217, by @caribouW3.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/performance-timeline#216, by @deniak.
-
-
1 pull request merged.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/performance-timeline#216.
-
-
1 pull request closed.
-
Update auto-publish.yml w3c/performance-timeline#217.
-
w3c/reporting
-
1 issue opened.
-
CSS Error Source Element w3c/reporting#278, by @jabcreations.
-
-
1 issue closed.
-
Set reporting endpoint in cross-domain iframe from parent page w3c/reporting#262.
-
-
2 issues received 2 new comments.
-
Set reporting endpoint in cross-domain iframe from parent page w3c/reporting#262 (1 comment by @mmocny)
-
1 pull request merged.
-
Use the more common index.bs naming w3c/reporting#256.
-
-
1 pull request received 2 new comments.
w3c/paint-timing
-
2 pull requests opened.
-
Fix PaintTimingMixin section header and link w3c/paint-timing#111, by @canova.
-
Fix broken Long Animation Frames spec url w3c/paint-timing#110, by @canova.
-
-
2 pull requests merged.
-
Fix PaintTimingMixin section header and link w3c/paint-timing#111.
-
Fix broken Long Animation Frames spec url w3c/paint-timing#110.
-
-
1 pull request received 2 new comments.
w3c/largest-contentful-paint
-
1 issue received 3 new comments.
-
LCP PerformanceEntry should Extend from PerformanceElementTiming entry w3c/largest-contentful-paint#127 (3 comments by @mmocny)
-
w3c/network-error-logging
-
5 issues opened.
-
Deal with fetchParams w3c/network-error-logging#188, by @miketaylr.
-
Should some Predefined network error types map directly to fetch error states? w3c/network-error-logging#185, by @miketaylr.
-
Map NEL phases to fetch w3c/network-error-logging#184, by @miketaylr.
-
Redefine report delivery in terms of Fetch w3c/network-error-logging#183, by @miketaylr.
-
Redefine network request in terms of Fetch w3c/network-error-logging#181, by @miketaylr.
-
-
3 issues closed.
-
Normative references to discontinued specs in Network Error Logging w3c/network-error-logging#177.
-
Register with IANA? w3c/network-error-logging#149.
-
False claim in privacy section w3c/network-error-logging#121.
-
-
6 issues received 12 new comments.
-
Normative references to discontinued specs in Network Error Logging w3c/network-error-logging#177 (2 comments by @miketaylr)
-
5 pull requests opened.
-
Update auto-publish.yml w3c/network-error-logging#187, by @caribouW3.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/network-error-logging#186, by @deniak.
-
Issue #181 - Redefine network request in terms of Fetch w3c/network-error-logging#182, by @miketaylr.
-
Update normative RFC references w3c/network-error-logging#180, by @miketaylr.
-
Remove settings from example report w3c/network-error-logging#179, by @miketaylr.
-
-
6 pull requests merged.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/network-error-logging#186.
-
Update normative RFC references w3c/network-error-logging#180.
-
Replace manual list of dependencies by automatically generated index w3c/network-error-logging#171.
-
Remove settings from example report w3c/network-error-logging#179.
-
Add note about transparent MitM proxies w3c/network-error-logging#157.
-
Balance the brackets w3c/network-error-logging#174.
-
-
1 pull request closed.
-
Update auto-publish.yml w3c/network-error-logging#187.
-
-
6 pull requests received 25 new comments.
-
Issue #181 - Redefine network request in terms of Fetch w3c/network-error-logging#182 (12 comments by @clelland, @miketaylr)
-
Replace manual list of dependencies by automatically generated index w3c/network-error-logging#171 (3 comments by @clelland, @miketaylr)
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/network-error-logging#186 (1 comment by @clelland)
-
w3c/hr-time
-
1 pull request opened.
-
change: Expose Performance interface to AudioWorklet w3c/hr-time#169, by @mjwilson-google.
-
-
1 pull request received 1 new comment.
w3c/element-timing
-
1 issue closed.
-
CFC: adopt to WebPerfWG as a Working Draft w3c/element-timing#48.
-
-
3 issues received 4 new comments.
-
Report image Element Timing algorithm doesn't report intrinsic size for LCP w3c/element-timing#31 (2 comments by @mmocny)
-
w3c/navigation-timing
-
1 pull request opened.
-
Update auto-publish.yml w3c/navigation-timing#206, by @caribouW3.
-
-
1 pull request merged.
-
Update auto-publish.yml w3c/navigation-timing#206.
-
-
1 pull request received 1 new comment.
w3c/server-timing
-
2 pull requests opened.
-
Update auto-publish.yml w3c/server-timing#101, by @caribouW3.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/server-timing#100, by @deniak.
-
-
1 pull request merged.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/server-timing#100.
-
-
1 pull request closed.
-
Update auto-publish.yml w3c/server-timing#101.
-
-
2 pull requests received 2 new comments.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/server-timing#100 (1 comment by @clelland)
w3c/user-timing
-
1 pull request opened.
-
Update auto-publish.yml w3c/user-timing#115, by @caribouW3.
-
-
1 pull request merged.
-
Update auto-publish.yml w3c/user-timing#115.
-
-
1 pull request received 1 new comment.
w3c/device-memory
-
2 pull requests opened.
-
Update auto-publish.yml w3c/device-memory#48, by @caribouW3.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/device-memory#47, by @deniak.
-
-
1 pull request merged.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/device-memory#47.
-
-
1 pull request closed.
-
Update auto-publish.yml w3c/device-memory#48.
-
-
2 pull requests received 2 new comments.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/device-memory#47 (1 comment by @clelland)
w3c/beacon
-
2 pull requests opened.
-
Update auto-publish.yml w3c/beacon#84, by @caribouW3.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/beacon#83, by @deniak.
-
-
1 pull request merged.
-
GitHub actions: replace ubuntu-20.04 with ubuntu-latest w3c/beacon#83.
-
-
1 pull request closed.
-
Update auto-publish.yml w3c/beacon#84.
-
-
2 pull requests received 2 new comments.
Participants
-
3 participants joined.
-
Pavlo Neiman (Amazon) joined.
-
Arturo Silva (The Washington Post) joined.
-
Patrick Nielsen (The Washington Post) joined.
-
-
4 participants left.
-
Matt Falkenhagen (Google LLC) left.
-
Jeb Barabanov (Wix.com Ltd.) left.
-
Madhavan Ramakrishnan (Techfriar) left.
-
Chengzhong Wu (Alibaba Group) left.
-
-
1 organization joined.
-
The Washington Post joined.
-
-
1 organization left.
-
Techfriar left.
-
GitHub
w3c/resource-timing
-
2 issues received 18 new comments.
-
Expose Content-Encoding to ResourceTiming w3c/resource-timing#381 (17 comments by @guohuideng2024, @LPardue, @noamr, @pmeenan, @yoavweiss)
-
Resource initiator information to enable creation of dependency trees w3c/resource-timing#263 (1 comment by @guohuideng2024)
-
-
1 pull request received 2 new comments.
-
Expose a filtered content-encoding value to resource timing w3c/resource-timing#411 (2 comments by @guohuideng2024, @noamr)
-
w3c/event-timing
-
1 issue opened.
-
Feature request: Support better metric distribution analysis w3c/event-timing#141, by @issacgerges.
-
-
1 issue closed.
-
Feature request: Support better metric distribution analysis w3c/event-timing#141.
-
-
1 issue received 2 new comments.
-
Feature request: Support better metric distribution analysis w3c/event-timing#141 (2 comments by @issacgerges, @mmocny)
-
w3c/largest-contentful-paint
-
2 issues opened.
-
Oversized transparent divs manipulate LCP calculation w3c/largest-contentful-paint#129, by @loader3788.
-
Wrong Web IDL type for URLs in Largest Contentful Paint w3c/largest-contentful-paint#128, by @dontcallmedom-bot.
-
-
1 issue received 1 new comment.
-
LCP PerformanceEntry should Extend from PerformanceElementTiming entry w3c/largest-contentful-paint#127 (1 comment by @mmocny)
-
w3c/reporting
-
3 issues opened.
-
How are reports actually delivered by the user agent? w3c/reporting#277, by @MexHigh.
-
Is failure reporting a privacy leak? w3c/reporting#276, by @annevk.
-
[reporting-1] Wrong Web IDL type for URLs in Reporting API w3c/reporting#275, by @dontcallmedom-bot.
-
-
1 issue closed.
-
How are reports actually delivered by the user agent? w3c/reporting#277.
-
-
2 issues received 3 new comments.
-
How are reports actually delivered by the user agent? w3c/reporting#277 (2 comments by @gapple, @MexHigh)
-
Set reporting endpoint in cross-domain iframe from parent page w3c/reporting#262 (1 comment by @clelland)
-
w3c/long-animation-frames
-
2 issues opened.
-
Long jobs from RequestIdleCallback are not contributing to blockingDuration w3c/long-animation-frames#28, by @peter-uxify.
-
Wrong Web IDL type for URLs in Long Animation Frames API w3c/long-animation-frames#27, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Long jobs from RequestIdleCallback are not contributing to blockingDuration w3c/long-animation-frames#28.
-
-
2 issues received 6 new comments.
-
Long jobs from RequestIdleCallback are not contributing to blockingDuration w3c/long-animation-frames#28 (5 comments by @mmocny, @noamr, @peter-uxify)
-
w3c/element-timing
-
1 issue opened.
-
Wrong Web IDL type for URLs in Element Timing API w3c/element-timing#83, by @dontcallmedom-bot.
-
-
3 pull requests opened.
-
Update URL to the Editor's Draft w3c/element-timing#85, by @tidoust.
-
Fix self-link url w3c/element-timing#84, by @dontcallmedom.
-
Update index.bs w3c/element-timing#82, by @caribouW3.
-
-
2 pull requests merged.
-
Update URL to the Editor's Draft w3c/element-timing#85.
-
Update index.bs w3c/element-timing#82.
-
-
1 pull request closed.
-
Fix self-link url w3c/element-timing#84.
-
-
2 pull requests received 2 new comments.
w3c/performance-timeline
-
1 issue opened.
-
Consider changing the spec text to allow `buffered` with `entryTypes` w3c/performance-timeline#215, by @hiikezoe.
-