Web Performance Working Group - Activity in 2024
No matches.
TR publications
-
1 document published.
-
requestIdleCallback() published as a Working Draft. History of requestIdleCallback()
-
GitHub
w3c/longtasks
-
1 issue opened.
-
Add support for Web Workers w3c/longtasks#142, by @joone.
-
-
2 issues received 9 new comments.
w3c/requestidlecallback
-
1 issue opened.
-
Warn readers that IdleDeadline.timeRemaining() can adjust asynchronously w3c/requestidlecallback#104, by @jyasskin.
-
-
1 pull request opened.
-
Refer to "get deadline time" where it's set. w3c/requestidlecallback#103, by @jyasskin.
-
-
1 pull request merged.
-
Refer to "get deadline time" where it's set. w3c/requestidlecallback#103.
-
w3c/resource-timing
-
2 issues received 10 new comments.
-
Expose Content-Encoding to ResourceTiming w3c/resource-timing#381 (7 comments by @guohuideng2024, @nhelfman, @pmeenan, @yoavweiss)
-
Add service worker static routing API information to resource timing w3c/resource-timing#389 (3 comments by @ErikWitt, @quasi-mod)
-
-
1 pull request opened.
-
Expose a filtered content-encoding value to resource timing w3c/resource-timing#411, by @guohuideng2024.
-
w3c/element-timing
-
1 pull request merged.
-
Inclujde `PaintMixin` in `PerformanceElementTiming` w3c/element-timing#81.
-
-
1 pull request received 2 new comments.
-
Inclujde `PaintMixin` in `PerformanceElementTiming` w3c/element-timing#81 (2 comments by @clelland, @noamr)
-
w3c/largest-contentful-paint
-
1 issue opened.
-
LCP PerformanceEntry should Extend from PerformanceElementTiming entry w3c/largest-contentful-paint#127, by @mmocny.
-
-
1 issue received 5 new comments.
-
LCP PerformanceEntry should Extend from PerformanceElementTiming entry w3c/largest-contentful-paint#127 (5 comments by @bdekoz, @clelland, @mmocny)
-
w3c/long-animation-frames
-
2 issues opened.
-
Better script URL attribution for dynamically inserted scripts w3c/long-animation-frames#25, by @mattzeunert.
-
Usage example near the top of the spec repeats the `observer.observe` code w3c/long-animation-frames#24, by @andydavies.
-
-
1 issue closed.
-
Better script URL attribution for dynamically inserted scripts w3c/long-animation-frames#25.
-
-
3 issues received 5 new comments.
-
Better script URL attribution for dynamically inserted scripts w3c/long-animation-frames#25 (2 comments by @andydavies, @tunetheweb)
-
Usage example near the top of the spec repeats the `observer.observe` code w3c/long-animation-frames#24 (2 comments by @andydavies, @mmocny)
-
Provide some source information for scripts without source information w3c/long-animation-frames#11 (1 comment by @andydavies)
-
-
1 pull request opened.
-
Remove duplicate observer registration in initial usage example w3c/long-animation-frames#26, by @andydavies.
-
w3c/reporting
-
1 issue opened.
-
Accessibility Reports? w3c/reporting#274, by @aluhrs13.
-
-
1 issue received 1 new comment.
TR publications
-
6 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
-
Paint Timing published twice 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
-
1 participant joined.
-
Issac Gerges (Salesforce) joined.
-
GitHub
w3c/hr-time
-
1 issue closed.
-
"safe" time in milliseconds since epoch without settings object w3c/hr-time#165.
-
-
1 issue received 5 new comments.
-
"safe" time in milliseconds since epoch without settings object w3c/hr-time#165 (5 comments by @annevk, @yoavweiss)
-
-
3 pull requests opened.
-
change: Update 'relative high resolution time' to use the principal realm. w3c/hr-time#168, by @Ms2ger.
-
Rename one of the "current wall time" dfns w3c/hr-time#167, by @yoavweiss.
-
Add a coarsening function for render timestamps w3c/hr-time#166, by @noamr.
-
-
1 pull request merged.
-
Rename one of the "current wall time" dfns w3c/hr-time#167.
-
-
2 pull requests received 5 new comments.
-
change: Update 'relative high resolution time' to use the principal realm. w3c/hr-time#168 (4 comments by @annevk, @noamr)
-
w3c/paint-timing
-
2 issues closed.
-
Timestamps should be specified in an interoperative way w3c/paint-timing#62.
-
Consider to expose decoding time for FCP and LCP? w3c/paint-timing#104.
-
-
1 issue reopened.
-
Timestamps should be specified in an interoperative way w3c/paint-timing#62, by @yoavweiss.
-
-
1 issue received 6 new comments.
-
Timestamps should be specified in an interoperative way w3c/paint-timing#62 (6 comments by @mstange, @noamr, @smfr, @yoavweiss)
-
-
5 pull requests opened.
-
Queue the long animation frame entry when presentation is ready w3c/paint-timing#109, by @noamr.
-
Add `PaintTimingMixin`, exposing interoperable + implementation defined paint timestamps w3c/paint-timing#108, by @noamr.
-
Update presentation-timestamps.md to include security & privacy w3c/paint-timing#107, by @noamr.
-
Create presentation-timestamps explainer w3c/paint-timing#106, by @noamr.
-
Remove TAO check from element timing & LCP reporting w3c/paint-timing#105, by @noamr.
-
-
5 pull requests merged.
-
Queue the long animation frame entry when presentation is ready w3c/paint-timing#109.
-
Update presentation-timestamps.md to include security & privacy w3c/paint-timing#107.
-
Add `PaintTimingMixin`, exposing interoperable + implementation defined paint timestamps w3c/paint-timing#108.
-
Create presentation-timestamps explainer w3c/paint-timing#106.
-
Remove TAO check from element timing & LCP reporting w3c/paint-timing#105.
-
-
4 pull requests received 21 new comments.
-
Update presentation-timestamps.md to include security & privacy w3c/paint-timing#107 (6 comments by @clelland, @noamr)
-
Add `PaintTimingMixin`, exposing interoperable + implementation defined paint timestamps w3c/paint-timing#108 (4 comments by @clelland, @noamr)
-
Queue the long animation frame entry when presentation is ready w3c/paint-timing#109 (1 comment by @noamr)
w3c/long-animation-frames
-
1 issue opened.
-
Feature Request: Summary of script-attribution for non-attributed scripts w3c/long-animation-frames#23, by @mmocny.
-
-
2 issues received 5 new comments.
-
Opaque attribution for extensions w3c/long-animation-frames#10 (3 comments by @andydavies, @mmocny, @noamr)
-
[LoAF] Use `sourceLine` and `sourceColumn` instead of `sourceCharPosition` for attribution w3c/long-animation-frames#16 (2 comments by @Miz85, @noamr)
-
-
2 pull requests opened.
-
Add hooks for `PaintTimingMixin` w3c/long-animation-frames#22, by @noamr.
-
Update user-defined-script-entry-point-explainer.md w3c/long-animation-frames#21, by @mmocny.
-
-
2 pull requests merged.
-
Add hooks for `PaintTimingMixin` w3c/long-animation-frames#22.
-
Update user-defined-script-entry-point-explainer.md w3c/long-animation-frames#21.
-
-
2 pull requests received 7 new comments.
-
Update user-defined-script-entry-point-explainer.md w3c/long-animation-frames#21 (1 comment by @brendankenny)
w3c/reporting
-
1 issue opened.
-
Generate Test Report: cannot check if something is a JSON object w3c/reporting#273, by @annevk.
-
-
1 issue received 1 new comment.
-
`process header` algorithm references undefined fetch response HTTPS state w3c/reporting#272 (1 comment by @clelland)
-
w3c/largest-contentful-paint
-
1 issue received 1 new comment.
-
Expose LCP renderTime in non-TAO cross-origin images, when it doesn't reflect the image decoding time w3c/largest-contentful-paint#91 (1 comment by @mmocny)
-
-
1 pull request opened.
-
Integrate with `PaintTimingMixin` w3c/largest-contentful-paint#126, by @noamr.
-
-
1 pull request merged.
-
Integrate with `PaintTimingMixin` w3c/largest-contentful-paint#126.
-
w3c/element-timing
-
2 pull requests opened.
-
Inclujde `PaintMixin` in `PerformanceElementTiming` w3c/element-timing#81, by @noamr.
-
Revise security and privacy section to remove TAO w3c/element-timing#80, by @noamr.
-
-
2 pull requests received 4 new comments.
-
Inclujde `PaintMixin` in `PerformanceElementTiming` w3c/element-timing#81 (2 comments by @clelland, @noamr)
-
Revise security and privacy section to remove TAO w3c/element-timing#80 (2 comments by @noamr, @yoavweiss)
-
w3c/resource-timing
-
1 issue closed.
-
Consider adding finalResponseHeaders{Start|End} times w3c/resource-timing#345.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Update timestamp SVG w3c/resource-timing#410, by @tunetheweb.
-
Add finalResponseHeadersStart which is always the 2xx/4xx/5xx response. w3c/resource-timing#408, by @noamr.
-
-
2 pull requests merged.
-
Update timestamp SVG w3c/resource-timing#410.
-
Add finalResponseHeadersStart which is always the 2xx/4xx/5xx response. w3c/resource-timing#408.
-
-
2 pull requests received 10 new comments.
-
Add finalResponseHeadersStart which is always the 2xx/4xx/5xx response. w3c/resource-timing#408 (9 comments by @LPardue, @noamr, @tunetheweb, @yoavweiss)
-
w3c/resource-timing#409 (1 comment by @w3cbot)
-
w3c/navigation-timing
-
1 pull request opened.
-
Update diagram to add finalResponseHeadersStart w3c/navigation-timing#205, by @tunetheweb.
-
-
1 pull request merged.
-
Update diagram to add finalResponseHeadersStart w3c/navigation-timing#205.
-
TR publications
-
1 document published.
-
User Timing published as a Candidate Recommendation Draft. History of User Timing
-
Participants
-
2 participants joined.
-
Sergey Chernyshev (Cloudflare) joined.
-
Victor Huang (Microsoft Corporation) joined.
-
GitHub
w3c/resource-timing
-
1 issue received 11 new comments.
-
Consider adding finalResponseHeaders{Start|End} times w3c/resource-timing#345 (11 comments by @Krinkle, @noamr, @tunetheweb)
-
-
1 pull request opened.
-
Create SECURITY.md w3c/resource-timing#407, by @Soonerseye.
-
-
1 pull request closed.
-
Create SECURITY.md w3c/resource-timing#407.
-
w3c/user-timing
-
1 pull request opened.
-
Remove level w3c/user-timing#114, by @deniak.
-
-
1 pull request merged.
-
Remove level w3c/user-timing#114.
-
-
1 pull request received 2 new comments.
w3c/long-animation-frames
-
1 issue opened.
-
Include some garbage collection information w3c/long-animation-frames#20, by @aluhrs13.
-
-
1 issue received 1 new comment.
w3c/largest-contentful-paint
-
1 issue opened.
-
[quesion] Strange PerformanceObserver API Judgment of LCP Elements w3c/largest-contentful-paint#125, by @electroluxcode.
-
-
1 issue closed.
-
[quesion] Strange PerformanceObserver API Judgment of LCP Elements w3c/largest-contentful-paint#125.
-
-
2 issues received 5 new comments.
-
[quesion] Strange PerformanceObserver API Judgment of LCP Elements w3c/largest-contentful-paint#125 (3 comments by @electroluxcode, @mmocny)
-
-
1 pull request opened.
-
Exclude Transparent Texts From Being Eligible LCP Candidate w3c/largest-contentful-paint#124, by @haoliuk.
-
-
1 pull request merged.
-
Exclude Transparent Texts From Being Eligible LCP Candidate w3c/largest-contentful-paint#124.
-
-
1 pull request received 3 new comments.
-
Exclude Transparent Texts From Being Eligible LCP Candidate w3c/largest-contentful-paint#124 (3 comments by @clelland, @haoliuk)
-
w3c/server-timing
-
1 issue received 3 new comments.
-
add start time to distinguish between cached and active entries w3c/server-timing#43 (3 comments by @LPardue, @paulirish)
-
w3c/event-timing
-
1 issue received 1 new comment.
w3c/web-performance
-
1 issue received 1 new comment.
w3c/network-error-logging
-
2 issues received 2 new comments.
-
Network failures after connection establishment w3c/network-error-logging#176 (1 comment by @nicjansma)
w3c/paint-timing
-
1 issue received 2 new comments.
w3c/reporting
-
1 issue opened.
-
`process header` algorithm references undefined fetch response HTTPS state w3c/reporting#272, by @simonwuelker.
-
w3c/performance-timeline
-
1 issue received 1 new comment.
-
`droppedEntriesCount` can be inconsistent with reported entries w3c/performance-timeline#214 (1 comment by @clelland)
-
Past meetings
Participants
-
7 participants joined.
-
Jose Dapena Paz (Igalia) joined.
-
Ling Zhong (Microsoft Corporation) joined.
-
Guohui Deng (Microsoft Corporation) joined.
-
Limin Zhu (Microsoft Corporation) joined.
-
TIEN MAI (Microsoft Corporation) joined.
-
Fabio Rocha (Microsoft Corporation) joined.
-
Nishitha Dey (Microsoft Corporation) joined.
-
-
1 participant left.
-
Shubhie Panicker (Google LLC) left.
-
GitHub
w3c/resource-timing
-
4 issues received 4 new comments.
-
Consider adding finalResponseHeaders{Start|End} times w3c/resource-timing#345 (1 comment by @tunetheweb)
-
Why is there noticeable gap between requestStart and connectEnd? w3c/resource-timing#365 (1 comment by @HduSy)
-
w3c/largest-contentful-paint
-
1 issue received 1 new comment.
-
Hover-based user input is often used for "zoom widgets", skewing LCP results w3c/largest-contentful-paint#108 (1 comment by @krzksz)
-
w3c/web-performance
-
1 issue received 2 new comments.
-
Outdated links in header of working group home page w3c/web-performance#61 (2 comments by @davehunt, @nicjansma)
-
w3c/performance-timeline
-
1 issue opened.
-
`droppedEntriesCount` can be inconsistent with reported entries w3c/performance-timeline#214, by @rubennorte.
-
w3c/hr-time
-
1 issue received 3 new comments.
-
"safe" time in milliseconds since epoch without settings object w3c/hr-time#165 (3 comments by @annevk, @yoavweiss)
-
w3c/event-timing
-
1 issue opened.
-
Consider removing pointermove (and interactionType and pointerIsDragSet) w3c/event-timing#140, by @mmocny.
-
-
1 issue received 1 new comment.
w3c/network-error-logging
-
1 issue received 1 new comment.
w3c/navigation-timing
-
1 issue closed.
-
Enum values that ignore naming conventions in Navigation Timing Level 2 w3c/navigation-timing#204.
-
-
1 issue received 1 new comment.
-
Enum values that ignore naming conventions in Navigation Timing Level 2 w3c/navigation-timing#204 (1 comment by @clelland)
-
w3c/long-animation-frames
-
1 issue received 1 new comment.
-
pauseDuration is 0 while synchronous dialogs are shown w3c/long-animation-frames#17 (1 comment by @mmocny)
-
TR publications
-
3 documents published.
-
Event Timing API published as a Working Draft. History of Event Timing API
-
Reporting API published twice as a Working Draft. History of Reporting API
-
Participants
-
3 participants joined.
-
Shouqun Liu (ByteDance) joined.
-
Ben Michel (Datadog) joined.
-
Tim Kadlec (W3C Invited Experts) joined.
-
GitHub
w3c/navigation-timing
-
1 issue opened.
-
Enum values that ignore naming conventions in Navigation Timing Level 2 w3c/navigation-timing#204, by @dontcallmedom-bot.
-
-
1 issue received 16 new comments.
-
Add `confidence` field to PerformanceNavigationTiming w3c/navigation-timing#202 (16 comments by @csharrison, @mwjacksonmsft, @noamr, @yoavweiss)
-
-
1 pull request opened.
-
Support ReSpec dark mode. w3c/navigation-timing#203, by @clelland.
-
-
1 pull request merged.
-
Support ReSpec dark mode. w3c/navigation-timing#203.
-
w3c/event-timing
-
1 issue opened.
-
Consider evolving "first-input" to "first interaction" w3c/event-timing#139, by @mmocny.
-
-
3 issues closed.
-
Provide more explanatory material in processing model w3c/event-timing#51.
-
Support for mousemove and other continuous events w3c/event-timing#99.
-
Fix spec build issues w3c/event-timing#135.
-
-
7 issues received 8 new comments.
-
Proposal: DOM event identifier which can map to EventTimingPerformance entry w3c/event-timing#108 (1 comment by @mmocny)
-
1 pull request opened.
-
Fix Event Timing build errors w3c/event-timing#138, by @mmocny.
-
-
1 pull request merged.
-
Fix Event Timing build errors w3c/event-timing#138.
-
w3c/server-timing
-
1 issue opened.
-
Normative references to discontinued specs in Server Timing w3c/server-timing#98, by @dontcallmedom-bot.
-
-
1 issue received 1 new comment.
-
Normative references to discontinued specs in Server Timing w3c/server-timing#98 (1 comment by @clelland)
-
-
1 pull request opened.
-
Support ReSpec dark mode. w3c/server-timing#99, by @clelland.
-
-
1 pull request merged.
-
Support ReSpec dark mode. w3c/server-timing#99.
-
-
1 pull request closed.
-
Add `[SecureContext]` tag to the interface w3c/server-timing#94.
-
-
1 pull request received 1 new comment.
w3c/user-timing
-
2 pull requests opened.
-
Support ReSpec dark mode. w3c/user-timing#113, by @clelland.
-
Create conditional-tracing-explainer.md w3c/user-timing#112, by @noamr.
-
-
1 pull request merged.
-
Support ReSpec dark mode. w3c/user-timing#113.
-
w3c/resource-timing
-
2 issues opened.
-
Normative references to discontinued specs in Resource Timing w3c/resource-timing#404, by @dontcallmedom-bot.
-
Inconsistent "response body info" vs "resource info" names w3c/resource-timing#403, by @arai-a.
-
-
1 issue closed.
-
Normative references to discontinued specs in Resource Timing w3c/resource-timing#404.
-
-
4 issues received 5 new comments.
-
Adding HTTP method to ResourceTiming API structure w3c/resource-timing#373 (2 comments by @drit, @nicjansma)
-
Normative references to discontinued specs in Resource Timing w3c/resource-timing#404 (1 comment by @clelland)
-
Inconsistent "response body info" vs "resource info" names w3c/resource-timing#403 (1 comment by @clelland)
-
Expose a way to link a call to fetch to an individual PerformanceResourceTiming object w3c/resource-timing#102 (1 comment by @sophiebits)
-
-
2 pull requests opened.
-
Fix broken reference to RFC7230 w3c/resource-timing#406, by @clelland.
-
Support ReSpec dark mode. w3c/resource-timing#405, by @clelland.
-
-
2 pull requests merged.
-
Support ReSpec dark mode. w3c/resource-timing#405.
-
Fix broken reference to RFC7230 w3c/resource-timing#406.
-
w3c/performance-timeline
-
1 pull request opened.
-
Support ReSpec dark mode. w3c/performance-timeline#213, by @clelland.
-
-
1 pull request merged.
-
Support ReSpec dark mode. w3c/performance-timeline#213.
-
w3c/network-error-logging
-
1 issue opened.
-
Normative references to discontinued specs in Network Error Logging w3c/network-error-logging#177, by @dontcallmedom-bot.
-
-
1 pull request opened.
-
Support ReSpec dark mode. w3c/network-error-logging#178, by @clelland.
-
-
1 pull request merged.
-
Support ReSpec dark mode. w3c/network-error-logging#178.
-
w3c/timing-entrytypes-registry
-
1 pull request opened.
-
Correct LOAF spec link w3c/timing-entrytypes-registry#19, by @clelland.
-
w3c/hr-time
-
1 issue opened.
-
"safe" time in milliseconds since epoch without settings object w3c/hr-time#165, by @annevk.
-
w3c/long-animation-frames
-
3 issues opened.
-
firstUIEventTimestamp not set to the first event start time w3c/long-animation-frames#19, by @rviscomi.
-
Chrome extension script included in LoAF entry w3c/long-animation-frames#18, by @rviscomi.
-
pauseDuration is 0 while synchronous dialogs are shown w3c/long-animation-frames#17, by @rviscomi.
-
-
1 issue closed.
-
Chrome extension script included in LoAF entry w3c/long-animation-frames#18.
-
-
3 issues received 8 new comments.
-
pauseDuration is 0 while synchronous dialogs are shown w3c/long-animation-frames#17 (4 comments by @mmocny, @rviscomi)
-
Chrome extension script included in LoAF entry w3c/long-animation-frames#18 (3 comments by @mmocny, @rviscomi)
-
firstUIEventTimestamp not set to the first event start time w3c/long-animation-frames#19 (1 comment by @mmocny)
-
w3c/reporting
-
2 pull requests opened.
-
Editorial: Fix bikeshed errors over ambiguous link. w3c/reporting#271, by @clelland.
-
Editorial: Update use of WebIDL "invoke a callback function" w3c/reporting#270, by @jeremyroman.
-
-
2 pull requests merged.
-
Editorial: Update use of WebIDL "invoke a callback function" w3c/reporting#270.
-
Editorial: Fix bikeshed errors over ambiguous link. w3c/reporting#271.
-
-
1 pull request received 4 new comments.
-
Editorial: Update use of WebIDL "invoke a callback function" w3c/reporting#270 (4 comments by @clelland, @jeremyroman)
-
w3c/element-timing
-
1 issue received 1 new comment.
w3c/largest-contentful-paint
-
1 issue received 2 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 (2 comments by @mmocny)
-
TR publications
-
1 document published.
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Participants
-
4 participants joined.
-
Jason Williams (Bloomberg) joined.
-
Bas Schouten (Mozilla Foundation) joined.
-
Dave Hunt (Mozilla Foundation) joined.
-
Benoit Zugmeyer (Datadog) joined.
-
-
1 organization joined.
-
Bloomberg joined.
-
GitHub
w3c/reporting
-
1 issue opened.
-
CSP Report Does Not Reflect Redirected Blocked Domains w3c/reporting#269, by @ConardLi.
-
-
1 issue closed.
-
CSP Report Does Not Reflect Redirected Blocked Domains w3c/reporting#269.
-
-
3 issues received 4 new comments.
-
Clarifying behavior when both Reporting-Endpoints and Report-To headers are provided? w3c/reporting#267 (1 comment by @wille)
w3c/user-timing
-
1 issue opened.
-
2 issues received 3 new comments.
-
Add a standard track/category field to the spec w3c/user-timing#109 (2 comments by @and-oli, @bgirard)
-
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 @clelland)
-
w3c/network-error-logging
-
2 issues opened.
-
Network failures after connection establishment w3c/network-error-logging#176, by @enygren.
-
"Happy Eyeballs" failure reporting w3c/network-error-logging#175, by @enygren.
-
-
3 issues received 7 new comments.
-
"Happy Eyeballs" failure reporting w3c/network-error-logging#175 (5 comments by @clelland, @LPardue, @pmeenan, @simon-friedberger)
-
w3c/navigation-timing
-
1 issue received 1 new comment.
-
Add `confidence` field to PerformanceNavigationTiming w3c/navigation-timing#202 (1 comment by @mwjacksonmsft)
-
-
1 pull request merged.
-
Fix `firstInterimResponseStart` name on diagram w3c/navigation-timing#200.
-
-
1 pull request received 1 new comment.
-
Fix `firstInterimResponseStart` name on diagram w3c/navigation-timing#200 (1 comment by @tunetheweb)
-
w3c/long-animation-frames
-
3 issues received 21 new comments.
-
[LoAF] Allow for annotations for long animation frame to further help debugging w3c/long-animation-frames#3 (16 comments by @mmocny, @noamr, @rviscomi)
-
[LoAF] Use `sourceLine` and `sourceColumn` instead of `sourceCharPosition` for attribution w3c/long-animation-frames#16 (4 comments by @Miz85, @mmocny, @noamr)
-
Provide some source information for scripts without source information w3c/long-animation-frames#11 (1 comment by @proofyman)
-
w3c/paint-timing
-
1 issue received 3 new comments.
-
Timestamps should be specified in an interoperative way w3c/paint-timing#62 (3 comments by @mmocny, @noamr)
-
w3c/resource-timing
-
3 issues received 3 new comments.
-
How to get correct connectStart/End, domainLookupStart/End value when service worker is enabled? w3c/resource-timing#363 (1 comment by @noamr)
-
Adding resource discovery time to ResourceTiming API structure w3c/resource-timing#374 (1 comment by @meetsuraj)
-
Adding HTTP method to ResourceTiming API structure w3c/resource-timing#373 (1 comment by @meetsuraj)
-
Participants
-
1 participant joined.
-
Rick Klein (Datadog) joined.
-
-
1 organization joined.
-
Datadog joined.
-
GitHub
w3c/long-animation-frames
-
2 issues opened.
-
[LoAF] Use `sourceLine` and `sourceColumn` instead of `sourceCharPosition` for attribution w3c/long-animation-frames#16, by @Miz85.
-
Should LoAF emit when there is a long blocking task but no "paint" w3c/long-animation-frames#14, by @tunetheweb.
-
-
4 issues received 15 new comments.
-
More informations about the source of user-callback and event-listener scripts w3c/long-animation-frames#12 (6 comments by @jinja12, @noamr, @tunetheweb)
-
[LoAF] Use `sourceLine` and `sourceColumn` instead of `sourceCharPosition` for attribution w3c/long-animation-frames#16 (4 comments by @Miz85, @mmocny)
-
Should LoAF emit when there is a long blocking task but no "paint" w3c/long-animation-frames#14 (4 comments by @mmocny, @tunetheweb)
-
Ambiguous behaviour in Attribution data on Mobile device with no CPU Throttling w3c/long-animation-frames#13 (1 comment by @jinja12)
-
-
1 pull request opened.
-
Fix typo w3c/long-animation-frames#15, by @martinthomson.
-
-
1 pull request merged.
-
Fix typo w3c/long-animation-frames#15.
-
w3c/navigation-timing
-
1 issue opened.
-
Add `confidence` field to PerformanceNavigationTiming w3c/navigation-timing#202, by @mwjacksonmsft.
-
-
1 issue closed.
-
Extend 'NavigationType' to include User Agent Launch w3c/navigation-timing#180.
-
-
2 issues received 20 new comments.
-
Add `confidence` field to PerformanceNavigationTiming w3c/navigation-timing#202 (18 comments by @clelland, @csharrison, @ear-dev, @mmocny, @mwjacksonmsft, @nicjansma, @yoavweiss)
-
Extend 'NavigationType' to include User Agent Launch w3c/navigation-timing#180 (2 comments by @clelland, @mwjacksonmsft)
-
w3c/web-performance
-
1 issue opened.
-
Outdated links in header of working group home page w3c/web-performance#61, by @davehunt.
-
-
1 pull request opened.
-
Fix typo in description of Timing Entry Names Registry entry w3c/web-performance#60, by @davehunt.
-
-
1 pull request merged.
-
Fix typo in description of Timing Entry Names Registry entry w3c/web-performance#60.
-
-
1 pull request received 1 new comment.
-
Fix typo in description of Timing Entry Names Registry entry w3c/web-performance#60 (1 comment by @clelland)
-
w3c/resource-timing
-
2 issues reopened.
-
Améthyst pierre magique pour la sagesse et l'intelligence. w3c/resource-timing#396, by @hamadilubinga.
-
https://github.com/users/hamadilubinga/achievements/quickdrawTora3 w3c/resource-timing#392, by @hamadilubinga.
-
-
2 issues received 3 new comments.
-
How to get correct connectStart/End, domainLookupStart/End value when service worker is enabled? w3c/resource-timing#363 (2 comments by @noamr, @tunetheweb)
-
Add service worker static routing API information to resource timing w3c/resource-timing#389 (1 comment by @nicjansma)
-
w3c/largest-contentful-paint
-
1 issue opened.
-
LCP behavior with dialogs w3c/largest-contentful-paint#123, by @ofirelarat.
-
-
1 issue closed.
-
LCP behavior with dialogs w3c/largest-contentful-paint#123.
-
-
1 issue received 4 new comments.
-
LCP behavior with dialogs w3c/largest-contentful-paint#123 (4 comments by @ofirelarat, @pmeenan, @tunetheweb)
-
w3c/user-timing
-
1 issue opened.
-
Extending 'Recommended mark names' to allow user agents to detect media timeouts w3c/user-timing#110, by @sushraja-msft.
-
-
1 issue received 1 new comment.
-
Extending 'Recommended mark names' to allow user agents to detect media timeouts w3c/user-timing#110 (1 comment by @nicjansma)
-
TR publications
-
2 documents published.
-
Resource Timing published as a Candidate Recommendation Draft. History of Resource Timing
-
Long Tasks API published as a Working Draft. History of Long Tasks API
-
GitHub
w3c/long-animation-frames
-
1 issue opened.
-
Ambiguous behaviour in Attribution data on Mobile device with no CPU Throttling w3c/long-animation-frames#13, by @jinja12.
-
-
2 issues received 10 new comments.
-
Ambiguous behaviour in Attribution data on Mobile device with no CPU Throttling w3c/long-animation-frames#13 (9 comments by @jinja12, @mmocny, @tunetheweb)
-
More informations about the source of user-callback and event-listener scripts w3c/long-animation-frames#12 (1 comment by @mmocny)
-
w3c/event-timing
-
1 issue closed.
-
How does Event Timing API relate to/overlap with Long Tasks API? w3c/event-timing#122.
-
-
1 issue received 1 new comment.
-
How does Event Timing API relate to/overlap with Long Tasks API? w3c/event-timing#122 (1 comment by @mmocny)
-
w3c/resource-timing
-
1 issue opened.
-
Add service worker static routing API information to resource timing w3c/resource-timing#389, by @sisidovski.
-
-
1 issue closed.
-
Broken references in Resource Timing w3c/resource-timing#376.
-
-
1 issue received 1 new comment.
-
How to get correct connectStart/End, domainLookupStart/End value when service worker is enabled? w3c/resource-timing#363 (1 comment by @nicjansma)
-
-
1 pull request opened.
-
Fix broken references w3c/resource-timing#390, by @clelland.
-
-
1 pull request merged.
-
Fix broken references w3c/resource-timing#390.
-
-
2 pull requests received 5 new comments.
-
w3c/resource-timing#391 (1 comment by @w3cbot)
w3c/user-timing
-
1 issue received 6 new comments.
-
Add a standard track/category field to the spec w3c/user-timing#109 (6 comments by @and-oli, @bgirard)
-
w3c/largest-contentful-paint
-
1 issue opened.
-
How should text overflow be handled? w3c/largest-contentful-paint#122, by @tunetheweb.
-
-
1 pull request received 1 new comment.
w3c/server-timing
-
1 issue closed.
-
Broken references in Server Timing w3c/server-timing#96.
-
-
1 pull request opened.
-
Fix broken reference w3c/server-timing#97, by @clelland.
-
-
1 pull request merged.
-
Fix broken reference w3c/server-timing#97.
-
w3c/longtasks
-
1 issue closed.
-
Broken references in Long Tasks API w3c/longtasks#108.
-
-
1 pull request opened.
-
Fix broken references w3c/longtasks#141, by @clelland.
-
-
1 pull request merged.
-
Fix broken references w3c/longtasks#141.
-
-
1 pull request received 2 new comments.
w3c/performance-timeline
-
1 issue received 7 new comments.
-
`PerformanceObserver.supportedEntryTypes`can't be annotated with `[SameObject]` w3c/performance-timeline#212 (7 comments by @clelland, @tunetheweb, @yoavweiss)
-
w3c/beacon
-
1 issue opened.
-
1 issue received 1 new comment.
-
Chrome, Safari and Firefox behave differently when beacon blocked by CSP w3c/beacon#82 (1 comment by @clelland)
-
w3c/paint-timing
-
1 issue received 1 new comment.
w3c/network-error-logging
-
1 pull request opened.
-
Balance the brackets w3c/network-error-logging#174, by @peternewman.
-
-
1 pull request received 2 new comments.
w3c/navigation-timing
-
1 issue opened.
-
"Create a NotRestoredReasons object" takes a realm, but "create the navigation timing entry" doesn't pass it w3c/navigation-timing#201, by @petervanderbeken.
-
-
1 pull request opened.
-
Fix `firstInterimResponseStart` name on diagram w3c/navigation-timing#200, by @tunetheweb.
-
-
1 pull request received 2 new comments.
-
Fix `firstInterimResponseStart` name on diagram w3c/navigation-timing#200 (2 comments by @tunetheweb, @yoavweiss)
-
TR publications
-
2 documents published.
-
Resource Timing published twice as a Candidate Recommendation Draft. History of Resource Timing
-
Participants
-
1 participant joined.
-
Mirjana Andovska (Netcetera) joined.
-
-
1 organization joined.
-
Netcetera joined.
-
GitHub
w3c/largest-contentful-paint
-
2 issues received 2 new comments.
-
requestAnimationFrame callback and LCP renderTime should be the same w3c/largest-contentful-paint#104 (1 comment by @noamr)
-
Hover-based user input is often used for "zoom widgets", skewing LCP results w3c/largest-contentful-paint#108 (1 comment by @Coiven)
-
-
1 pull request received 3 new comments.
w3c/resource-timing
-
1 issue opened.
-
Should data: urls be reported in resource timing? w3c/resource-timing#386, by @clelland.
-
-
1 issue closed.
-
Should data: urls be reported in resource timing? w3c/resource-timing#386.
-
-
2 issues received 6 new comments.
-
Should data: urls be reported in resource timing? w3c/resource-timing#386 (4 comments by @clelland, @noamr)
-
How to get correct connectStart/End, domainLookupStart/End value when service worker is enabled? w3c/resource-timing#363 (2 comments by @noamr, @tunetheweb)
-
-
1 pull request opened.
-
Correct clarification for data: URIs w3c/resource-timing#387, by @noamr.
-
-
1 pull request merged.
-
Correct clarification for data: URIs w3c/resource-timing#387.
-
-
1 pull request received 1 new comment.
-
w3c/resource-timing#388 (1 comment by @w3cbot)
-
w3c/event-timing
-
2 issues received 2 new comments.
-
Add `targetSelector` attribute to Event Timing API (for cases where target is detached) w3c/event-timing#126 (1 comment by @mmocny)
-
-
1 pull request closed.
-
Fix #135 remove empty attribute w3c/event-timing#136.
-
w3c/paint-timing
-
1 issue opened.
-
Consider to expose decoding time for FCP and LCP? w3c/paint-timing#104, by @sefeng211.
-
-
2 issues received 6 new comments.
-
Timestamps should be specified in an interoperative way w3c/paint-timing#62 (5 comments by @anniesullie, @mmocny, @noamr, @smfr)
-
w3c/performance-timeline
-
1 issue opened.
-
`PerformanceObserver.supportedEntryTypes`can't be annotated with `[SameObject]` w3c/performance-timeline#212, by @petervanderbeken.
-
w3c/navigation-timing
-
1 issue opened.
-
Timing values are inconsistent across browsers when page is controlled by service worker w3c/navigation-timing#199, by @philipwalton.
-
w3c/reporting
-
1 issue received 1 new comment.
w3c/longtasks
-
1 issue closed.
-
Generic model for causal attribution (non-sampling based) w3c/longtasks#89.
-
-
1 issue received 1 new comment.
w3c/long-animation-frames
-
1 issue opened.
-
More informations about the source of user-callback and event-listener scripts w3c/long-animation-frames#12, by @rackaam.
-
-
1 issue received 1 new comment.
-
Provide some source information for scripts without source information w3c/long-animation-frames#11 (1 comment by @noamr)
-
w3c/server-timing
-
1 issue opened.
-
Broken references in Server Timing w3c/server-timing#96, by @dontcallmedom-bot.
-
TR publications
-
3 documents published.
-
Long Tasks API published as a Working Draft. History of Long Tasks API
-
Navigation Timing Level 2 published twice as a Working Draft. History of Navigation Timing Level 2
-
Participants
-
1 participant joined.
-
Kenichi Ishibashi (Google LLC) joined.
-
GitHub
w3c/long-animation-frames
-
2 issues opened.
-
Provide some source information for scripts without source information w3c/long-animation-frames#11, by @noamr.
-
Opaque attribution for extensions w3c/long-animation-frames#10, by @rviscomi.
-
-
2 issues received 2 new comments.
-
[LoAF] Allow for annotations for long animation frame to further help debugging w3c/long-animation-frames#3 (1 comment by @patrickhousley)
-
w3c/timing-entrytypes-registry
-
2 issues opened.
-
Missing `visibility-state` entry type w3c/timing-entrytypes-registry#18, by @Lubrsi.
-
Broken references in Timing Entry Names Registry w3c/timing-entrytypes-registry#17, by @dontcallmedom-bot.
-
w3c/resource-timing
-
2 issues received 4 new comments.
-
Expose Content-Encoding to ResourceTiming w3c/resource-timing#381 (3 comments by @horo-t, @Jxck, @nicjansma)
-
Should `firstInterimResponseStart` show 0 when there is no interim response? w3c/resource-timing#382 (1 comment by @nicjansma)
-
-
1 pull request opened.
-
Expose Content-Encoding to resource-timing w3c/resource-timing#385, by @Jxck.
-
-
1 pull request received 2 new comments.
w3c/navigation-timing
-
1 issue opened.
-
"Process Unload Event" in wrong place on timing diagram w3c/navigation-timing#197, by @tunetheweb.
-
-
1 issue closed.
-
"Process Unload Event" in wrong place on timing diagram w3c/navigation-timing#197.
-
-
2 issues received 2 new comments.
-
Proposal: add timestamp for when "activation" or "dismissal" starts w3c/navigation-timing#193 (1 comment by @nicjansma)
-
"Process Unload Event" in wrong place on timing diagram w3c/navigation-timing#197 (1 comment by @tunetheweb)
-
-
1 pull request opened.
-
Update diagram to better reflect unload timing w3c/navigation-timing#198, by @noamr.
-
-
2 pull requests merged.
-
Update diagram to better reflect unload timing w3c/navigation-timing#198.
-
Add notRestoredReasons to PerformanceNavigationTiming attribute w3c/navigation-timing#195.
-
w3c/server-timing
-
1 issue received 1 new comment.
-
PerformanceServerTiming entry always has a duration field even when the original header did not w3c/server-timing#95 (1 comment by @nicjansma)
-
w3c/longtasks
-
1 issue closed.
-
Consider to have a separate spec for Long Animation Frame API w3c/longtasks#132.
-
-
1 issue received 1 new comment.
-
Consider to have a separate spec for Long Animation Frame API w3c/longtasks#132 (1 comment by @caribouW3)
-
-
2 pull requests opened.
-
Update loaf-explainer.md to link to new repo w3c/longtasks#139, by @noamr.
-
Remove loaf, it's in its own repo w3c/longtasks#138, by @noamr.
-
-
2 pull requests merged.
-
Update loaf-explainer.md to link to new repo w3c/longtasks#139.
-
Remove loaf, it's in its own repo w3c/longtasks#138.
-
-
1 pull request reopened.
-
Update loaf-explainer.md to link to new repo w3c/longtasks#139, by @noamr.
-
TR publications
-
5 documents published.
-
Performance Timeline published twice as a Candidate Recommendation Draft. History of Performance Timeline
-
Resource Timing published as a Candidate Recommendation Draft. History of Resource Timing
-
Long Tasks API published as a Working Draft. History of Long Tasks API
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
GitHub
w3c/resource-timing
-
1 issue closed.
-
Should `firstInterimResponseStart` show 0 when there is no interim response? w3c/resource-timing#382.
-
-
3 issues received 5 new comments.
-
Should `firstInterimResponseStart` show 0 when there is no interim response? w3c/resource-timing#382 (2 comments by @tunetheweb)
-
-
1 pull request opened.
-
WebIDL fix: initialize PerformanceEntry instead of shadowing w3c/resource-timing#383, by @noamr.
-
-
1 pull request merged.
-
WebIDL fix: initialize PerformanceEntry instead of shadowing w3c/resource-timing#383.
-
-
2 pull requests received 3 new comments.
-
WebIDL fix: initialize PerformanceEntry instead of shadowing w3c/resource-timing#383 (2 comments by @clelland, @noamr)
-
w3c/resource-timing#384 (1 comment by @w3cbot)
-
w3c/largest-contentful-paint
-
1 issue received 2 new comments.
-
Hover-based user input is often used for "zoom widgets", skewing LCP results w3c/largest-contentful-paint#108 (2 comments by @Santas, @yoavweiss)
-
w3c/network-error-logging
-
1 issue received 1 new comment.
w3c/navigation-timing
-
1 pull request opened.
-
Use correct ref for queuing w3c/navigation-timing#196, by @noamr.
-
-
1 pull request merged.
-
Use correct ref for queuing w3c/navigation-timing#196.
-
-
1 pull request reopened.
-
Add notRestoredReasons to PerformanceNavigationTiming attribute w3c/navigation-timing#195, by @noamr.
-
-
1 pull request received 3 new comments.
-
Add notRestoredReasons to PerformanceNavigationTiming attribute w3c/navigation-timing#195 (3 comments by @rubberyuzu, @smaug----)
-
w3c/server-timing
-
1 issue opened.
-
PerformanceServerTiming entry always has a duration field even when the original header did not w3c/server-timing#95, by @andydavies.
-
-
1 issue received 2 new comments.
-
PerformanceServerTiming entry always has a duration field even when the original header did not w3c/server-timing#95 (2 comments by @andydavies, @clelland)
-
-
1 pull request opened.
-
Add `[SecureContext]` tag to the interface w3c/server-timing#94, by @OnkarRuikar.
-
-
1 pull request received 2 new comments.
-
Add `[SecureContext]` tag to the interface w3c/server-timing#94 (2 comments by @clelland, @OnkarRuikar)
-
w3c/reporting
-
1 issue opened.
-
Expected behavior for same-origin-cross-site reporting? w3c/reporting#268, by @freyalaluna.
-
-
1 issue closed.
-
Expected behavior for same-origin-cross-site reporting? w3c/reporting#268.
-
-
1 issue received 1 new comment.
w3c/longtasks
-
1 issue closed.
-
New proposal: long animation frames w3c/longtasks#103.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Fix type of sourceCharPosition attribute, and amend explainer w3c/longtasks#137, by @noamr.
-
-
1 pull request merged.
-
Fix type of sourceCharPosition attribute, and amend explainer w3c/longtasks#137.
-
-
1 pull request reopened.
-
Fix type of sourceCharPosition attribute, and amend explainer w3c/longtasks#137, by @noamr.
-
w3c/performance-timeline
-
1 issue closed.
-
"Queue a navigation performance entry" doesn't seem to be used w3c/performance-timeline#209.
-
-
1 pull request opened.
-
Export `end time` so that subclasses can change it w3c/performance-timeline#211, by @noamr.
-
-
2 pull requests merged.
-
Export `end time` so that subclasses can change it w3c/performance-timeline#211.
-
The common atttribute of `PerformanceEntry` should be initialized rat… w3c/performance-timeline#210.
-
-
2 pull requests received 4 new comments.
-
Export `end time` so that subclasses can change it w3c/performance-timeline#211 (2 comments by @clelland, @noamr)
-
The common atttribute of `PerformanceEntry` should be initialized rat… w3c/performance-timeline#210 (2 comments by @noamr)
-
w3c/element-timing
-
1 issue received 2 new comments.
w3c/user-timing
-
1 issue opened.
-
Add a standard track/category field to the spec w3c/user-timing#109, by @bgirard.
-
-
1 issue received 3 new comments.
-
Add a standard track/category field to the spec w3c/user-timing#109 (3 comments by @bgirard, @mmocny)
-
w3c/event-timing
-
1 issue closed.
-
Proposal: add more main thread activity information to PerformanceEventTiming entry w3c/event-timing#109.
-
-
1 issue received 4 new comments.
-
Proposal: add more main thread activity information to PerformanceEventTiming entry w3c/event-timing#109 (4 comments by @mmocny, @nhelfman, @noamr, @yoavweiss)
-
w3c/requestidlecallback
-
1 pull request opened.
-
fix: fixes code in example 1 w3c/requestidlecallback#102, by @guiseek.
-
TR publications
-
7 documents published.
-
Long Tasks API published 4 times as a Working Draft. History of Long Tasks API
-
Largest Contentful Paint published as a Working Draft. History of Largest Contentful Paint
-
Paint Timing published twice as a Working Draft. History of Paint Timing
-
Participants
-
1 chair appointed.
-
Yoav Weiss became a chair.
-
-
1 chair stepped down.
-
Yoav Weiss stepped down as a chair.
-
-
1 participant joined.
-
Yoav Weiss (Shopify) joined.
-
-
1 participant left.
-
Yoav Weiss (Shopify) left.
-
GitHub
w3c/long-animation-frames
-
3 issues opened.
-
The `sourceLocation` property of `PerformanceScriptTiming` is complex or ambiguous to parse w3c/long-animation-frames#6, by @philipwalton.
-
LoAF: `firstUIEventTimestamp` contains non-INP events w3c/long-animation-frames#1, by @tunetheweb.
-
[LoAF] Settle on what `PerformanceScriptTiming.name` means w3c/long-animation-frames#7, by @noamr.
-
-
2 issues closed.
-
The `sourceLocation` property of `PerformanceScriptTiming` is complex or ambiguous to parse w3c/long-animation-frames#6.
-
[LoAF] Settle on what `PerformanceScriptTiming.name` means w3c/long-animation-frames#7.
-
-
3 issues received 19 new comments.
-
[LoAF] Settle on what `PerformanceScriptTiming.name` means w3c/long-animation-frames#7 (10 comments by @aarontgrogg, @borisschapira, @lasseschou, @noamr)
-
LoAF: `firstUIEventTimestamp` contains non-INP events w3c/long-animation-frames#1 (6 comments by @anatdagan, @mmocny, @tunetheweb, @vanderhoop)
-
[LoAF] Should it be easier to link LoAF to INP entries w3c/long-animation-frames#5 (3 comments by @lebreRafael, @noamr, @vegerot)
-
w3c/longtasks
-
2 issues opened.
-
Overloading PerformanceEntry w3c/longtasks#133, by @Elchi3.
-
Consider to have a separate spec for Long Animation Frame API w3c/longtasks#132, by @sefeng211.
-
-
1 issue received 2 new comments.
-
Consider to have a separate spec for Long Animation Frame API w3c/longtasks#132 (2 comments by @caribouW3, @yoavweiss)
-
-
6 pull requests opened.
-
LongScriptTiming: break down source location to 3 attributes w3c/longtasks#136, by @noamr.
-
Add note about upstreaming monkey patches w3c/longtasks#131, by @noamr.
-
Update loaf-explainer.md w3c/longtasks#130, by @noamr.
-
Renames: use invoker/invokerType instead of name/type w3c/longtasks#129, by @noamr.
-
LoAF: add remaining script properties w3c/longtasks#128, by @noamr.
-
LoAF: Amend `blockingDuration` to match implementation w3c/longtasks#127, by @noamr.
-
-
7 pull requests merged.
-
LongScriptTiming: break down source location to 3 attributes w3c/longtasks#136.
-
LoAF: Amend `blockingDuration` to match implementation w3c/longtasks#127.
-
Add note about upstreaming monkey patches w3c/longtasks#131.
-
Update loaf-explainer.md w3c/longtasks#130.
-
Renames: use invoker/invokerType instead of name/type w3c/longtasks#129.
-
LoAF: add remaining script properties w3c/longtasks#128.
-
LoAF: add support for scripts w3c/longtasks#124.
-
-
4 pull requests received 38 new comments.
w3c/element-timing
-
1 issue received 2 new comments.
-
1 pull request merged.
-
Refactor Element Timing on top of Paint Timing w3c/element-timing#78.
-
-
1 pull request received 1 new comment.
w3c/largest-contentful-paint
-
3 issues closed.
-
What exactly does loadTime attribute mean? w3c/largest-contentful-paint#118.
-
Element Timing spec is still within WICG rather than W3 w3c/largest-contentful-paint#113.
-
Improve unimportant image heuristic w3c/largest-contentful-paint#86.
-
-
2 issues received 3 new comments.
-
What exactly does loadTime attribute mean? w3c/largest-contentful-paint#118 (2 comments by @clelland, @tunetheweb)
-
Element Timing spec is still within WICG rather than W3 w3c/largest-contentful-paint#113 (1 comment by @clelland)
-
-
1 pull request merged.
-
Rebase LCP on top of w3c/paint-timing#100 w3c/largest-contentful-paint#121.
-
-
1 pull request received 9 new comments.
-
Rebase LCP on top of w3c/paint-timing#100 w3c/largest-contentful-paint#121 (9 comments by @clelland, @noamr)
-
w3c/navigation-timing
-
1 pull request received 5 new comments.
-
Add notRestoredReasons to PerformanceNavigationTiming attribute w3c/navigation-timing#195 (5 comments by @domenic, @rubberyuzu, @smaug----)
-
w3c/resource-timing
-
1 issue opened.
-
Should `firstInterimResponseStart` show 0 when there is no interim response? w3c/resource-timing#382, by @tunetheweb.
-
w3c/event-timing
-
1 issue opened.
-
Broken references in Event Timing API w3c/event-timing#137, by @dontcallmedom-bot.
-
w3c/timing-entrytypes-registry
-
1 pull request opened.
-
Add long-animation-frame to registry w3c/timing-entrytypes-registry#16, by @noamr.
-
-
1 pull request merged.
-
Add long-animation-frame to registry w3c/timing-entrytypes-registry#16.
-
-
1 pull request received 3 new comments.
-
Add long-animation-frame to registry w3c/timing-entrytypes-registry#16 (3 comments by @noamr, @tunetheweb)
-
w3c/performance-timeline
-
1 pull request opened.
-
The common atttribute of `PerformanceEntry` should be initialized rat… w3c/performance-timeline#210, by @noamr.
-
-
1 pull request received 5 new comments.
-
The common atttribute of `PerformanceEntry` should be initialized rat… w3c/performance-timeline#210 (5 comments by @clelland, @noamr)
-
w3c/network-error-logging
-
1 issue received 1 new comment.
w3c/paint-timing
-
2 pull requests opened.
-
Mark spec as editor's draft; update editors w3c/paint-timing#103, by @clelland.
-
Auto-deploy to GHPages as well as TR w3c/paint-timing#102, by @clelland.
-
-
3 pull requests merged.
-
Mark spec as editor's draft; update editors w3c/paint-timing#103.
-
Auto-deploy to GHPages as well as TR w3c/paint-timing#102.
-
Include algorithms and concepts from Element Timing and LCP w3c/paint-timing#100.
-
-
3 pull requests received 11 new comments.
-
Include algorithms and concepts from Element Timing and LCP w3c/paint-timing#100 (7 comments by @clelland, @noamr)
-