Web Performance Working Group - Activity in 2022
No matches.
GitHub
w3c/largest-contentful-paint
-
2 issues opened.
-
renderTime should be CORS-protected, not TAO-protected w3c/largest-contentful-paint#111, by @noamr.
-
Broken references in Largest Contentful Paint w3c/largest-contentful-paint#109, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Update the 'Status of this document' section to indicate LCP has been adopted by WebPerfWG w3c/largest-contentful-paint#97.
-
-
13 issues received 21 new comments.
-
Hover-based user input is often used for "zoom widgets", skewing LCP results w3c/largest-contentful-paint#108 (5 comments by @gilbertococchi, @ksylor, @rockeynebhwani, @siakaramalegos, @tunetheweb)
-
Improve unimportant image heuristic w3c/largest-contentful-paint#86 (3 comments by @clelland, @jonsneyers)
-
Offscreen elements should be considered once they enter the viewport? w3c/largest-contentful-paint#61 (2 comments by @mmocny, @yoavweiss)
-
Elements that are obscured by other elements shouldn't be considered w3c/largest-contentful-paint#70 (2 comments by @noamr, @yoavweiss)
-
Update the 'Status of this document' section to indicate LCP has been adopted by WebPerfWG w3c/largest-contentful-paint#97 (1 comment by @yoavweiss)
-
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 @yoavweiss)
-
Should we skip images with an existing LCP entry? w3c/largest-contentful-paint#82 (1 comment by @yoavweiss)
-
Refine LCP to take progressive loading into account w3c/largest-contentful-paint#71 (1 comment by @yoavweiss)
-
renderTime definition is unclear in the spec for each element type w3c/largest-contentful-paint#54 (1 comment by @yoavweiss)
-
Separation between LCP and Paint Timing is confusing from a user perspective w3c/largest-contentful-paint#36 (1 comment by @yoavweiss)
-
-
1 pull request opened.
-
Move viewport link to visual viewport w3c/largest-contentful-paint#110, by @yoavweiss.
-
w3c/resource-timing
-
1 issue opened.
-
Why is there noticeable gap between requestStart and connectEnd? w3c/resource-timing#365, by @xiaofud.
-
-
3 issues received 7 new comments.
-
Problematic cases with cross-origin iframes & aborted navigations w3c/resource-timing#340 (4 comments by @annevk, @nicjansma, @noamr)
-
User Agent may want to restrict cross-origin transferSize/encodedBodySize/decodedBodySize visibility even with TAO w3c/resource-timing#342 (1 comment by @yoavweiss)
-
-
1 pull request opened.
-
Add interim response times w3c/resource-timing#366, by @noamr.
-
-
1 pull request received 1 new comment.
w3c/event-timing
-
2 issues opened.
-
Broken references in Event Timing API w3c/event-timing#127, by @dontcallmedom-bot.
-
1 issue closed.
-
Broken references in Event Timing API w3c/event-timing#127.
-
-
1 pull request opened.
-
Fix broken links w3c/event-timing#128, by @yoavweiss.
-
-
1 pull request merged.
-
Fix broken links w3c/event-timing#128.
-
-
1 pull request received 1 new comment.
w3c/navigation-timing
-
1 issue opened.
-
NavigationTimingType enum need updates as HTML spec changed w3c/navigation-timing#185, by @Elchi3.
-
-
3 issues received 6 new comments.
-
Extending the NavigationTimingType w3c/navigation-timing#184 (4 comments by @Krinkle, @tunetheweb, @verlok-cn, @yoavweiss)
-
Extend 'NavigationType' to include User Agent Launch w3c/navigation-timing#180 (1 comment by @dmurph)
-
NavigationTimingType enum need updates as HTML spec changed w3c/navigation-timing#185 (1 comment by @Krinkle)
-
w3c/longtasks
-
1 issue received 2 new comments.
-
Provide an option for overriding the 50ms threshold w3c/longtasks#14 (2 comments by @Elchi3, @yoavweiss)
-
w3c/hr-time
-
1 issue opened.
-
`timeOrigin` and skew over time from the system clock w3c/hr-time#141, by @yoavweiss.
-
w3c/beacon
-
1 issue received 3 new comments.
w3c/server-timing
-
1 issue received 1 new comment.
w3c/reporting
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Change Report and ReportBody interfaces to dicts. w3c/reporting#258, by @clelland.
-
-
1 pull request received 1 new comment.
TR publications
-
3 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
-
Participants
-
2 participants joined.
-
Jennifer Strickland (W3C Invited Experts) joined.
-
Sia Karamalegos (Shopify) joined.
-
-
1 organization joined.
-
MITRE Corporation joined.
-
GitHub
w3c/event-timing
-
1 issue opened.
-
Add `targetSelector` attribute to Event Timing API (for cases where target is detached) w3c/event-timing#126, by @mmocny.
-
-
1 issue closed.
-
1 issue received 4 new comments.
-
Add `targetSelector` attribute to Event Timing API (for cases where target is detached) w3c/event-timing#126 (4 comments by @mmocny, @nhelfman, @yoavweiss)
-
-
1 pull request opened.
-
Replace interactionCounts map-like with a single interactionCount number w3c/event-timing#125, by @zuoaoyuan.
-
-
1 pull request merged.
-
Replace interactionCounts map-like with a single interactionCount number w3c/event-timing#125.
-
-
1 pull request received 9 new comments.
-
Replace interactionCounts map-like with a single interactionCount number w3c/event-timing#125 (9 comments by @mmocny, @yoavweiss, @zuoaoyuan)
-
w3c/largest-contentful-paint
-
1 issue opened.
-
Hover-based user input is often used for "zoom widgets", skewing LCP results w3c/largest-contentful-paint#108, by @yoavweiss.
-
-
1 issue closed.
-
Why 'has dispatched scroll event' depends on whether untrusted scroll events have been dispatched? w3c/largest-contentful-paint#56.
-
-
4 issues received 4 new comments.
-
Hover-based user input is often used for "zoom widgets", skewing LCP results w3c/largest-contentful-paint#108 (1 comment by @yoavweiss)
-
Should border-images be considered contentful w3c/largest-contentful-paint#107 (1 comment by @clelland)
-
Why 'has dispatched scroll event' depends on whether untrusted scroll events have been dispatched? w3c/largest-contentful-paint#56 (1 comment by @clelland)
-
Call back to indicate that the observer is about to stop w3c/largest-contentful-paint#43 (1 comment by @clelland)
-
w3c/resource-timing
-
4 issues opened.
-
List of initiatorType types w3c/resource-timing#364, by @Elchi3.
-
How to get correct connectStart/End, domainLookupStart/End value when service worker is enabled? w3c/resource-timing#363, by @xiaofud.
-
Cache and Proxy information w3c/resource-timing#362, by @mnot.
-
Specify the behaviors of requestStart and responseStart for Prefetch w3c/resource-timing#360, by @liuwilliam-gh.
-
-
2 issues closed.
-
Drop the "L2" part from the published version w3c/resource-timing#326.
-
Failed deploy w3c/resource-timing#357.
-
-
6 issues received 11 new comments.
-
Specify the behaviors of requestStart and responseStart for Prefetch w3c/resource-timing#360 (3 comments by @jeremyroman, @liuwilliam-gh, @yoavweiss)
-
How to get correct connectStart/End, domainLookupStart/End value when service worker is enabled? w3c/resource-timing#363 (2 comments by @xiaofud, @yoavweiss)
-
Problematic cases with cross-origin iframes & aborted navigations w3c/resource-timing#340 (1 comment by @noamr)
-
Add response status codes for resources in Resource Timing API. w3c/resource-timing#90 (1 comment by @Paktas)
-
-
3 pull requests opened.
-
Explainer for Content-type w3c/resource-timing#361, by @abinpaul1.
-
removing level from title w3c/resource-timing#359, by @caribouW3.
-
update autopublish for CR Drafts w3c/resource-timing#358, by @caribouW3.
-
-
2 pull requests merged.
-
removing level from title w3c/resource-timing#359.
-
update autopublish for CR Drafts w3c/resource-timing#358.
-
-
1 pull request closed.
-
Update auto-publish.yml w3c/resource-timing#354.
-
-
2 pull requests received 4 new comments.
w3c/reporting
-
2 issues received 10 new comments.
w3c/element-timing
-
1 issue opened.
-
Broken references in Element Timing API w3c/element-timing#72, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in Element Timing API w3c/element-timing#72.
-
-
1 pull request opened.
-
Fix TAO check link w3c/element-timing#73, by @npm1.
-
-
1 pull request merged.
-
Fix TAO check link w3c/element-timing#73.
-
w3c/performance-timeline
-
1 issue closed.
-
Auto-publishing failures w3c/performance-timeline#201.
-
-
1 issue received 2 new comments.
-
3 pull requests opened.
-
Fix stray ">" w3c/performance-timeline#205, by @Elchi3.
-
Removing mentions of "level 2" w3c/performance-timeline#204, by @caribouW3.
-
change to publish CRDs w3c/performance-timeline#203, by @caribouW3.
-
-
3 pull requests merged.
-
Fix stray ">" w3c/performance-timeline#205.
-
Removing mentions of "level 2" w3c/performance-timeline#204.
-
change to publish CRDs w3c/performance-timeline#203.
-
-
2 pull requests received 2 new comments.
-
Add support for accessing cross-frame entries. w3c/performance-timeline#202 (1 comment by @clelland)
-
w3c/hr-time
-
1 pull request received 1 new comment.
w3c/navigation-timing
-
1 issue opened.
-
Extending the NavigationTimingType w3c/navigation-timing#184, by @tunetheweb.
-
TR publications
-
1 document published.
-
Resource Timing published as a Candidate Recommendation Snapshot. History of Resource Timing
-
GitHub
w3c/navigation-timing
-
1 issue opened.
-
performance.timeOrigin vs performance.timing.navigationStart w3c/navigation-timing#183, by @Quadiago.
-
-
1 issue closed.
-
performance.timeOrigin vs performance.timing.navigationStart w3c/navigation-timing#183.
-
-
1 issue reopened.
-
Extend 'NavigationType' to include User Agent Launch w3c/navigation-timing#180, by @marcelduran.
-
-
2 issues received 5 new comments.
-
performance.timeOrigin vs performance.timing.navigationStart w3c/navigation-timing#183 (3 comments by @Quadiago, @yoavweiss)
-
Extend 'NavigationType' to include User Agent Launch w3c/navigation-timing#180 (2 comments by @dmurph, @marcelduran)
-
w3c/resource-timing
-
1 issue opened.
-
Failed deploy w3c/resource-timing#357, by @yoavweiss.
-
-
1 issue received 1 new comment.
-
Problematic cases with cross-origin iframes & aborted navigations w3c/resource-timing#340 (1 comment by @noamr)
-
-
2 pull requests opened.
-
Status code explainer nits and suggestions w3c/resource-timing#355, by @yoavweiss.
-
Update auto-publish.yml w3c/resource-timing#354, by @caribouW3.
-
-
2 pull requests merged.
-
Add response status code to PerfomanceResourceTiming w3c/resource-timing#335.
-
Status code explainer nits and suggestions w3c/resource-timing#355.
-
-
2 pull requests received 5 new comments.
-
Add response status code to PerfomanceResourceTiming w3c/resource-timing#335 (4 comments by @abinpaul1, @yoavweiss)
-
w3c/resource-timing#356 (1 comment by @w3cbot)
-
w3c/largest-contentful-paint
-
1 issue opened.
-
Should border-images be considered contentful w3c/largest-contentful-paint#107, by @sohomdatta1.
-
-
3 issues received 6 new comments.
-
Should content-set be used for text-based LCP entries w3c/largest-contentful-paint#106 (3 comments by @clelland, @yoavweiss)
-
requestAnimationFrame callback and LCP renderTime should be the same w3c/largest-contentful-paint#104 (2 comments by @mmocny, @sefeng211)
-
Should border-images be considered contentful w3c/largest-contentful-paint#107 (1 comment by @yoavweiss)
-
w3c/hr-time
-
1 issue opened.
-
Spec text isn't clear about time origins and monotonic clocks w3c/hr-time#139, by @jyasskin.
-
-
1 pull request opened.
-
editorial: Introduce clocks, moments, and durations w3c/hr-time#140, by @jyasskin.
-
-
1 pull request received 12 new comments.
-
editorial: Introduce clocks, moments, and durations w3c/hr-time#140 (12 comments by @jyasskin, @noamr, @yoavweiss)
-
w3c/performance-timeline
-
3 issues received 3 new comments.
-
Consider renaming PerformanceObserverCallbackOptions w3c/performance-timeline#199 (1 comment by @clelland)
w3c/web-performance
-
1 issue opened.
-
Consider performance tools aimed at the ESM JavaScript loading w3c/web-performance#40, by @dvoytenko.
-
-
1 issue received 2 new comments.
-
Consider performance tools aimed at the ESM JavaScript loading w3c/web-performance#40 (2 comments by @dvoytenko, @yoavweiss)
-
w3c/event-timing
-
1 issue opened.
-
1 issue received 6 new comments.
-
Default buffering of Event Timing Entries is based on durationThreshold: 104 -- even for Interactions. w3c/event-timing#124 (6 comments by @mmocny, @nhelfman, @philipwalton, @yoavweiss)
-
TR publications
-
9 documents published.
-
Resource Timing Level 2 published 4 times as a Working Draft. History of Resource Timing Level 2
-
High Resolution Time published as a Working Draft. History of High Resolution Time
-
Reporting API published 3 times as a Working Draft. History of Reporting API
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Past meetings
-
4 meetings.
Participants
-
1 participant joined.
-
Abin Paul (W3C Invited Experts) joined.
-
-
2 participants left.
-
Paul Calvano (Akamai Technologies) left.
-
Vaspol Ruamviboonsuk (Akamai Technologies) left.
-
GitHub
w3c/event-timing
-
2 issues opened.
-
Spec should clarify value of `renderingTimestamp` whenever there is no next rendering opportunity. w3c/event-timing#123, by @mmocny.
-
How does Event Timing API relate to/overlap with Long Tasks API? w3c/event-timing#122, by @mmocny.
-
w3c/reporting
-
1 issue opened.
-
Inconsistent optionality for settings when generating reports w3c/reporting#257, by @jyasskin.
-
-
1 issue closed.
-
reporting cache replace operation not defined w3c/reporting#157.
-
-
4 issues received 8 new comments.
-
Tie retries to user browsing behavior for better privacy? w3c/reporting#4 (4 comments by @clelland, @npdoty, @yoavweiss)
-
-
6 pull requests opened.
-
Use the more common index.bs naming w3c/reporting#256, by @jyasskin.
-
Fix spec-prod action destination w3c/reporting#255, by @clelland.
-
Wire up a way for users to disable particular kinds of reporting. w3c/reporting#254, by @jyasskin.
-
Export "generate and queue a report" instead of "queue a report". w3c/reporting#253, by @jyasskin.
-
Fix bikeshed errors and use "Structured Fields" consistently. w3c/reporting#252, by @jyasskin.
-
Use spec-prod for all spec building. w3c/reporting#251, by @jyasskin.
-
-
5 pull requests merged.
-
Remove undefined 'replace' operation. w3c/reporting#229.
-
Fix spec-prod action destination w3c/reporting#255.
-
Use spec-prod for all spec building. w3c/reporting#251.
-
Export "generate and queue a report" instead of "queue a report". w3c/reporting#253.
-
Fix bikeshed errors and use "Structured Fields" consistently. w3c/reporting#252.
-
-
1 pull request closed.
-
Add note on leaking user identifiers. w3c/reporting#231.
-
-
3 pull requests received 7 new comments.
-
Export "generate and queue a report" instead of "queue a report". w3c/reporting#253 (3 comments by @clelland, @jyasskin, @triple-underscore)
-
Wire up a way for users to disable particular kinds of reporting. w3c/reporting#254 (1 comment by @yoavweiss)
-
w3c/network-error-logging
-
1 issue opened.
-
Link to updated reporting interface w3c/network-error-logging#131, by @jyasskin.
-
w3c/element-timing
-
1 issue received 24 new comments.
-
How should Element Timing interact with Shadow DOM? w3c/element-timing#3 (24 comments by @annevk, @nolanlawson, @rniwa, @smaug----, @yoavweiss)
-
w3c/resource-timing
-
1 issue opened.
-
InitiatorType for module scripts w3c/resource-timing#346, by @yoavweiss.
-
-
3 issues received 26 new comments.
-
Consider adding finalResponseHeaders{Start|End} times w3c/resource-timing#345 (23 comments by @annevk, @colinbendell, @dotjs, @LPardue, @nicjansma, @noamr, @tunetheweb)
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (1 comment by @hrghauri)
-
-
4 pull requests opened.
-
Update README.md w3c/resource-timing#353, by @caribouW3.
-
Update README.md w3c/resource-timing#352, by @caribouW3.
-
Update index.html w3c/resource-timing#350, by @caribouW3.
-
Explainer for Resource response status w3c/resource-timing#347, by @abinpaul1.
-
-
6 pull requests merged.
-
Update README.md w3c/resource-timing#353.
-
Update README.md w3c/resource-timing#352.
-
Update index.html w3c/resource-timing#350.
-
Explainer for Resource response status w3c/resource-timing#347.
-
Explainer for Render Blocking Status w3c/resource-timing#330.
-
Add notes RE privacy IG issues w3c/resource-timing#339.
-
-
5 pull requests received 25 new comments.
-
Add content-type to resource-timing w3c/resource-timing#341 (11 comments by @abinpaul1, @domenic, @yoavweiss)
-
Add delivery type to PerformanceResourceTiming. w3c/resource-timing#343 (6 comments by @jeremyroman, @nicjansma, @yoavweiss)
-
w3c/resource-timing#351 (1 comment by @w3cbot)
-
w3c/resource-timing#349 (1 comment by @w3cbot)
-
w3c/largest-contentful-paint
-
1 issue opened.
-
Should content-set be used for text-based LCP entries w3c/largest-contentful-paint#106, by @sohomdatta1.
-
-
1 issue received 1 new comment.
-
Elements that are obscured by other elements shouldn't be considered w3c/largest-contentful-paint#70 (1 comment by @noamr)
-
w3c/server-timing
-
1 issue received 7 new comments.
w3c/performance-timeline
-
1 pull request opened.
-
Add support for accessing cross-frame entries. w3c/performance-timeline#202, by @clelland.
-
-
2 pull requests received 3 new comments.
-
Add support for accessing cross-frame entries. w3c/performance-timeline#202 (2 comments by @clelland, @yoavweiss)
-
w3c/navigation-timing
-
2 issues received 4 new comments.
-
Clarify how PerformanceTiming.responseStart relates to Early Hint responses w3c/navigation-timing#181 (2 comments by @clelland, @nicjansma)
-
Extend 'NavigationType' to include User Agent Launch w3c/navigation-timing#180 (2 comments by @bmathwig, @yoavweiss)
-
-
1 pull request opened.
-
Navigation timing name should be the initial URL w3c/navigation-timing#182, by @noamr.
-
-
1 pull request merged.
-
Navigation timing name should be the initial URL w3c/navigation-timing#182.
-
-
1 pull request reopened.
-
Navigation timing name should be the initial URL w3c/navigation-timing#182, by @noamr.
-
-
1 pull request received 3 new comments.
-
Navigation timing name should be the initial URL w3c/navigation-timing#182 (3 comments by @noamr, @yoavweiss)
-
w3c/hr-time
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Revert "Expose everywhere" w3c/hr-time#138.
-
-
1 pull request received 1 new comment.
TR publications
-
3 documents published.
-
Beacon published as a Candidate Recommendation Draft. History of Beacon
-
User Timing Level 3 published as a Candidate Recommendation Draft. History of User Timing Level 3
-
Resource Timing Level 2 published as a Working Draft. History of Resource Timing Level 2
-
Participants
-
1 participant joined.
-
Andy Luhrs (Microsoft Corporation) joined.
-
GitHub
w3c/navigation-timing
-
1 issue opened.
-
Clarify how PerformanceTiming.responseStart relates to Early Hint responses w3c/navigation-timing#181, by @colinbendell.
-
-
2 issues received 3 new comments.
-
Extend 'NavigationType' to include User Agent Launch w3c/navigation-timing#180 (2 comments by @amiyagupta, @marcelduran)
-
Clarify how PerformanceTiming.responseStart relates to Early Hint responses w3c/navigation-timing#181 (1 comment by @LPardue)
-
w3c/resource-timing
-
3 issues opened.
-
Consider adding finalResponseHeaders{Start|End} times w3c/resource-timing#345, by @noamr.
-
Problematic cases with cross-origin iframes & aborted navigations w3c/resource-timing#340, by @noamr.
-
-
4 issues received 14 new comments.
-
Problematic cases with cross-origin iframes & aborted navigations w3c/resource-timing#340 (9 comments by @clelland, @domenic, @noamr, @sefeng211, @yoavweiss)
-
Consider adding finalResponseHeaders{Start|End} times w3c/resource-timing#345 (3 comments by @LPardue, @noamr)
-
-
2 pull requests opened.
-
Add delivery type to PerformanceResourceTiming. w3c/resource-timing#343, by @jeremyroman.
-
Add content-type to resource-timing w3c/resource-timing#341, by @abinpaul1.
-
-
1 pull request merged.
-
Add Render Blocking Status to PerformanceResourceTiming w3c/resource-timing#327.
-
-
6 pull requests received 23 new comments.
-
Add Render Blocking Status to PerformanceResourceTiming w3c/resource-timing#327 (10 comments by @abinpaul1, @noamr, @sefeng211)
-
Add delivery type to PerformanceResourceTiming. w3c/resource-timing#343 (5 comments by @jeremyroman, @yoavweiss)
-
Explainer for Render Blocking Status w3c/resource-timing#330 (4 comments by @abinpaul1, @tunetheweb)
-
Add response status code to PerfomanceResourceTiming w3c/resource-timing#335 (2 comments by @abinpaul1, @yoavweiss)
-
w3c/resource-timing#344 (1 comment by @w3cbot)
-
w3c/user-timing
-
2 issues opened.
-
Failed publishing w3c/user-timing#96, by @yoavweiss.
-
2 issues closed.
-
User timing buffer size w3c/user-timing#92.
-
Failed publishing w3c/user-timing#96.
-
-
4 issues received 8 new comments.
-
In workers, mark names can be PerformanceTiming attributes but they cannot be retrieved in measures w3c/user-timing#99 (3 comments by @paulirish, @yoavweiss)
-
It isn't defined what happens if StructuredSerialize in measure() throws an exception w3c/user-timing#91 (2 comments by @mmocny, @smaug----)
-
-
2 pull requests opened.
-
Update auto-publish.yml w3c/user-timing#98, by @caribouW3.
-
Update auto-publish.yml w3c/user-timing#97, by @caribouW3.
-
-
2 pull requests merged.
-
Update auto-publish.yml w3c/user-timing#98.
-
Update auto-publish.yml w3c/user-timing#97.
-
-
1 pull request received 1 new comment.
w3c/largest-contentful-paint
-
1 issue opened.
-
Need a new DOM concept for user-driven events rather than using `isTrusted` w3c/largest-contentful-paint#105, by @sefeng211.
-
-
2 issues closed.
-
Explainer should define which events are included in user input, not which ones are not w3c/largest-contentful-paint#27.
-
LargestContentfulPaint is difficult to efficiently implement w3c/largest-contentful-paint#31.
-
-
7 issues received 18 new comments.
-
Need a new DOM concept for user-driven events rather than using `isTrusted` w3c/largest-contentful-paint#105 (10 comments by @domenic, @noamr, @yoavweiss)
-
Update the 'Status of this document' section to indicate LCP has been adopted by WebPerfWG w3c/largest-contentful-paint#97 (3 comments by @caribouW3, @yoavweiss)
-
Background purposed images is not properly defined in the spec w3c/largest-contentful-paint#28 (1 comment by @yoavweiss)
-
Explainer should define which events are included in user input, not which ones are not w3c/largest-contentful-paint#27 (1 comment by @yoavweiss)
-
LargestContentfulPaint is difficult to efficiently implement w3c/largest-contentful-paint#31 (1 comment by @yoavweiss)
-
Frame viewport clipping is not properly specified w3c/largest-contentful-paint#26 (1 comment by @yoavweiss)
-
requestAnimationFrame callback and LCP renderTime should be the same w3c/largest-contentful-paint#104 (1 comment by @mmocny)
-
w3c/server-timing
-
2 issues opened.
-
Spec is broken w3c/server-timing#88, by @npm1.
-
3 issues closed.
-
Spec is broken w3c/server-timing#88.
-
Should PerformanceServerTiming inherit from PerformanceEntry? w3c/server-timing#85.
-
Nested hierarchy and grouping of sub-tasks w3c/server-timing#78.
-
-
6 issues received 7 new comments.
-
add start time to distinguish between cached and active entries w3c/server-timing#43 (1 comment by @noamr)
-
Should PerformanceServerTiming inherit from PerformanceEntry? w3c/server-timing#85 (1 comment by @noamr)
-
Server-Timing is too limited in scope, rename to Server-Metrics w3c/server-timing#77 (1 comment by @noamr)
w3c/beacon
-
3 issues closed.
-
Is "entry setings object" correct? w3c/beacon#78.
-
Drop dependencies section w3c/beacon#68.
-
-
4 issues received 6 new comments.
-
References terms from Page Visibility, which is a discontinued draft w3c/beacon#77 (2 comments by @clelland, @yoavweiss)
-
2 pull requests opened.
-
Remove deps section, properly cross-reference links w3c/beacon#81, by @clelland.
-
Update process w3c/beacon#80, by @clelland.
-
-
2 pull requests merged.
-
Remove deps section, properly cross-reference links w3c/beacon#81.
-
Update process w3c/beacon#80.
-
-
1 pull request received 3 new comments.
w3c/performance-timeline
-
1 issue opened.
-
Auto-publishing failures w3c/performance-timeline#201, by @yoavweiss.
-
-
1 issue received 2 new comments.
TR publications
-
4 documents published.
-
Device Memory published as a Working Draft. History of Device Memory
-
Resource Timing Level 2 published 3 times as a Working Draft. History of Resource Timing Level 2
-
Participants
-
5 participants joined.
-
Barry Pollard (Google LLC) joined.
-
Shuo Feng (Mozilla Foundation) joined.
-
Hao Liu (Google LLC) joined.
-
Aoyuan Zuo (Google LLC) joined.
-
Scott Haseley (Google LLC) joined.
-
-
4 participants left.
-
Neel Wadhwani (Google LLC) left.
-
Nat Duca (Google LLC) left.
-
Corentin Pescheloche (Meta) left.
-
Mark Hahnenberg (Meta) left.
-
GitHub
w3c/resource-timing
-
2 issues opened.
-
Is nexthopprotocol different from that in the chrome devtools? w3c/resource-timing#336, by @mamumu123.
-
Expose delivery type in PerformanceResourceTiming. w3c/resource-timing#332, by @jeremyroman.
-
-
6 issues closed.
-
WPT Cleanup w3c/resource-timing#254.
-
Transition Level 2 to CR w3c/resource-timing#71.
-
Server pushed resources in ResourceTiming w3c/resource-timing#53.
-
Consider to limit the max size of resource timing buffer w3c/resource-timing#304.
-
ResourceTiming and preconnect w3c/resource-timing#58.
-
Is nexthopprotocol different from that in the chrome devtools? w3c/resource-timing#336.
-
-
12 issues received 33 new comments.
-
Provide a TAO-bypass for Navigation timing w3c/resource-timing#220 (10 comments by @annevk, @camillelamy, @noamr, @yoavweiss)
-
Expose delivery type in PerformanceResourceTiming. w3c/resource-timing#332 (6 comments by @jeremyroman, @noamr, @yoavweiss)
-
Consider to limit the max size of resource timing buffer w3c/resource-timing#304 (3 comments by @bdekoz, @noamr, @yoavweiss)
-
Server pushed resources in ResourceTiming w3c/resource-timing#53 (2 comments by @MattMenke2, @noamr)
-
Render blocking status of resources w3c/resource-timing#262 (2 comments by @abinpaul1, @ArthurSonzogni)
-
Is nexthopprotocol different from that in the chrome devtools? w3c/resource-timing#336 (1 comment by @nicjansma)
-
Add response status codes for resources in Resource Timing API. w3c/resource-timing#90 (1 comment by @abinpaul1)
-
-
7 pull requests opened.
-
Add notes RE privacy IG issues w3c/resource-timing#339, by @yoavweiss.
-
chore: Fix missing curly brace w3c/resource-timing#337, by @nicjansma.
-
Add response status code to PerfomanceResourceTiming w3c/resource-timing#335, by @abinpaul1.
-
Update my affiliation w3c/resource-timing#334, by @noamr.
-
Fix the assertion in setup the resource timing entry. w3c/resource-timing#331, by @jeremyroman.
-
Explainer for Render Blocking Status w3c/resource-timing#330, by @abinpaul1.
-
Explainer: Render blocking status w3c/resource-timing#329, by @abinpaul1.
-
-
3 pull requests merged.
-
chore: Fix missing curly brace w3c/resource-timing#337.
-
Update my affiliation w3c/resource-timing#334.
-
Fix the assertion in setup the resource timing entry. w3c/resource-timing#331.
-
-
1 pull request closed.
-
Explainer: Render blocking status w3c/resource-timing#329.
-
-
1 pull request reopened.
-
Explainer: Render blocking status w3c/resource-timing#329, by @abinpaul1.
-
-
6 pull requests received 12 new comments.
-
Add response status code to PerfomanceResourceTiming w3c/resource-timing#335 (4 comments by @abinpaul1, @martinthomson, @yoavweiss)
-
Explainer for Render Blocking Status w3c/resource-timing#330 (4 comments by @caribouW3, @w3cbot, @yoavweiss)
-
w3c/resource-timing#338 (1 comment by @w3cbot)
-
w3c/resource-timing#333 (1 comment by @w3cbot)
-
w3c/reporting
-
1 issue closed.
-
Specify better data structures w3c/reporting#14.
-
-
6 issues received 6 new comments.
-
Endpoint weighted selection algorithm fails if weights are 0 w3c/reporting#153 (1 comment by @clelland)
-
Allow features to specify the criteria for considering a report successfully sent w3c/reporting#7 (1 comment by @clelland)
-
What happens if "Let total weight be the sum of the weight value of each endpoint in endpoints" overflows w3c/reporting#138 (1 comment by @clelland)
w3c/beacon
-
3 issues opened.
-
Duplicate, vague, and monkeypatching normative requirements w3c/beacon#79, by @domenic.
-
Is "entry setings object" correct? w3c/beacon#78, by @domenic.
-
References terms from Page Visibility, which is a discontinued draft w3c/beacon#77, by @domenic.
-
-
1 issue received 4 new comments.
w3c/largest-contentful-paint
-
1 issue opened.
-
requestAnimationFrame callback and LCP renderTime should be the same w3c/largest-contentful-paint#104, by @sefeng211.
-
-
1 issue closed.
-
Use naturalSize doesn't make sense for css images w3c/largest-contentful-paint#98.
-
-
3 issues received 11 new comments.
-
requestAnimationFrame callback and LCP renderTime should be the same w3c/largest-contentful-paint#104 (6 comments by @mmocny, @noamr, @sefeng211, @yoavweiss)
-
Refine LCP to take progressive loading into account w3c/largest-contentful-paint#71 (3 comments by @jonsneyers, @mlstubblefield, @yoavweiss)
-
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 @yoavweiss)
-
-
1 pull request opened.
-
isTrusted needs to be true for scroll events w3c/largest-contentful-paint#103, by @yoavweiss.
-
-
2 pull requests merged.
-
Fix image sizing penalty to use CSS terms w3c/largest-contentful-paint#99.
-
isTrusted needs to be true for scroll events w3c/largest-contentful-paint#103.
-
-
2 pull requests received 8 new comments.
-
Fix image sizing penalty to use CSS terms w3c/largest-contentful-paint#99 (6 comments by @noamr, @yoavweiss)
-
isTrusted needs to be true for scroll events w3c/largest-contentful-paint#103 (2 comments by @mmocny, @yoavweiss)
-
w3c/user-timing
-
3 pull requests opened.
-
Update auto-publish.yml w3c/user-timing#95, by @caribouW3.
-
Update auto-publish.yml w3c/user-timing#94, by @caribouW3.
-
Revert "Expose everywhere" w3c/user-timing#93, by @yoavweiss.
-
-
3 pull requests merged.
-
Update auto-publish.yml w3c/user-timing#95.
-
Update auto-publish.yml w3c/user-timing#94.
-
Revert "Expose everywhere" w3c/user-timing#93.
-
-
2 pull requests received 3 new comments.
w3c/device-memory
-
5 issues closed.
-
Setup auto-publish workflow for index.html; deprecate README.md w3c/device-memory#11.
-
Drop/Adjust link to ED? w3c/device-memory#44.
-
Upper and lower bound should be UA opiniated decision, in entire text. w3c/device-memory#23.
-
IANA considerations section needed w3c/device-memory#21.
-
Should device memory be limited to what the UA can access? w3c/device-memory#13.
-
-
3 issues received 5 new comments.
-
Setup auto-publish workflow for index.html; deprecate README.md w3c/device-memory#11 (3 comments by @caribouW3, @yoavweiss)
-
Upper and lower bound should be UA opiniated decision, in entire text. w3c/device-memory#23 (1 comment by @yoavweiss)
-
-
1 pull request opened.
-
Address editorial issues w3c/device-memory#46, by @yoavweiss.
-
-
1 pull request merged.
-
Address editorial issues w3c/device-memory#46.
-
-
1 pull request closed.
-
chore: update README w3c/device-memory#39.
-
-
2 pull requests received 9 new comments.
w3c/performance-timeline
-
1 issue closed.
-
Ensure tests are clean w3c/performance-timeline#100.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Revert "Expose everywhere" w3c/performance-timeline#200, by @yoavweiss.
-
-
1 pull request merged.
-
Revert "Expose everywhere" w3c/performance-timeline#200.
-
-
1 pull request received 1 new comment.
w3c/navigation-timing
-
1 pull request received 1 new comment.
w3c/hr-time
-
1 issue received 1 new comment.
-
Suggestions: ticking during sleep, comparison across contexts, time origin + now semantics, and skew definition w3c/hr-time#115 (1 comment by @jonathanmayer)
-
-
1 pull request opened.
-
Revert "Expose everywhere" w3c/hr-time#138, by @yoavweiss.
-
-
1 pull request received 1 new comment.
w3c/element-timing
-
1 issue opened.
-
Normatively define the “elementtiming” content attribute w3c/element-timing#71, by @yoavweiss.
-
-
1 issue received 1 new comment.
w3c/event-timing
-
1 issue opened.
-
"has dispatched input event" should only be set for trusted events w3c/event-timing#121, by @yoavweiss.
-
-
1 issue received 3 new comments.
-
"has dispatched input event" should only be set for trusted events w3c/event-timing#121 (3 comments by @mmocny, @yoavweiss)
-
TR publications
-
4 documents published.
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Resource Timing Level 2 published as a Working Draft. History of Resource Timing Level 2
-
Page Visibility Level 2 published as a Discontinued Draft. History of Page Visibility Level 2
GitHub
w3c/largest-contentful-paint
-
1 issue received 3 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 @mmocny, @nicjansma)
-
-
1 pull request opened.
-
Add final slash to ED URL w3c/largest-contentful-paint#102, by @tidoust.
-
-
1 pull request received 1 new comment.
w3c/element-timing
-
1 issue received 1 new comment.
-
How should Element Timing interact with Shadow DOM? w3c/element-timing#3 (1 comment by @toddreifsteck)
-
w3c/requestidlecallback
-
3 issues received 8 new comments.
-
Setup auto publishing w3c/requestidlecallback#100 (5 comments by @caribouW3, @clelland, @plehegar, @yoavweiss)
-
-
1 pull request merged.
-
chore: auto-publish w3c/requestidlecallback#94.
-
-
1 pull request received 1 new comment.
w3c/hr-time
-
2 issues received 4 new comments.
-
Suggestions: ticking during sleep, comparison across contexts, time origin + now semantics, and skew definition w3c/hr-time#115 (2 comments by @clelland, @yoavweiss)
-
Security and privacy considerations for DOMHighResTimeStamp resolution w3c/hr-time#79 (2 comments by @clelland, @yoavweiss)
-
w3c/paint-timing
-
1 issue received 2 new comments.
-
Add attribution information about what triggers paint w3c/paint-timing#44 (2 comments by @noamr, @npm1)
-
-
1 pull request opened.
-
Remove rendering pipeline note w3c/paint-timing#94, by @noamr.
-
-
1 pull request received 5 new comments.
w3c/user-timing
-
2 issues received 2 new comments.
-
Marking and measuring style computation, layout calculations, etc w3c/user-timing#88 (1 comment by @nicjansma)
-
w3c/resource-timing
-
2 issues received 2 new comments.
-
Consider to limit the max size of resource timing buffer w3c/resource-timing#304 (1 comment by @yoavweiss)
-
Expose a way to link a call to fetch to an individual PerformanceResourceTiming object w3c/resource-timing#102 (1 comment by @cdaringe)
-
-
1 pull request opened.
-
Add Render Blocking Status to PerformanceResourceTiming w3c/resource-timing#327, by @abinpaul1.
-
-
1 pull request merged.
-
Use `response body info` instead of `timing info` for body sizes w3c/resource-timing#321.
-
-
1 pull request closed.
-
Expose everywhere w3c/resource-timing#302.
-
-
1 pull request reopened.
-
Use `response body info` instead of `timing info` for body sizes w3c/resource-timing#321, by @noamr.
-
-
4 pull requests received 17 new comments.
-
Add Render Blocking Status to PerformanceResourceTiming w3c/resource-timing#327 (10 comments by @abinpaul1, @caribouW3, @noamr, @yoavweiss)
-
Use `response body info` instead of `timing info` for body sizes w3c/resource-timing#321 (2 comments by @noamr, @yoavweiss)
-
w3c/resource-timing#328 (1 comment by @w3cbot)
-
w3c/reporting
-
7 issues closed.
-
Use low priority task queue and add takeRecords to ReportingObserver? w3c/reporting#58.
-
Friendly TAG Review: relation to lifecycle events w3c/reporting#54.
-
Friendly TAG Review: service worker integration w3c/reporting#50.
-
Are report type extensible? w3c/reporting#250.
-
endpoints should be stateless w3c/reporting#133.
-
Batch reports from related documents? w3c/reporting#226.
-
3 issues received 3 new comments.
-
Use low priority task queue and add takeRecords to ReportingObserver? w3c/reporting#58 (1 comment by @clelland)
-
w3c/navigation-timing
-
3 issues received 7 new comments.
-
Extend 'NavigationType' to include User Agent Launch w3c/navigation-timing#180 (5 comments by @amiyagupta, @domenic, @yoavweiss)
-
What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? w3c/navigation-timing#124 (1 comment by @noamr)
-
Detecting whether a navigation was BFCache-eligible w3c/navigation-timing#179 (1 comment by @fergald)
-
-
1 pull request merged.
-
Pass response body info through w3c/navigation-timing#176.
-
-
1 pull request received 1 new comment.
w3c/beacon
-
1 pull request merged.
-
Adjust resource-timing reporting to fetch refactor w3c/beacon#75.
-
-
1 pull request reopened.
-
Adjust resource-timing reporting to fetch refactor w3c/beacon#75, by @noamr.
-
w3c/server-timing
-
1 pull request closed.
-
Expose everywhere w3c/server-timing#84.
-
-
1 pull request received 1 new comment.
w3c/event-timing
-
1 pull request opened.
-
Add final slash to ED URL w3c/event-timing#120, by @tidoust.
-
-
1 pull request merged.
-
Add final slash to ED URL w3c/event-timing#120.
-
TR publications
-
2 documents published.
-
Event Timing API published as a First Public Working Draft. History of Event Timing API
-
Largest Contentful Paint published as a First Public Working Draft. History of Largest Contentful Paint
-
Participants
-
1 participant joined.
-
Marcos Caceres (Apple Inc.) joined.
-
-
1 participant left.
-
Philippe Le Hegaret (W3C) left.
-
GitHub
w3c/navigation-timing
-
2 issues opened.
-
Extend 'NavigationType' to include User Agent Launch w3c/navigation-timing#180, by @bmathwig.
-
Detecting whether a navigation was BFCache-eligible w3c/navigation-timing#179, by @fergald.
-
-
2 issues closed.
-
Should pages with different COOP be able to get unload event start/end. w3c/navigation-timing#169.
-
Extend the navigationType enum to include "reload after being discarded" navigations w3c/navigation-timing#178.
-
-
7 issues received 14 new comments.
-
Should pages with different COOP be able to get unload event start/end. w3c/navigation-timing#169 (7 comments by @domenic, @hemeryar, @noamr, @rakina)
-
Extend the navigationType enum to include "reload after being discarded" navigations w3c/navigation-timing#178 (2 comments by @yoavweiss)
-
Extend Navigation Timing API to include back/forward cache NotRestoredReasons w3c/navigation-timing#171 (1 comment by @nicjansma)
-
Extend 'NavigationType' to include User Agent Launch w3c/navigation-timing#180 (1 comment by @amiyagupta)
-
Report that Critical-CH was used to restart a navigation w3c/navigation-timing#177 (1 comment by @nicjansma)
-
w3c/reporting
-
3 issues closed.
-
Report calls to console-methods like "console.error" w3c/reporting#176.
-
Add "javascript error" report type? w3c/reporting#119.
-
Add "performance warning" report type? w3c/reporting#118.
-
-
4 issues received 4 new comments.
w3c/largest-contentful-paint
-
5 issues received 8 new comments.
-
Should we skip images with an existing LCP entry? w3c/largest-contentful-paint#82 (3 comments by @noamr, @rik)
-
Very large transparent SVG should not count as LCP w3c/largest-contentful-paint#72 (2 comments by @noamr)
-
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)
-
Specify exclusions for opacity:0, display:none, etc. w3c/largest-contentful-paint#79 (1 comment by @noamr)
-
-
1 pull request opened.
-
Fix link to editors draft & repo w3c/largest-contentful-paint#101, by @dontcallmedom.
-
-
1 pull request merged.
-
Fix link to editors draft & repo w3c/largest-contentful-paint#101.
-
-
1 pull request received 7 new comments.
-
Fix image sizing penalty to use CSS terms w3c/largest-contentful-paint#99 (7 comments by @emilio, @noamr, @sefeng211)
-
w3c/event-timing
-
3 issues received 5 new comments.
-
Proposal: DOM event identifier which can map to EventTimingPerformance entry w3c/event-timing#108 (2 comments by @mmocny, @nhelfman)
-
Consider replacing `performance.interactionCounts` map-like with a `performance.interactionCount` number w3c/event-timing#117 (2 comments by @mmocny, @nicjansma)
-
w3c/web-performance
-
1 pull request received 1 new comment.
w3c/user-timing
-
1 issue opened.
-
User timing buffer size w3c/user-timing#92, by @legendecas.
-
-
2 issues received 5 new comments.
-
Marking and measuring style computation, layout calculations, etc w3c/user-timing#88 (4 comments by @mmocny, @nhelfman, @noamr)
-
w3c/resource-timing
-
1 issue reopened.
-
Add tests for not-same-site nested contexts w3c/resource-timing#204, by @yoavweiss.
-
-
3 issues received 4 new comments.
-
Test multiple DNS responses and connection failures w3c/resource-timing#188 (2 comments by @noamr, @yoavweiss)
-
Consider to limit the max size of resource timing buffer w3c/resource-timing#304 (1 comment by @nicjansma)
-
Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent browser history leakage w3c/resource-timing#222 (1 comment by @yoavweiss)
-
-
1 pull request received 2 new comments.
-
Use `response body info` instead of `timing info` for body sizes w3c/resource-timing#321 (2 comments by @noamr, @yoavweiss)
-
TR publications
-
4 documents published.
-
Server Timing published as a Working Draft. History of Server Timing
-
Resource Timing Level 2 published twice as a Working Draft. History of Resource Timing Level 2
-
Reporting API published as a Working Draft. History of Reporting API
-
Participants
-
3 participants joined.
-
Amiya Gupta (Microsoft Corporation) joined.
-
Jeremy Rose (Salesforce) joined.
-
Noli Fernan Perez (Rakuten Group, Inc.) joined.
-
-
3 participants left.
-
Thomas Kelly (Shopify) left.
-
Maxime Vaillancourt (Shopify) left.
-
Marcos Caceres (Apple Inc.) left.
-
-
1 organization joined.
-
Rakuten Group, Inc. joined.
-
GitHub
w3c/resource-timing
-
1 issue opened.
-
Drop the "L2" part from the published version w3c/resource-timing#326, by @yoavweiss.
-
-
4 issues closed.
-
elaborate on `stalled` or `blocked` stage in specs w3c/resource-timing#164.
-
Clarify what constitutes a "downloadable resource" w3c/resource-timing#100.
-
Discussion: Media reporting & range requests w3c/resource-timing#320.
-
Review that Resource Timing 2 language works for QUIC w3c/resource-timing#126.
-
-
8 issues received 27 new comments.
-
Reflect preload information (in ResourceTiming?) w3c/resource-timing#303 (13 comments by @andydavies, @nicjansma, @noamr)
-
Consider removing nextHopProtocol as it may expose whether visitor is using VPN / proxy w3c/resource-timing#221 (6 comments by @LPardue, @sleevi)
-
initiatorType definition doesn't define initiator in multiple element scenarios w3c/resource-timing#54 (1 comment by @noamr)
-
-
2 pull requests opened.
-
Clarify "downloadable" w3c/resource-timing#324, by @noamr.
-
Illustrate in diagram that timestamps are not necessarily consecutive w3c/resource-timing#323, by @noamr.
-
-
3 pull requests merged.
-
Illustrate in diagram that timestamps are not necessarily consecutive w3c/resource-timing#323.
-
Clarify "downloadable" w3c/resource-timing#324.
-
Update diagram to include workerStart and QUIC w3c/resource-timing#322.
-
-
3 pull requests received 6 new comments.
-
Illustrate in diagram that timestamps are not necessarily consecutive w3c/resource-timing#323 (3 comments by @noamr, @yoavweiss)
-
Update diagram to include workerStart and QUIC w3c/resource-timing#322 (2 comments by @noamr, @yoavweiss)
-
w3c/resource-timing#325 (1 comment by @w3cbot)
-
w3c/navigation-timing
-
2 issues opened.
-
Extend the navigationType enum to include "reload after being discarded" navigations w3c/navigation-timing#178, by @yoavweiss.
-
Report that Critical-CH was used to restart a navigation w3c/navigation-timing#177, by @yoavweiss.
-
-
7 issues closed.
-
should unloaded iframes be included in their parent document's unload duration? w3c/navigation-timing#83.
-
Should navigationEntry's navigationType be updated according to the parent page ? w3c/navigation-timing#85.
-
Spec for PerformanceNavigationTiming.type does not match any implementations w3c/navigation-timing#114.
-
Clarify security context for PerformanceNavigationTiming w3c/navigation-timing#144.
-
A scenario where transferSize is 0 for non cached loads (or may be not) w3c/navigation-timing#146.
-
Using "connectStart", "secureConnectionStart" and "connectEnd" with HTTP/3 flows w3c/navigation-timing#165.
-
Transition Level 2 to CR w3c/navigation-timing#49.
-
-
13 issues received 26 new comments.
-
Using navigationStart as a baseline may expose cross-origin timing information w3c/navigation-timing#160 (4 comments by @annevk, @noamr)
-
Should pages with different COOP be able to get unload event start/end. w3c/navigation-timing#169 (3 comments by @hemeryar, @yoavweiss)
-
The "Obsolete" label is rendered in a seemingly random place w3c/navigation-timing#149 (3 comments by @noamr, @yoavweiss)
-
Lack of Feature Parity with Performace.measure() in Level 2 w3c/navigation-timing#154 (2 comments by @yoavweiss)
-
Should navigationEntry's navigationType be updated according to the parent page ? w3c/navigation-timing#85 (2 comments by @noamr)
-
should unloaded iframes be included in their parent document's unload duration? w3c/navigation-timing#83 (2 comments by @noamr, @yoavweiss)
-
Spec for PerformanceNavigationTiming.type does not match any implementations w3c/navigation-timing#114 (2 comments by @noamr, @yoavweiss)
-
Clarify security context for PerformanceNavigationTiming w3c/navigation-timing#144 (2 comments by @noamr, @yoavweiss)
-
Extend the navigationType enum to include "reload after being discarded" navigations w3c/navigation-timing#178 (1 comment by @yoavweiss)
-
A scenario where transferSize is 0 for non cached loads (or may be not) w3c/navigation-timing#146 (1 comment by @yoavweiss)
-
Using "connectStart", "secureConnectionStart" and "connectEnd" with HTTP/3 flows w3c/navigation-timing#165 (1 comment by @annevk)
-
w3c/largest-contentful-paint
-
2 issues opened.
-
Use naturalSize doesn't make sense for css images w3c/largest-contentful-paint#98, by @sefeng211.
-
Update the 'Status of this document' section to indicate LCP has been adopted by WebPerfWG w3c/largest-contentful-paint#97, by @sefeng211.
-
-
3 issues received 19 new comments.
-
Use naturalSize doesn't make sense for css images w3c/largest-contentful-paint#98 (10 comments by @emilio, @noamr, @sefeng211, @yoavweiss)
-
Update the 'Status of this document' section to indicate LCP has been adopted by WebPerfWG w3c/largest-contentful-paint#97 (8 comments by @clelland, @npm1, @sefeng211, @tabatkins, @yoavweiss)
-
"Contentful style-background-images" definition is too vague to be relied upon? w3c/largest-contentful-paint#55 (1 comment by @LukeLeber)
-
-
1 pull request opened.
-
Fix image sizing penalty to use CSS terms w3c/largest-contentful-paint#99, by @noamr.
-
-
1 pull request received 13 new comments.
-
Fix image sizing penalty to use CSS terms w3c/largest-contentful-paint#99 (13 comments by @emilio, @noamr, @npm1, @sefeng211, @yoavweiss)
-
w3c/requestidlecallback
-
1 issue opened.
-
Setup auto publishing w3c/requestidlecallback#100, by @yoavweiss.
-
-
1 issue closed.
-
Can we rename this spec? w3c/requestidlecallback#91.
-
-
1 pull request opened.
-
Update editors w3c/requestidlecallback#101, by @domenic.
-
-
2 pull requests merged.
-
Update editors w3c/requestidlecallback#101.
-
Editorial: rename spec to requestIdleCallback() w3c/requestidlecallback#92.
-
-
1 pull request received 6 new comments.
-
Update editors w3c/requestidlecallback#101 (6 comments by @domenic, @igrigorik, @rmcilroy, @yoavweiss)
-
w3c/event-timing
-
1 issue opened.
-
Update research reference to more current research w3c/event-timing#118, by @nhelfman.
-
-
1 issue received 2 new comments.
-
Update research reference to more current research w3c/event-timing#118 (2 comments by @mmocny, @yoavweiss)
-
-
1 pull request opened.
-
Update spec URL w3c/event-timing#119, by @queengooborg.
-
-
1 pull request merged.
-
Update spec URL w3c/event-timing#119.
-
-
1 pull request received 1 new comment.
w3c/user-timing
-
2 issues opened.
-
It isn't defined what happens if StructuredSerialize in measure() throws an exception w3c/user-timing#91, by @smaug----.
-
-
1 issue closed.
-
2 issues received 10 new comments.
-
It is unclear what "If startOrMeasureOptions is a non-empty PerformanceMeasureOptions object" means w3c/user-timing#89 (7 comments by @clelland, @npm1, @smaug----, @yoavweiss)
-
Contextual and GC friendly user timing w3c/user-timing#86 (3 comments by @legendecas, @mmocny, @yoavweiss)
-
-
1 pull request opened.
-
Remove incorrect non-empty check w3c/user-timing#90, by @npm1.
-
-
1 pull request merged.
-
Remove incorrect non-empty check w3c/user-timing#90.
-
w3c/server-timing
-
4 issues closed.
-
RT and NT processing is not well defined w3c/server-timing#38.
-
Creation time of PerformanceServerTiming objects unclear w3c/server-timing#69.
-
Fetch integration is missing w3c/server-timing#55.
-
Evaluate current parsing error strategy w3c/server-timing#42.
-
-
2 issues received 3 new comments.
-
Creation time of PerformanceServerTiming objects unclear w3c/server-timing#69 (1 comment by @annevk)
-
1 pull request merged.
-
Add explicit parsing rules for FETCH integration w3c/server-timing#87.
-
-
2 pull requests reopened.
-
Add explicit parsing rules for FETCH integration w3c/server-timing#87, by @noamr.
-
Add explicit parsing rules for FETCH integration w3c/server-timing#87, by @noamr.
-
-
1 pull request received 1 new comment.
w3c/beacon
-
1 issue opened.
-
Setup auto publishing w3c/beacon#76, by @yoavweiss.
-
-
1 issue received 3 new comments.
w3c/hr-time
-
1 issue closed.
-
Prerendered pages and `timeOrigin` w3c/hr-time#136.
-
-
1 issue received 1 new comment.
w3c/longtasks
-
1 issue opened.
-
Task duration should be coarsened for each context w3c/longtasks#98, by @noamr.
-
-
1 issue closed.
-
Task duration should be coarsened for each context w3c/longtasks#98.
-
-
2 issues received 9 new comments.
-
Task duration should be coarsened for each context w3c/longtasks#98 (7 comments by @domenic, @noamr, @yoavweiss)
-
Event loop timing reporting seems to ignore reentrancy w3c/longtasks#76 (2 comments by @noamr, @yoavweiss)
-
-
1 pull request opened.
-
Coarsen timestamps when reporting w3c/longtasks#99, by @noamr.
-
-
1 pull request merged.
-
Coarsen timestamps when reporting w3c/longtasks#99.
-
w3c/reporting
-
1 issue closed.
-
The document in TR space hasn't been updated since 2018. w3c/reporting#248.
-
-
1 issue received 2 new comments.
-
The document in TR space hasn't been updated since 2018. w3c/reporting#248 (2 comments by @clelland, @plehegar)
-
TR publications
-
3 documents published.
-
Navigation Timing Level 2 published twice as a Working Draft. History of Navigation Timing Level 2
-
Preload published as a Discontinued Draft. History of Preload
-
Participants
-
3 participants joined.
-
Alex N. Jose (Google LLC) joined.
-
Neel Wadhwani (Google LLC) joined.
-
Giacomo Zecchini (W3C Invited Experts) joined.
-
GitHub
w3c/resource-timing
-
1 issue closed.
-
Clarify RT entry creation when iframe changes `src` w3c/resource-timing#316.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Update diagram to include workerStart and QUIC w3c/resource-timing#322, by @noamr.
-
Use `response body info` instead of `timing info` for body sizes w3c/resource-timing#321, by @noamr.
-
-
1 pull request received 4 new comments.
-
Update diagram to include workerStart and QUIC w3c/resource-timing#322 (4 comments by @noamr, @yoavweiss)
-
w3c/hr-time
-
1 issue opened.
-
Prerendered pages and `timeOrigin` w3c/hr-time#136, by @yoavweiss.
-
w3c/largest-contentful-paint
-
1 issue opened.
-
Expose LCP renderTime in non-TAO cross-origin images, when it doesn't reflect the image decoding time w3c/largest-contentful-paint#91, by @yoavweiss.
-
-
2 issues received 6 new comments.
-
Refine LCP to take progressive loading into account w3c/largest-contentful-paint#71 (4 comments by @benkingcode, @florentb, @yoavweiss)
-
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, @yoavweiss)
-
-
2 pull requests opened.
-
Change `pair` use to `tuple` w3c/largest-contentful-paint#90, by @yoavweiss.
-
Change to W3C template w3c/largest-contentful-paint#89, by @yoavweiss.
-
-
2 pull requests merged.
-
Change `pair` use to `tuple` w3c/largest-contentful-paint#90.
-
Change to W3C template w3c/largest-contentful-paint#89.
-
-
1 pull request reopened.
-
Change `pair` use to `tuple` w3c/largest-contentful-paint#90, by @npm1.
-
-
1 pull request received 1 new comment.
w3c/user-timing
-
1 issue opened.
-
Marking and measuring style computation, layout calculations, etc w3c/user-timing#88, by @andyearnshaw.
-
-
2 issues closed.
-
Provide a way to associate warnings with measurements w3c/user-timing#25.
-
-
6 issues received 10 new comments.
-
Allow marks and measures to be shown in developer tooling without adding it to the performance timeline w3c/user-timing#68 (5 comments by @jackfranklin, @yoavweiss)
-
Marking and measuring style computation, layout calculations, etc w3c/user-timing#88 (1 comment by @yoavweiss)
-
Update the introductory text to explain how this API differs from performance.now() w3c/user-timing#37 (1 comment by @yoavweiss)
-
Define best practices for monitoring of single page apps via UT / custom Entries w3c/user-timing#40 (1 comment by @yoavweiss)
-
w3c/navigation-timing
-
2 issues opened.
-
Links to "relevant application caches" are broken w3c/navigation-timing#173, by @yoavweiss.
-
Extend Navigation Timing API to include back/forward cache NotRestoredReasons w3c/navigation-timing#171, by @rubberyuzu.
-
-
9 issues closed.
-
Define attribute behavior only once w3c/navigation-timing#97.
-
Should processing model cut the steps defined by PerformanceResourceTiming? w3c/navigation-timing#78.
-
workerStart should be gated on same-origin check w3c/navigation-timing#99.
-
worker start needs to be added to diagram w3c/navigation-timing#128.
-
Clarify spec and tests with respect to redirect info w3c/navigation-timing#158.
-
AppCache meaning w3c/navigation-timing#140.
-
Processing Model: Should 'prompt for unload' box actually be unload? w3c/navigation-timing#164.
-
Better integration with ResourceTiming w3c/navigation-timing#117.
-
Links to "relevant application caches" are broken w3c/navigation-timing#173.
-
-
11 issues received 16 new comments.
-
Extend Navigation Timing API to include back/forward cache NotRestoredReasons w3c/navigation-timing#171 (3 comments by @crockercliff, @rubberyuzu, @yoavweiss)
-
Should processing model cut the steps defined by PerformanceResourceTiming? w3c/navigation-timing#78 (2 comments by @noamr, @yoavweiss)
-
Should navigationEntry's navigationType be updated according to the parent page ? w3c/navigation-timing#85 (2 comments by @noamr, @yoavweiss)
-
Should pages with different COOP be able to get unload event start/end. w3c/navigation-timing#169 (1 comment by @noamr)
-
What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? w3c/navigation-timing#124 (1 comment by @noamr)
-
Clarify spec and tests with respect to redirect info w3c/navigation-timing#158 (1 comment by @noamr)
-
Links to "relevant application caches" are broken w3c/navigation-timing#173 (1 comment by @yoavweiss)
-
-
4 pull requests opened.
-
Pass response body info through w3c/navigation-timing#176, by @noamr.
-
Update diagram: rename "prompt to unload" and "AppCache" w3c/navigation-timing#175, by @noamr.
-
Update "relevant application cache" to point to HTTP cache w3c/navigation-timing#174, by @noamr.
-
Rename NavigationType to NavigationTimingType w3c/navigation-timing#172, by @domenic.
-
-
3 pull requests merged.
-
Rename NavigationType to NavigationTimingType w3c/navigation-timing#172.
-
Update diagram: rename "prompt to unload" and "AppCache" w3c/navigation-timing#175.
-
Update "relevant application cache" to point to HTTP cache w3c/navigation-timing#174.
-
-
2 pull requests received 2 new comments.
w3c/beacon
-
1 pull request opened.
-
Adjust resource-timing reporting to fetch refactor w3c/beacon#75, by @noamr.
-
-
1 pull request received 1 new comment.
w3c/performance-timeline
-
1 issue opened.
-
Consider renaming PerformanceObserverCallbackOptions w3c/performance-timeline#199, by @kenchris.
-
w3c/event-timing
-
1 issue opened.
-
2 pull requests opened.
-
Fix up contextmenu link issue w3c/event-timing#116, by @yoavweiss.
-
Change document template w3c/event-timing#115, by @yoavweiss.
-
-
2 pull requests merged.
-
Fix up contextmenu link issue w3c/event-timing#116.
-
Change document template w3c/event-timing#115.
-
-
1 pull request received 1 new comment.
w3c/reporting
-
1 issue received 1 new comment.
w3c/element-timing
-
1 pull request opened.
-
Editorial: use associated Document in place of responsible document w3c/element-timing#70, by @miketaylr.
-
-
1 pull request merged.
-
Editorial: use associated Document in place of responsible document w3c/element-timing#70.
-
w3c/web-performance
-
1 issue received 1 new comment.
w3c/server-timing
-
1 issue received 2 new comments.
-
Creation time of PerformanceServerTiming objects unclear w3c/server-timing#69 (2 comments by @annevk, @noamr)
-
TR publications
-
2 documents published.
-
Navigation Timing Level 2 published twice as a Working Draft. History of Navigation Timing Level 2
-
Participants
-
1 participant joined.
-
Chris Danis (Wikimedia Foundation) joined.
-
GitHub
w3c/server-timing
-
1 issue closed.
-
Clarify security context for PerformanceResourceTiming w3c/server-timing#79.
-
-
4 issues received 7 new comments.
-
Clarify security context for PerformanceResourceTiming w3c/server-timing#79 (4 comments by @fred-wang, @yoavweiss)
-
-
1 pull request opened.
-
Add explicit parsing rules for FETCH integration w3c/server-timing#87, by @noamr.
-
-
1 pull request received 11 new comments.
-
Add explicit parsing rules for FETCH integration w3c/server-timing#87 (11 comments by @noamr, @yoavweiss)
-
w3c/navigation-timing
-
1 issue opened.
-
Should pages with different COOP be able to get unload event start/end. w3c/navigation-timing#169, by @hemeryar.
-
-
5 issues received 13 new comments.
-
How should prefetch be exposed? w3c/navigation-timing#163 (3 comments by @igrigorik, @jeremyroman, @sefeng211)
-
Lack of Feature Parity with Performace.measure() in Level 2 w3c/navigation-timing#154 (2 comments by @nicjansma, @yoavweiss)
-
Should pages with different COOP be able to get unload event start/end. w3c/navigation-timing#169 (2 comments by @noamr, @yoavweiss)
-
A scenario where transferSize is 0 for non cached loads (or may be not) w3c/navigation-timing#146 (2 comments by @noamr, @yoavweiss)
-
1 pull request opened.
-
Hide redirectStart and redirectEnd for navigations with cross-origin redirects w3c/navigation-timing#170, by @noamr.
-
-
2 pull requests merged.
-
Hide redirectStart and redirectEnd for navigations with cross-origin redirects w3c/navigation-timing#170.
-
Fix typo in markup w3c/navigation-timing#162.
-
-
3 pull requests received 9 new comments.
-
Hide redirectStart and redirectEnd for navigations with cross-origin redirects w3c/navigation-timing#170 (5 comments by @noamr, @yoavweiss)
-
Add a landing attribute to PerformanceNavigationTiming w3c/navigation-timing#161 (3 comments by @jakearchibald, @marcelduran, @yoavweiss)
-
w3c/reporting
-
1 issue opened.
-
Are report type extensible? w3c/reporting#250, by @Marwansabbouh.
-
-
1 issue received 1 new comment.
w3c/resource-timing
-
1 issue received 2 new comments.
-
Add tests for not-same-site nested contexts w3c/resource-timing#204 (2 comments by @tommckee1, @yoavweiss)
-
-
1 pull request received 2 new comments.
w3c/event-timing
-
1 issue closed.
-
CfC: Adopt Event Timing into the WebPerfWG as a Working Draft w3c/event-timing#112.
-
-
1 issue received 1 new comment.
-
CfC: Adopt Event Timing into the WebPerfWG as a Working Draft w3c/event-timing#112 (1 comment by @yoavweiss)
-
w3c/largest-contentful-paint
-
1 issue closed.
-
CfC: Adopt LCP into the WebPerfWG as a Working Draft w3c/largest-contentful-paint#87.
-
-
1 issue received 1 new comment.
-
CfC: Adopt LCP into the WebPerfWG as a Working Draft w3c/largest-contentful-paint#87 (1 comment by @yoavweiss)
-
w3c/requestidlecallback
-
2 pull requests closed.
-
Define algorithm for determining whether high priority work exists. w3c/requestidlecallback#88.
-
Better define deadline w3c/requestidlecallback#78.
-
-
3 pull requests received 3 new comments.
-
Editorial: Use the HTML spec's timers infrastructure for `timeout` w3c/requestidlecallback#98 (1 comment by @yoavweiss)
-
Define algorithm for determining whether high priority work exists. w3c/requestidlecallback#88 (1 comment by @yoavweiss)
-
TR publications
-
6 documents published.
-
High Resolution Time published twice as a Working Draft. History of High Resolution Time
-
Resource Timing Level 2 published 3 times as a Working Draft. History of Resource Timing Level 2
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Participants
-
3 participants joined.
-
John Engebretson (Amazon) joined.
-
Chengzhong Wu (Alibaba Group) joined.
-
Alon Kochba (Wix.com Ltd.) joined.
-
-
3 participants left.
-
Scott Gifford (Amazon) left.
-
LI ZHOU (Alibaba Group) left.
-
Jinxin She (Alibaba Group) left.
-
-
1 organization joined.
-
Wix.com Ltd. joined.
-
GitHub
w3c/performance-timeline
-
1 issue opened.
-
`performance entry buffer` should be exported w3c/performance-timeline#196, by @yoavweiss.
-
-
1 issue closed.
-
`performance entry buffer` should be exported w3c/performance-timeline#196.
-
-
1 issue received 1 new comment.
-
Fire Paint Timing events for soft navigations w3c/performance-timeline#168 (1 comment by @yoavweiss)
-
-
2 pull requests opened.
-
Export performance entry buffer w3c/performance-timeline#198, by @npm1.
-
Add some exports used elsewhere w3c/performance-timeline#197, by @npm1.
-
-
3 pull requests merged.
-
Export performance entry buffer w3c/performance-timeline#198.
-
Add some exports used elsewhere w3c/performance-timeline#197.
-
Expose everywhere w3c/performance-timeline#193.
-
-
2 pull requests received 5 new comments.
w3c/navigation-timing
-
1 issue opened.
-
ToT spec has a bunch of respec warnings and errors w3c/navigation-timing#167, by @yoavweiss.
-
-
4 issues closed.
-
workerStart should be clearly defined as applicable to the last SW w3c/navigation-timing#100.
-
Load event timings are not well-defined w3c/navigation-timing#101.
-
Should about:blank have a PerformanceNavigationTiming? w3c/navigation-timing#155.
-
ToT spec has a bunch of respec warnings and errors w3c/navigation-timing#167.
-
-
4 issues received 7 new comments.
-
workerStart should be clearly defined as applicable to the last SW w3c/navigation-timing#100 (1 comment by @noamr)
-
Should about:blank have a PerformanceNavigationTiming? w3c/navigation-timing#155 (1 comment by @noamr)
-
1 pull request opened.
-
Fix multiple lint warnings: w3c/navigation-timing#168, by @noamr.
-
-
1 pull request merged.
-
Fix multiple lint warnings: w3c/navigation-timing#168.
-
-
2 pull requests received 4 new comments.
-
Add a landing attribute to PerformanceNavigationTiming w3c/navigation-timing#161 (3 comments by @andydavies, @jakearchibald, @marcelduran)
-
w3c/resource-timing
-
3 issues opened.
-
Discussion: Media reporting & range requests w3c/resource-timing#320, by @noamr.
-
Remove application cache references (in non-normative section) w3c/resource-timing#317, by @domenic.
-
Clarify RT entry creation when iframe changes `src` w3c/resource-timing#316, by @noamr.
-
-
5 issues closed.
-
Remove application cache references (in non-normative section) w3c/resource-timing#317.
-
Missing tests following the Fetch integration w3c/resource-timing#286.
-
Should favicon loading times be exposed to the document? w3c/resource-timing#299.
-
"Queue a task to run fire a buffer full event" needs to have a task queue w3c/resource-timing#249.
-
-
6 issues received 15 new comments.
-
Clarify RT entry creation when iframe changes `src` w3c/resource-timing#316 (6 comments by @achristensen07, @noamr, @yoavweiss)
-
Consider to limit the max size of resource timing buffer w3c/resource-timing#304 (4 comments by @npm1, @smaug----)
-
"Queue a task to run fire a buffer full event" needs to have a task queue w3c/resource-timing#249 (2 comments by @noamr, @yoavweiss)
-
Remove application cache references (in non-normative section) w3c/resource-timing#317 (1 comment by @yoavweiss)
-
spec what requestStart, responseStart, and responseEnd should represent when service worker is involved w3c/resource-timing#119 (1 comment by @noamr)
-
-
6 pull requests opened.
-
Editorial: Remove 'relevant application caches' w3c/resource-timing#318, by @noamr.
-
Override spec status for auto-publishing w3c/resource-timing#315, by @yoavweiss.
-
Fix up a missing section w3c/resource-timing#312, by @yoavweiss.
-
List all the attributes that will get masked when TAO fails w3c/resource-timing#311, by @tommckee1.
-
Clean up unused definitions and other respec errors w3c/resource-timing#310, by @yoavweiss.
-
Fix a link to the HR-TIME spec w3c/resource-timing#308, by @tommckee1.
-
-
7 pull requests merged.
-
Minor clarity improvement in Privacy & Security section w3c/resource-timing#307.
-
Editorial: Remove 'relevant application caches' w3c/resource-timing#318.
-
Override spec status for auto-publishing w3c/resource-timing#315.
-
List all the attributes that will get masked when TAO fails w3c/resource-timing#311.
-
Fix up a missing section w3c/resource-timing#312.
-
Clean up unused definitions and other respec errors w3c/resource-timing#310.
-
Fix a link to the HR-TIME spec w3c/resource-timing#308.
-
-
2 pull requests reopened.
-
Expose everywhere w3c/resource-timing#302, by @Ms2ger.
-
Fix a link to the HR-TIME spec w3c/resource-timing#308, by @tommckee1.
-
-
9 pull requests received 32 new comments.
-
Clean up unused definitions and other respec errors w3c/resource-timing#310 (10 comments by @npm1, @yoavweiss)
-
Fix a link to the HR-TIME spec w3c/resource-timing#308 (7 comments by @npm1, @tommckee1, @yoavweiss)
-
List all the attributes that will get masked when TAO fails w3c/resource-timing#311 (6 comments by @tommckee1, @yoavweiss)
-
Minor clarity improvement in Privacy & Security section w3c/resource-timing#307 (4 comments by @npm1, @patrickhulce, @w3cbot)
-
w3c/resource-timing#319 (1 comment by @w3cbot)
-
w3c/resource-timing#314 (1 comment by @w3cbot)
-
w3c/resource-timing#313 (1 comment by @w3cbot)
-
w3c/resource-timing#309 (1 comment by @w3cbot)
-
w3c/user-timing
-
1 issue received 5 new comments.
-
1 pull request merged.
-
Expose everywhere w3c/user-timing#85.
-
-
1 pull request reopened.
-
Expose everywhere w3c/user-timing#85, by @Ms2ger.
-
-
1 pull request received 2 new comments.
w3c/longtasks
-
2 issues closed.
-
Names are inconsistent w3c/longtasks#53.
-
"multiple-contexts" doesn't seem useful w3c/longtasks#67.
-
-
4 issues received 7 new comments.
-
Can we find which script or function is taking longer than 50 ms? w3c/longtasks#28 (1 comment by @yoavweiss)
-
1 pull request opened.
-
Add note about naming inconsistency w3c/longtasks#97, by @npm1.
-
-
1 pull request merged.
-
Add note about naming inconsistency w3c/longtasks#97.
-
-
1 pull request received 2 new comments.
w3c/element-timing
-
1 pull request opened.
-
Remove several unneeded hard-coded refs w3c/element-timing#69, by @npm1.
-
-
1 pull request merged.
-
Remove several unneeded hard-coded refs w3c/element-timing#69.
-
w3c/hr-time
-
1 pull request opened.
-
Add a privacy section w3c/hr-time#134, by @noamr.
-
-
2 pull requests merged.
-
Expose everywhere w3c/hr-time#130.
-
Add a privacy section w3c/hr-time#134.
-
-
2 pull requests received 4 new comments.
-
w3c/hr-time#135 (1 comment by @w3cbot)
w3c/event-timing
-
1 issue opened.
-
Move some definition of interactionID to UI Events w3c/event-timing#114, by @npm1.
-
-
2 issues closed.
-
Proposal: add page visibility attribute to PerformanceEventTiming entry w3c/event-timing#110.
-
interactionID should be harmonized with activation triggering input events w3c/event-timing#105.
-
-
2 issues received 4 new comments.
-
Proposal: add page visibility attribute to PerformanceEventTiming entry w3c/event-timing#110 (2 comments by @npm1)
-
interactionID should be harmonized with activation triggering input events w3c/event-timing#105 (2 comments by @annevk, @npm1)
-
w3c/server-timing
-
1 pull request reopened.
-
Expose everywhere w3c/server-timing#84, by @Ms2ger.
-
w3c/requestidlecallback
-
3 issues closed.
-
The order of idle callbacks across windows is inconsistent between spec & UAs w3c/requestidlecallback#82.
-
timeRemaining() step 4 should define what it means to have a "time-critical task pending" w3c/requestidlecallback#87.
-
6.2. invoke idle callbacks algorithm step 1 should be defined in terms of task sources having tasks enqueued w3c/requestidlecallback#86.
-
-
3 issues received 3 new comments.
-
The order of idle callbacks across windows is inconsistent between spec & UAs w3c/requestidlecallback#82 (1 comment by @noamr)
-
timeRemaining() step 4 should define what it means to have a "time-critical task pending" w3c/requestidlecallback#87 (1 comment by @noamr)
-
6.2. invoke idle callbacks algorithm step 1 should be defined in terms of task sources having tasks enqueued w3c/requestidlecallback#86 (1 comment by @noamr)
-
-
1 pull request opened.
-
Fix lint warnings w3c/requestidlecallback#99, by @noamr.
-
-
1 pull request merged.
-
Fix lint warnings w3c/requestidlecallback#99.
-
-
1 pull request received 5 new comments.
w3c/reporting
-
1 issue received 2 new comments.
w3c/largest-contentful-paint
-
1 issue closed.
-
Reset LCP for Single Page App soft navigations w3c/largest-contentful-paint#6.
-
-
1 issue received 1 new comment.
-
Reset LCP for Single Page App soft navigations w3c/largest-contentful-paint#6 (1 comment by @yoavweiss)
-