Web Performance Working Group - Activity in 2023
No matches.
Participants
-
2 participants left.
-
Ian Hickson (Google LLC) left.
-
Dave Pifke (Wikimedia Foundation) left.
-
GitHub
w3c/paint-timing
-
1 pull request received 16 new comments.
-
Include algorithms and concepts from Element Timing and LCP w3c/paint-timing#100 (16 comments by @clelland, @noamr)
-
w3c/navigation-timing
-
1 pull request opened.
-
Add notRestoredReasons to PerformanceNavigationTiming attribute w3c/navigation-timing#195, by @rubberyuzu.
-
w3c/beacon
-
1 issue received 2 new comments.
-
Ambiguity on "maximum data size" limit and enforcement w3c/beacon#38 (2 comments by @clelland, @collimarco)
-
w3c/network-error-logging
-
2 issues opened.
-
Distribute NEL policies with DNS w3c/network-error-logging#173, by @simon-friedberger.
-
WebSocket support w3c/network-error-logging#172, by @ricea.
-
-
2 issues received 6 new comments.
-
Distribute NEL policies with DNS w3c/network-error-logging#173 (4 comments by @clelland, @LPardue, @Sora2455, @SulemanAhmadd)
-
w3c/longtasks
-
2 pull requests reopened.
-
LoAF: add support for scripts w3c/longtasks#124, by @noamr.
-
LoAF: add support for scripts w3c/longtasks#124, by @noamr.
-
-
1 pull request received 15 new comments.
w3c/element-timing
-
1 issue opened.
-
Support Element Timing on Containers w3c/element-timing#79, by @andydavies.
-
w3c/reporting
-
1 issue opened.
w3c/long-animation-frames
-
1 issue closed.
-
[LoAF] is blockingDuration needed? w3c/long-animation-frames#8.
-
-
1 issue received 1 new comment.
Lifecycle
TR publications
-
6 documents published.
-
User Timing Level 3 published twice as a Candidate Recommendation Draft. History of User Timing Level 3
-
Long Tasks API published as a Working Draft. History of Long Tasks API
-
Paint Timing published twice as a Working Draft. History of Paint Timing
-
Reporting API published as a Working Draft. History of Reporting API
-
Participants
-
1 participant joined.
-
Madhavan Ramakrishnan (Techfriar) joined.
-
-
1 participant left.
-
Laurent Dang (Shopify) left.
-
-
1 organization joined.
-
Techfriar joined.
-
GitHub
w3c/longtasks
-
3 pull requests opened.
-
LoAF: add support for scripts w3c/longtasks#124, by @noamr.
-
LoAF: Add HTML monkey-patches w3c/longtasks#123, by @noamr.
-
LoAF initial spec w3c/longtasks#122, by @noamr.
-
-
1 pull request merged.
-
LoAF initial spec w3c/longtasks#122.
-
-
1 pull request closed.
-
LoAF: Add HTML monkey-patches w3c/longtasks#123.
-
-
1 pull request reopened.
-
LoAF: add support for scripts w3c/longtasks#124, by @noamr.
-
-
3 pull requests received 24 new comments.
w3c/paint-timing
-
2 pull requests opened.
-
Update .pr-preview.json w3c/paint-timing#101, by @clelland.
-
Include algorithms and concepts from Element Timing and LCP w3c/paint-timing#100, by @clelland.
-
-
2 pull requests merged.
-
Update .pr-preview.json w3c/paint-timing#101.
-
Update linkable references w3c/paint-timing#99.
-
-
1 pull request received 20 new comments.
-
Include algorithms and concepts from Element Timing and LCP w3c/paint-timing#100 (20 comments by @clelland, @noamr, @yoavweiss)
-
w3c/long-animation-frames
-
3 issues opened.
-
[LoAF] is blockingDuration needed? w3c/long-animation-frames#8, by @mmocny.
-
[LoAF] scheduler.yield() resolver sourceLocation seems broken w3c/long-animation-frames#9, by @mmocny.
-
[LoAF] Should be a way to switch script "Entry Point" without yielding. w3c/long-animation-frames#2, by @mmocny.
-
-
1 issue closed.
-
[LoAF] scheduler.yield() resolver sourceLocation seems broken w3c/long-animation-frames#9.
-
-
4 issues received 6 new comments.
-
[LoAF] Should be a way to switch script "Entry Point" without yielding. w3c/long-animation-frames#2 (2 comments by @mmocny, @noamr)
-
[LoAF] scheduler.yield() resolver sourceLocation seems broken w3c/long-animation-frames#9 (1 comment by @mmocny)
-
[LoAF] Allow for annotations for long animation frame to further help debugging w3c/long-animation-frames#3 (1 comment by @gilbertococchi)
w3c/network-error-logging
-
1 issue closed.
-
NEL scope different in the latest editor's draft and the original paper behind NEL w3c/network-error-logging#160.
-
-
3 issues received 6 new comments.
-
NEL scope different in the latest editor's draft and the original paper behind NEL w3c/network-error-logging#160 (2 comments by @mmocny, @simon-friedberger)
-
1 pull request opened.
-
Replace manual list of dependencies by automatically generated index w3c/network-error-logging#171, by @dontcallmedom.
-
-
1 pull request received 1 new comment.
-
Replace manual list of dependencies by automatically generated index w3c/network-error-logging#171 (1 comment by @dontcallmedom)
-
w3c/navigation-timing
-
2 issues opened.
-
Chore: Fix overloading in WebIDL w3c/navigation-timing#194, by @noamr.
-
Proposal: add timestamp for when "activation" or "dismissal" starts w3c/navigation-timing#193, by @noamr.
-
-
2 issues received 2 new comments.
-
Proposal: add timestamp for when "activation" or "dismissal" starts w3c/navigation-timing#193 (1 comment by @fergald)
-
Consider using `reload` instead of `back_forward` for "tab restore" w3c/navigation-timing#192 (1 comment by @noamr)
-
w3c/largest-contentful-paint
-
1 pull request opened.
-
Rebase LCP on top of w3c/paint-timing#100 w3c/largest-contentful-paint#121, by @clelland.
-
-
1 pull request received 7 new comments.
-
Rebase LCP on top of w3c/paint-timing#100 w3c/largest-contentful-paint#121 (7 comments by @clelland, @yoavweiss)
-
w3c/element-timing
-
1 pull request opened.
-
Refactor Element Timing on top of Paint Timing w3c/element-timing#78, by @clelland.
-
-
1 pull request received 1 new comment.
w3c/event-timing
-
1 issue received 1 new comment.
w3c/user-timing
-
2 issues closed.
-
Add `mark_feature_usage` as a recommended mark name w3c/user-timing#105.
-
Bring "Recommended Mark Names" back to User Timing L3 w3c/user-timing#103.
-
-
1 issue reopened.
-
Add `mark_feature_usage` as a recommended mark name w3c/user-timing#105, by @anniesullie.
-
-
2 issues received 2 new comments.
-
Bring "Recommended Mark Names" back to User Timing L3 w3c/user-timing#103 (1 comment by @anniesullie)
-
2 pull requests opened.
-
Clarify name for recommended mark for feature usag based on feedback w3c/user-timing#108, by @anniesullie.
-
Add mark_use_counter recommended use name. w3c/user-timing#107, by @anniesullie.
-
-
3 pull requests merged.
-
Clarify name for recommended mark for feature usag based on feedback w3c/user-timing#108.
-
Add mark_use_counter recommended use name. w3c/user-timing#107.
-
Add Recommended Mark Names section. w3c/user-timing#106.
-
-
2 pull requests received 16 new comments.
-
Add Recommended Mark Names section. w3c/user-timing#106 (9 comments by @anniesullie, @nicjansma, @npm1, @yoavweiss)
-
Add mark_use_counter recommended use name. w3c/user-timing#107 (7 comments by @anniesullie, @ksylor, @yoavweiss)
-
w3c/performance-timeline
-
1 issue opened.
-
"Queue a navigation performance entry" doesn't seem to be used w3c/performance-timeline#209, by @yoavweiss.
-
-
1 issue received 2 new comments.
-
"Queue a navigation performance entry" doesn't seem to be used w3c/performance-timeline#209 (2 comments by @clelland, @noamr)
-
w3c/reporting
-
1 pull request opened.
-
Export dfn of 'visible to ReportingObserver' w3c/reporting#266, by @dontcallmedom.
-
-
1 pull request merged.
-
Export dfn of 'visible to ReportingObserver' w3c/reporting#266.
-
TR publications
-
5 documents published.
-
Performance Timeline published as a Candidate Recommendation Draft. History of Performance Timeline
-
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
-
Network Error Logging published twice as a Working Draft. History of Network Error Logging
-
GitHub
w3c/user-timing
-
3 issues opened.
-
Add `mark_feature_usage` as a recommended mark name w3c/user-timing#105, by @anniesullie.
-
Add w3c/user-timing#104, by @anniesullie.
-
Bring "Recommended Mark Names" back to User Timing L3 w3c/user-timing#103, by @anniesullie.
-
-
1 issue closed.
-
Add w3c/user-timing#104.
-
-
1 pull request opened.
-
Add Recommended Mark Names section. w3c/user-timing#106, by @anniesullie.
-
-
1 pull request received 31 new comments.
-
Add Recommended Mark Names section. w3c/user-timing#106 (31 comments by @anniesullie, @clelland, @jyasskin, @marcoscaceres, @npm1, @yoavweiss)
-
w3c/event-timing
-
1 issue opened.
-
Fix spec build issues w3c/event-timing#135, by @mmocny.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Fix #135 remove empty attribute w3c/event-timing#136, by @mmocny.
-
-
1 pull request merged.
-
InteractionID & Count Explainer w3c/event-timing#133.
-
-
2 pull requests received 7 new comments.
w3c/largest-contentful-paint
-
1 issue opened.
-
What exactly does loadTime attribute mean? w3c/largest-contentful-paint#118, by @xiaofud.
-
-
2 issues received 3 new comments.
-
What exactly does loadTime attribute mean? w3c/largest-contentful-paint#118 (2 comments by @clelland, @xiaofud)
-
-
2 pull requests opened.
-
Create SECURITY.md w3c/largest-contentful-paint#120, by @lunaroco33.
-
Update README.md for video w3c/largest-contentful-paint#119, by @tunetheweb.
-
-
1 pull request closed.
-
Create SECURITY.md w3c/largest-contentful-paint#120.
-
-
1 pull request received 3 new comments.
w3c/element-timing
-
1 pull request opened.
-
Update a couple of broken references w3c/element-timing#77, by @clelland.
-
-
1 pull request merged.
-
Update a couple of broken references w3c/element-timing#77.
-
w3c/navigation-timing
-
1 issue opened.
-
Consider using `reload` instead of `back_forward` for "tab restore" w3c/navigation-timing#192, by @noamr.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Update diagram to make unload parallel w3c/navigation-timing#191, by @noamr.
-
-
1 pull request merged.
-
Update diagram to make unload parallel w3c/navigation-timing#191.
-
-
1 pull request received 7 new comments.
-
Update diagram to make unload parallel w3c/navigation-timing#191 (7 comments by @noamr, @tunetheweb)
-
w3c/longtasks
-
1 issue received 3 new comments.
-
2 pull requests opened.
-
[Editorial] LoAF explainer: Changed -> improved w3c/longtasks#119, by @noamr.
-
Some LoAF explainer edits for TAG review w3c/longtasks#118, by @noamr.
-
-
2 pull requests merged.
-
[Editorial] LoAF explainer: Changed -> improved w3c/longtasks#119.
-
Some LoAF explainer edits for TAG review w3c/longtasks#118.
-
-
1 pull request received 7 new comments.
-
Some LoAF explainer edits for TAG review w3c/longtasks#118 (7 comments by @clelland, @noamr, @yoavweiss)
-
w3c/network-error-logging
-
3 issues opened.
-
Only Fetch? w3c/network-error-logging#170, by @LPardue.
-
Network Error Logging w3c/network-error-logging#169, by @Appai207.
-
Clarify client flexibility w3c/network-error-logging#168, by @simon-friedberger.
-
-
2 issues closed.
-
Network Error Logging w3c/network-error-logging#169.
-
Republish with a non-leveled shortname w3c/network-error-logging#165.
-
-
3 issues received 6 new comments.
-
NEL scope different in the latest editor's draft and the original paper behind NEL w3c/network-error-logging#160 (4 comments by @clelland, @noamr, @yoavweiss)
-
Proposal: Convey Extended DNS Errors w3c/network-error-logging#129 (1 comment by @simon-friedberger)
-
-
1 pull request opened.
-
Reflect change of shortname (drop level) w3c/network-error-logging#167, by @caribouW3.
-
-
1 pull request merged.
-
Reflect change of shortname (drop level) w3c/network-error-logging#167.
-
w3c/paint-timing
-
1 pull request opened.
-
Update linkable references w3c/paint-timing#99, by @clelland.
-
w3c/long-animation-frames
-
1 issue reopened.
-
[LoAF] Allow for annotations for long animation frame to further help debugging w3c/long-animation-frames#3, by @noamr.
-
-
1 issue received 5 new comments.
-
[LoAF] Allow for annotations for long animation frame to further help debugging w3c/long-animation-frames#3 (5 comments by @jarmit, @mmocny, @noamr)
-
w3c/hr-time
-
1 issue opened.
-
Describe the risk of exposing additional hardware clocks w3c/hr-time#164, by @jyasskin.
-
-
1 issue received 1 new comment.
-
Add description of various timer related vulnerabilities to the security and privacy sections w3c/hr-time#102 (1 comment by @jyasskin)
-
w3c/reporting
-
1 issue opened.
-
Reports should be queued for reporting observers even when no endpoint exists w3c/reporting#265, by @clelland.
-
w3c/performance-timeline
-
1 pull request merged.
-
Add navigationId to PerformanceEntry w3c/performance-timeline#192.
-
-
1 pull request received 5 new comments.
-
Add navigationId to PerformanceEntry w3c/performance-timeline#192 (5 comments by @clelland, @yoavweiss)
-
TR publications
-
5 documents published.
-
Network Error Logging published twice as a Working Draft. History of Network Error Logging
-
Largest Contentful Paint published 3 times as a Working Draft. History of Largest Contentful Paint
-
Past meetings
Participants
-
2 participants joined.
-
Tariq Rafique (Salesforce) joined.
-
Thomas Nguyen (Google LLC) joined.
-
-
1 participant left.
-
Giacomo Zecchini (W3C Invited Experts) left.
-
GitHub
w3c/network-error-logging
-
6 issues opened.
-
Rebase NEL on top of Fetch w3c/network-error-logging#166, by @clelland.
-
Republish with a non-leveled shortname w3c/network-error-logging#165, by @caribouW3.
-
Auto-publishing to /TR/ is failing w3c/network-error-logging#161, by @clelland.
-
NEL scope different in the latest editor's draft and the original paper behind NEL w3c/network-error-logging#160, by @polcak.
-
Report-To header no longer defined w3c/network-error-logging#159, by @nicjansma.
-
JSON validation schema w3c/network-error-logging#156, by @rfmoz.
-
-
7 issues closed.
-
Clear report body fields based on `phase` and report destination w3c/network-error-logging#105.
-
Auto-publishing to /TR/ is failing w3c/network-error-logging#161.
-
SRI violation reporting w3c/network-error-logging#155.
-
Move sampling rate into Reporting? w3c/network-error-logging#71.
-
One origin can set a policy for a different origin w3c/network-error-logging#117.
-
Broken references in Network Error Logging w3c/network-error-logging#132.
-
Use camelCase for field names w3c/network-error-logging#97.
-
-
14 issues received 40 new comments.
-
Ensure that NEL does not report on requests that users do not make voluntarily. w3c/network-error-logging#150 (13 comments by @clelland, @LPardue, @martinthomson, @neilstuartcraig, @polcak, @yoavweiss)
-
False claim in privacy section w3c/network-error-logging#121 (6 comments by @clelland, @MattMenke2, @yoavweiss)
-
Clear report body fields based on `phase` and report destination w3c/network-error-logging#105 (6 comments by @clelland, @martinthomson)
-
Auto-publishing to /TR/ is failing w3c/network-error-logging#161 (2 comments by @caribouW3, @clelland)
-
Allow limiting information in URLs exposed in NEL w3c/network-error-logging#151 (2 comments by @clelland, @valenting)
-
`request_headers` may send SameSite cookies cross-site w3c/network-error-logging#111 (2 comments by @clelland, @yoavweiss)
-
NEL header injection attack allows stealing HttpOnly cookies w3c/network-error-logging#112 (1 comment by @clelland)
-
One origin can set a policy for a different origin w3c/network-error-logging#117 (1 comment by @clelland)
-
-
5 pull requests opened.
-
Remove unnecessary fields and URL parts w3c/network-error-logging#164, by @clelland.
-
Update index.html w3c/network-error-logging#163, by @caribouW3.
-
Update index.html w3c/network-error-logging#162, by @caribouW3.
-
Fix links to "phase" w3c/network-error-logging#158, by @clelland.
-
Add note about transparent MitM proxies w3c/network-error-logging#157, by @clelland.
-
-
4 pull requests merged.
-
Remove unnecessary fields and URL parts w3c/network-error-logging#164.
-
Update index.html w3c/network-error-logging#163.
-
Update index.html w3c/network-error-logging#162.
-
Fix links to "phase" w3c/network-error-logging#158.
-
-
2 pull requests received 4 new comments.
-
Remove unnecessary fields and URL parts w3c/network-error-logging#164 (2 comments by @clelland, @yoavweiss)
-
w3c/performance-timeline
-
1 pull request received 15 new comments.
-
Add navigationId to PerformanceEntry w3c/performance-timeline#192 (15 comments by @clelland, @Krinkle, @noamr, @yoavweiss)
-
w3c/long-animation-frames
-
2 issues opened.
-
[LoAF] Allow for annotations for long animation frame to further help debugging w3c/long-animation-frames#3, by @jarmit.
-
[LoAF] Support custom durationThreshold w3c/long-animation-frames#4, by @mmocny.
-
-
1 issue received 1 new comment.
w3c/beacon
-
1 issue closed.
-
Setup auto publishing w3c/beacon#76.
-
w3c/requestidlecallback
-
1 issue closed.
-
Setup auto publishing w3c/requestidlecallback#100.
-
-
1 issue received 1 new comment.
w3c/resource-timing
-
1 issue opened.
-
Expose Content-Encoding to ResourceTiming w3c/resource-timing#381, by @nicjansma.
-
-
1 issue closed.
-
Include Content Type w3c/resource-timing#203.
-
-
4 issues received 5 new comments.
-
Resource Initiator Information Reporting w3c/resource-timing#380 (2 comments by @nicjansma, @yoavweiss)
-
-
1 pull request received 3 new comments.
-
Add http method to ResourceTiming interface w3c/resource-timing#375 (3 comments by @sohomdatta1, @yoavweiss)
-
w3c/reporting
-
2 issues received 3 new comments.
-
Could there be a way to collect Crash/Intervention reports without collecting Deprecation reports? w3c/reporting#263 (1 comment by @rfmoz)
w3c/element-timing
-
1 issue received 1 new comment.
-
1 pull request received 3 new comments.
-
Replace "viewport" with "Initial Containing Block" w3c/element-timing#76 (3 comments by @clelland, @npm1)
-
w3c/web-performance
-
1 issue opened.
-
Explicitly including reliability in scope w3c/web-performance#59, by @aluhrs13.
-
-
1 issue closed.
-
Remove API key from the group homepage w3c/web-performance#57.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
W3C WebPerf 2023 Charter w3c/web-performance#58, by @nicjansma.
-
w3c/largest-contentful-paint
-
1 issue opened.
-
Elements using CSS image-set() for background should be considered LCP candidates w3c/largest-contentful-paint#116, by @ryantownsend.
-
-
1 issue closed.
-
Broken references in Largest Contentful Paint w3c/largest-contentful-paint#109.
-
-
1 issue received 2 new comments.
-
Elements using CSS image-set() for background should be considered LCP candidates w3c/largest-contentful-paint#116 (2 comments by @clelland, @yoavweiss)
-
-
1 pull request opened.
-
Fix ambiguous references w3c/largest-contentful-paint#117, by @clelland.
-
-
3 pull requests merged.
-
Fix ambiguous references w3c/largest-contentful-paint#117.
-
Move viewport link to visual viewport w3c/largest-contentful-paint#110.
-
Add final slash to ED URL w3c/largest-contentful-paint#102.
-
-
2 pull requests received 2 new comments.
Lifecycle
-
1 charter extension.
-
Charter extended until 30 November 2023.
-
Participants
-
1 participant joined.
-
Nidhi Jaju (Google LLC) joined.
-
GitHub
w3c/element-timing
-
1 pull request opened.
-
Replace "viewport" with "Initial Containing Block" w3c/element-timing#76, by @clelland.
-
w3c/largest-contentful-paint
-
1 pull request opened.
-
Add entropy calculation w3c/largest-contentful-paint#115, by @clelland.
-
-
1 pull request received 1 new comment.
w3c/network-error-logging
-
1 issue opened.
-
SRI violation reporting w3c/network-error-logging#155, by @xtuc.
-
-
1 issue received 1 new comment.
-
Allow limiting information in URLs exposed in NEL w3c/network-error-logging#151 (1 comment by @clelland)
-
w3c/performance-timeline
-
1 pull request received 2 new comments.
w3c/resource-timing
-
1 issue opened.
-
Resource Initiator Information Reporting w3c/resource-timing#380, by @yashjoshi-dotcom.
-
w3c/long-animation-frames
-
1 issue opened.
-
[LoAF] Should it be easier to link LoAF to INP entries w3c/long-animation-frames#5, by @tunetheweb.
-
-
1 issue received 1 new comment.
-
[LoAF] Should it be easier to link LoAF to INP entries w3c/long-animation-frames#5 (1 comment by @noamr)
-
w3c/reporting
-
1 pull request received 3 new comments.
-
Wire up a way for users to disable particular kinds of reporting. w3c/reporting#254 (3 comments by @jyasskin, @npdoty, @pes10k)
-
w3c/longtasks
-
1 pull request opened.
-
Update README.md w3c/longtasks#114, by @vanderhoop.
-
-
1 pull request closed.
-
Update README.md w3c/longtasks#114.
-
TR publications
-
6 documents published.
-
High Resolution Time published as a Working Draft. History of High Resolution Time
-
Long Tasks API published 3 times as a Working Draft. History of Long Tasks API
-
Event Timing API published as a Working Draft. History of Event Timing API
-
Paint Timing published as a Working Draft. History of Paint Timing
-
GitHub
w3c/performance-timeline
-
1 pull request received 1 new comment.
w3c/web-performance
-
1 issue opened.
-
Remove API key from the group homepage w3c/web-performance#57, by @xfq.
-
-
2 issues closed.
-
"Performance APIs, security and privacy" document w3c/web-performance#46.
-
The charter should discuss open issues around privacy w3c/web-performance#51.
-
-
3 issues received 4 new comments.
-
The charter should discuss open issues around privacy w3c/web-performance#51 (1 comment by @yoavweiss)
-
2 pull requests opened.
-
A couple of reference drafts and URIs corrected w3c/web-performance#56, by @caribouW3.
-
draft w3c/web-performance#55, by @caribouW3.
-
-
1 pull request merged.
-
A couple of reference drafts and URIs corrected w3c/web-performance#56.
-
-
1 pull request closed.
-
draft w3c/web-performance#55.
-
w3c/hr-time
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Editorial: Add an index to the appendices w3c/hr-time#163, by @rakuco.
-
-
1 pull request merged.
-
Editorial: Add an index to the appendices w3c/hr-time#163.
-
-
1 pull request received 3 new comments.
-
Editorial: Add an index to the appendices w3c/hr-time#163 (3 comments by @rakuco, @w3cbot, @yoavweiss)
-
w3c/longtasks
-
3 pull requests opened.
-
Update loaf-explainer.md w3c/longtasks#113, by @noamr.
-
Update index.bs w3c/longtasks#112, by @caribouW3.
-
Create auto-publish.yml w3c/longtasks#111, by @caribouW3.
-
-
4 pull requests merged.
-
Update loaf-explainer.md w3c/longtasks#113.
-
Add overview to loaf explainer w3c/longtasks#110.
-
Update index.bs w3c/longtasks#112.
-
Create auto-publish.yml w3c/longtasks#111.
-
-
1 pull request received 2 new comments.
w3c/network-error-logging
-
1 issue closed.
-
2 issues received 2 new comments.
-
Ensure that NEL does not report on requests that users do not make voluntarily. w3c/network-error-logging#150 (1 comment by @polcak)
-
The academic paper behind NEL expected that users are able to opt-out from NEL but such option is not required from user agents by the draft standard w3c/network-error-logging#152 (1 comment by @polcak)
-
-
2 pull requests opened.
-
Rename auto-publish.yml to auto-publish.yml w3c/network-error-logging#154, by @caribouW3.
-
Create auto-publish.yml w3c/network-error-logging#153, by @caribouW3.
-
-
2 pull requests merged.
-
Rename auto-publish.yml to auto-publish.yml w3c/network-error-logging#154.
-
Create auto-publish.yml w3c/network-error-logging#153.
-
w3c/largest-contentful-paint
-
1 issue received 1 new comment.
w3c/element-timing
-
1 issue opened.
-
Should MathML be included? w3c/element-timing#75, by @sefeng211.
-
-
1 issue closed.
-
Should MathML be included? w3c/element-timing#75.
-
-
1 issue received 1 new comment.
w3c/paint-timing
-
4 pull requests opened.
-
fix for auto-publishing w3c/paint-timing#98, by @caribouW3.
-
Update auto-publish.yml w3c/paint-timing#97, by @caribouW3.
-
Update auto-publish.yml w3c/paint-timing#96, by @caribouW3.
-
Update auto-publish.yml w3c/paint-timing#95, by @caribouW3.
-
-
3 pull requests merged.
-
fix for auto-publishing w3c/paint-timing#98.
-
Update auto-publish.yml w3c/paint-timing#97.
-
Update auto-publish.yml w3c/paint-timing#95.
-
-
1 pull request closed.
-
Update auto-publish.yml w3c/paint-timing#96.
-
TR publications
-
1 document published.
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Participants
-
1 participant left.
-
Staphany Park (Google LLC) left.
-
GitHub
w3c/web-performance
-
8 issues closed.
-
Consider including userland conventions and protocols w3c/web-performance#52.
-
Consider unifying specifications w3c/web-performance#44.
-
"HR-time" can maybe be renamed to "time" w3c/web-performance#53.
-
Remove Preload from charter? w3c/web-performance#50.
-
Privacy Preserving Monitoring w3c/web-performance#45.
-
Remove Page Visibility from charter? w3c/web-performance#49.
-
Add LCP to charter w3c/web-performance#47.
-
Add Event Timing to charter w3c/web-performance#48.
-
-
9 issues received 9 new comments.
-
The charter should discuss open issues around privacy w3c/web-performance#51 (1 comment by @yoavweiss)
-
Consider including userland conventions and protocols w3c/web-performance#52 (1 comment by @yoavweiss)
-
w3c/network-error-logging
-
6 issues opened.
-
Allow limiting information in URLs exposed in NEL w3c/network-error-logging#151, by @polcak.
-
Ensure that NEL does not report on requests that users do not make voluntarily. w3c/network-error-logging#150, by @polcak.
-
Register with IANA? w3c/network-error-logging#149, by @LPardue.
-
Remove support for HTTP Trailers w3c/network-error-logging#146, by @clelland.
-
Report-To: {"endpoints":{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=ETcZDK308tPXIcI8k4EK6CpOy6EZbQAti1VMop765bZHMTlFClnF6qT8OBb93AeAVO9pgxakliCDtYfKJbrcJGc4lQ3ZoUCz4RORxa%2FEgAZHPmqmdWdJTJf5oyACWHo5WQ%3D%3D"},"group":"cf-nel","max_age":604800} w3c/network-error-logging#142, by @rkabiri1988.
-
7 issues closed.
-
NEL cache should be time-bound w3c/network-error-logging#139.
-
Remove support for HTTP Trailers w3c/network-error-logging#146.
-
Link to updated reporting interface w3c/network-error-logging#131.
-
NEL suborigin policies should not be able to generate reports on success w3c/network-error-logging#141.
-
NEL cache should be partitioned w3c/network-error-logging#138.
-
Consider limiting scope of NEL registration w3c/network-error-logging#140.
-
-
7 issues received 22 new comments.
-
Remove support for HTTP Trailers w3c/network-error-logging#146 (9 comments by @clelland, @LPardue, @noamr, @yoavweiss)
-
NEL cache should be time-bound w3c/network-error-logging#139 (4 comments by @clelland, @polcak, @yoavweiss)
-
Consider limiting scope of NEL registration w3c/network-error-logging#140 (3 comments by @clelland, @polcak)
-
The academic paper behind NEL expected that users are able to opt-out from NEL but such option is not required from user agents by the draft standard w3c/network-error-logging#152 (1 comment by @clelland)
-
Report-To: {"endpoints":{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=ETcZDK308tPXIcI8k4EK6CpOy6EZbQAti1VMop765bZHMTlFClnF6qT8OBb93AeAVO9pgxakliCDtYfKJbrcJGc4lQ3ZoUCz4RORxa%2FEgAZHPmqmdWdJTJf5oyACWHo5WQ%3D%3D"},"group":"cf-nel","max_age":604800} w3c/network-error-logging#142 (1 comment by @clelland)
-
-
5 pull requests opened.
-
Remove trailer processing w3c/network-error-logging#148, by @clelland.
-
Make NEL policies stale after 48h w3c/network-error-logging#147, by @clelland.
-
Fix broken references w3c/network-error-logging#145, by @clelland.
-
Ensure that subdomain policies are only for DNS. w3c/network-error-logging#144, by @clelland.
-
Partition the policy cache w3c/network-error-logging#143, by @clelland.
-
-
5 pull requests merged.
-
Make NEL policies stale after 48h w3c/network-error-logging#147.
-
Remove trailer processing w3c/network-error-logging#148.
-
Fix broken references w3c/network-error-logging#145.
-
Ensure that subdomain policies are only for DNS. w3c/network-error-logging#144.
-
Partition the policy cache w3c/network-error-logging#143.
-
-
3 pull requests received 6 new comments.
-
Make NEL policies stale after 48h w3c/network-error-logging#147 (4 comments by @clelland, @yoavweiss)
-
Ensure that subdomain policies are only for DNS. w3c/network-error-logging#144 (1 comment by @yoavweiss)
-
w3c/reporting
-
1 issue received 1 new comment.
-
Could there be a way to collect Crash/Intervention reports without collecting Deprecation reports? w3c/reporting#263 (1 comment by @aluhrs13)
-
w3c/longtasks
-
2 pull requests opened.
-
Add overview to loaf explainer w3c/longtasks#110, by @noamr.
-
loaf-explainer: Include some info about TBT w3c/longtasks#109, by @noamr.
-
-
1 pull request merged.
-
loaf-explainer: Include some info about TBT w3c/longtasks#109.
-
-
2 pull requests received 5 new comments.
w3c/largest-contentful-paint
-
2 issues opened.
-
High entropy image excluded from LCP due to the image covering the viewport w3c/largest-contentful-paint#114, by @valiantvu.
-
Element Timing spec is still within WICG rather than W3 w3c/largest-contentful-paint#113, by @andydavies.
-
-
2 issues received 3 new comments.
-
Very large transparent SVG should not count as LCP w3c/largest-contentful-paint#72 (2 comments by @clelland, @onlinebizsoft)
-
Elements that are obscured by other elements shouldn't be considered w3c/largest-contentful-paint#70 (1 comment by @nhoizey)
-
w3c/navigation-timing
-
2 issues closed.
-
How should prefetch be exposed? w3c/navigation-timing#163.
-
Report that Critical-CH was used to restart a navigation w3c/navigation-timing#177.
-
-
1 pull request merged.
-
Add criticalCHRestart w3c/navigation-timing#188.
-
-
1 pull request received 2 new comments.
w3c/performance-timeline
-
1 issue received 1 new comment.
-
API shape for monitoring new navigation-like entries such as App History, BFCache, etc w3c/performance-timeline#182 (1 comment by @clelland)
-
w3c/event-timing
-
1 issue opened.
-
Expose interactionId to keypress w3c/event-timing#134, by @zuoaoyuan.
-
-
1 issue closed.
-
Consider expose interactionId to keypress, input, and more other event types w3c/event-timing#132.
-
-
1 issue received 1 new comment.
-
Consider expose interactionId to keypress, input, and more other event types w3c/event-timing#132 (1 comment by @zuoaoyuan)
-
w3c/resource-timing
-
1 issue received 1 new comment.
-
Expose a way to link a call to fetch to an individual PerformanceResourceTiming object w3c/resource-timing#102 (1 comment by @qtow)
-
TR publications
-
3 documents published.
-
Resource Timing published twice as a Candidate Recommendation Draft. History of Resource Timing
-
Reporting API published as a Working Draft. History of Reporting API
-
Participants
-
1 participant left.
-
Vivek Sekhar (Google LLC) left.
-
GitHub
w3c/network-error-logging
-
5 issues opened.
-
NEL suborigin policies should not be able to generate reports on success w3c/network-error-logging#141, by @clelland.
-
Consider limiting scope of NEL registration w3c/network-error-logging#140, by @yoavweiss.
-
NEL cache should be time-bound w3c/network-error-logging#139, by @yoavweiss.
-
NEL cache should be partitioned w3c/network-error-logging#138, by @yoavweiss.
-
Data protection and security issues with Network Error Logging w3c/network-error-logging#136, by @polcak.
-
-
2 issues closed.
-
Clarify the include_subdomains directive WRT subdomain depth w3c/network-error-logging#135.
-
Data protection and security issues with Network Error Logging w3c/network-error-logging#136.
-
-
6 issues received 30 new comments.
-
Clarify the include_subdomains directive WRT subdomain depth w3c/network-error-logging#135 (8 comments by @clelland, @neilstuartcraig, @yoavweiss)
-
Proposal: Control delivery of network error types on client side w3c/network-error-logging#133 (6 comments by @neilstuartcraig, @nicjansma, @rfmoz)
-
Consider limiting scope of NEL registration w3c/network-error-logging#140 (4 comments by @clelland, @yoavweiss)
-
Data protection and security issues with Network Error Logging w3c/network-error-logging#136 (4 comments by @polcak, @yoavweiss)
-
Better HTTP/2 and HTTP/3 errors w3c/network-error-logging#134 (4 comments by @LPardue, @neilstuartcraig)
-
-
1 pull request opened.
-
Clarify that include_subdomains covers unlimited subdomain depth w3c/network-error-logging#137, by @neilstuartcraig.
-
-
1 pull request merged.
-
Clarify that include_subdomains covers unlimited subdomain depth w3c/network-error-logging#137.
-
-
1 pull request received 1 new comment.
-
Clarify that include_subdomains covers unlimited subdomain depth w3c/network-error-logging#137 (1 comment by @clelland)
-
w3c/resource-timing
-
1 issue opened.
-
sendBeacon() integration w3c/resource-timing#377, by @annevk.
-
-
1 issue closed.
-
Expose delivery type in PerformanceResourceTiming. w3c/resource-timing#332.
-
-
1 issue reopened.
-
Consider adding finalResponseHeaders{Start|End} times w3c/resource-timing#345, by @noamr.
-
-
2 issues received 4 new comments.
-
Consider adding finalResponseHeaders{Start|End} times w3c/resource-timing#345 (2 comments by @annevk, @noamr)
-
-
2 pull requests merged.
-
Add content-type to resource-timing w3c/resource-timing#341.
-
Add interim response times w3c/resource-timing#366.
-
-
2 pull requests reopened.
-
Add interim response times w3c/resource-timing#366, by @noamr.
-
Add interim response times w3c/resource-timing#366, by @noamr.
-
-
3 pull requests received 20 new comments.
-
Add interim response times w3c/resource-timing#366 (18 comments by @annevk, @johnathan79717, @noamr, @tunetheweb)
-
w3c/resource-timing#379 (1 comment by @w3cbot)
-
w3c/resource-timing#378 (1 comment by @w3cbot)
-
w3c/reporting
-
1 issue opened.
-
1 issue received 3 new comments.
-
Could there be a way to collect Crash/Intervention reports without collecting Deprecation reports? w3c/reporting#263 (3 comments by @clelland, @neilstuartcraig)
-
-
1 pull request opened.
-
Fix a link to a Background Sync issue w3c/reporting#264, by @jyasskin.
-
-
1 pull request merged.
-
Fix a link to a Background Sync issue w3c/reporting#264.
-
w3c/navigation-timing
-
1 pull request received 1 new comment.
w3c/hr-time
-
1 issue received 2 new comments.
w3c/server-timing
-
1 issue reopened.
-
add total to distinguish between calendar time and effort time w3c/server-timing#44, by @yoavweiss.
-
-
2 issues received 2 new comments.
-
Server-Timing is too limited in scope, rename to Server-Metrics w3c/server-timing#77 (1 comment by @josephwynn-sc)
-
add total to distinguish between calendar time and effort time w3c/server-timing#44 (1 comment by @yoavweiss)
-
TR publications
-
4 documents published.
-
User Timing Level 3 published as a Candidate Recommendation Draft. History of User Timing Level 3
-
High Resolution Time published twice as a Working Draft. History of High Resolution Time
-
Server Timing published as a Working Draft. History of Server Timing
-
GitHub
w3c/server-timing
-
1 issue closed.
-
Make it clearer what the units for `duration` are w3c/server-timing#86.
-
-
1 issue received 1 new comment.
-
add total to distinguish between calendar time and effort time w3c/server-timing#44 (1 comment by @noamr)
-
-
1 pull request opened.
-
Editorial: Note about millis w3c/server-timing#93, by @noamr.
-
-
1 pull request merged.
-
Editorial: Note about millis w3c/server-timing#93.
-
-
1 pull request received 3 new comments.
w3c/network-error-logging
-
3 issues opened.
-
Clarify the include_subdomains directive WRT subdomain depth w3c/network-error-logging#135, by @neilstuartcraig.
-
Better HTTP/2 and HTTP/3 errors w3c/network-error-logging#134, by @LPardue.
-
Proposal: Control delivery of network error types on client side w3c/network-error-logging#133, by @rfmoz.
-
-
1 issue closed.
-
HTTP error types w3c/network-error-logging#126.
-
-
3 issues received 10 new comments.
-
Proposal: Control delivery of network error types on client side w3c/network-error-logging#133 (6 comments by @clelland, @neilstuartcraig, @Sora2455)
-
Better HTTP/2 and HTTP/3 errors w3c/network-error-logging#134 (3 comments by @clelland, @LPardue, @yoavweiss)
-
w3c/navigation-timing
-
2 issues opened.
-
Measuring `beforeunload` w3c/navigation-timing#190, by @yoavweiss.
-
Broken references in Navigation Timing Level 2 w3c/navigation-timing#189, by @dontcallmedom-bot.
-
-
3 issues received 5 new comments.
-
NavigationTimingType enum need updates as HTML spec changed w3c/navigation-timing#185 (1 comment by @annevk)
-
Clarify how PerformanceTiming.responseStart relates to Early Hint responses w3c/navigation-timing#181 (1 comment by @noamr)
w3c/reporting
-
1 issue opened.
-
Set reporting endpoint in cross-domain iframe from parent page w3c/reporting#262, by @wiedaw.
-
-
1 issue received 2 new comments.
-
Set reporting endpoint in cross-domain iframe from parent page w3c/reporting#262 (2 comments by @clelland, @wiedaw)
-
w3c/resource-timing
-
1 issue opened.
-
Broken references in Resource Timing w3c/resource-timing#376, by @dontcallmedom-bot.
-
-
3 issues closed.
-
Render blocking status of resources w3c/resource-timing#262.
-
Add response status codes for resources in Resource Timing API. w3c/resource-timing#90.
-
Problematic cases with cross-origin iframes & aborted navigations w3c/resource-timing#340.
-
-
6 issues received 12 new comments.
-
Test infrastructure to expose whether a browser intends to expose transferSize across origins with TAO w3c/resource-timing#371 (6 comments by @sefeng211, @yoavweiss)
-
Adding resource discovery time to ResourceTiming API structure w3c/resource-timing#374 (2 comments by @clelland, @nicjansma)
-
Adding HTTP method to ResourceTiming API structure w3c/resource-timing#373 (1 comment by @nicjansma)
-
Add response status codes for resources in Resource Timing API. w3c/resource-timing#90 (1 comment by @yoavweiss)
-
-
1 pull request opened.
-
Add http method to ResourceTiming interface w3c/resource-timing#375, by @sohomdatta1.
-
-
2 pull requests received 4 new comments.
-
Add http method to ResourceTiming interface w3c/resource-timing#375 (2 comments by @sohomdatta1, @yoavweiss)
w3c/web-performance
-
2 issues opened.
-
Consider deprecating primer w3c/web-performance#54, by @nicjansma.
-
"HR-time" can maybe be renamed to "time" w3c/web-performance#53, by @yoavweiss.
-
-
4 issues received 8 new comments.
-
Consider including userland conventions and protocols w3c/web-performance#52 (2 comments by @bdekoz, @yoavweiss)
-
The charter should discuss open issues around privacy w3c/web-performance#51 (2 comments by @bdekoz)
w3c/user-timing
-
1 issue opened.
-
Broken references in User Timing Level 3 w3c/user-timing#101, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Broken references in User Timing Level 3 w3c/user-timing#101.
-
-
1 pull request opened.
-
Editorial: nits w3c/user-timing#102, by @npm1.
-
-
1 pull request merged.
-
Editorial: nits w3c/user-timing#102.
-
-
2 pull requests received 2 new comments.
w3c/performance-timeline
-
2 issues received 7 new comments.
-
Cross-origin timeline support w3c/performance-timeline#207 (6 comments by @clelland, @nicjansma, @sefeng211, @yoavweiss)
-
Proposal: clock-drift correction, potentially with opt-in w3c/performance-timeline#206 (1 comment by @ayushgupta9906)
-
-
1 pull request received 1 new comment.
w3c/hr-time
-
2 issues opened.
-
Better ids for the two "unsafe current time"s w3c/hr-time#156, by @jyasskin.
-
Expose the "current wall time" w3c/hr-time#155, by @jyasskin.
-
-
3 issues closed.
-
Expose the "current wall time" w3c/hr-time#155.
-
Better ids for the two "unsafe current time"s w3c/hr-time#156.
-
-
2 issues received 7 new comments.
-
Expose the "current wall time" w3c/hr-time#155 (6 comments by @clelland, @jyasskin, @noamr, @yoavweiss)
-
-
3 pull requests opened.
-
Editorial: performance.now(): Use relevant global object w3c/hr-time#159, by @noamr.
-
Editorial: Add ids to unsafe-current-time dfns w3c/hr-time#157, by @noamr.
-
3 pull requests merged.
-
Editorial: performance.now(): Use relevant global object w3c/hr-time#159.
-
Editorial: Add ids to unsafe-current-time dfns w3c/hr-time#157.
-
3 pull requests received 3 new comments.
-
w3c/hr-time#162 (1 comment by @w3cbot)
-
w3c/hr-time#160 (1 comment by @w3cbot)
-
w3c/hr-time#158 (1 comment by @w3cbot)
-
w3c/event-timing
-
2 issues received 2 new comments.
-
Proposal: DOM event identifier which can map to EventTimingPerformance entry w3c/event-timing#108 (1 comment by @mmocny)
-
1 pull request opened.
-
InteractionID & Count Explainer w3c/event-timing#133, by @zuoaoyuan.
-
-
1 pull request received 6 new comments.
w3c/largest-contentful-paint
-
1 issue opened.
-
The factors than make an element Contentful or not-Contentful should be defined w3c/largest-contentful-paint#112, by @andydavies.
-
-
1 issue received 1 new comment.
-
The factors than make an element Contentful or not-Contentful should be defined w3c/largest-contentful-paint#112 (1 comment by @clelland)
-
w3c/element-timing
-
1 issue received 1 new comment.
w3c/longtasks
-
1 issue opened.
-
Broken references in Long Tasks API w3c/longtasks#108, by @dontcallmedom-bot.
-
-
2 pull requests opened.
-
Update loaf-explainer.md: explain blockingTime w3c/longtasks#107, by @noamr.
-
Update loaf-explainer.md w3c/longtasks#106, by @noamr.
-
-
3 pull requests merged.
-
Update loaf-explainer.md: explain blockingTime w3c/longtasks#107.
-
Update w3c.json w3c/longtasks#105.
-
Update loaf-explainer.md w3c/longtasks#106.
-
-
1 pull request received 2 new comments.
TR publications
-
7 documents published.
-
Resource Timing published twice as a Candidate Recommendation Draft. History of Resource Timing
-
High Resolution Time published twice as a Working Draft. History of High Resolution Time
-
Server Timing published twice as a Working Draft. History of Server Timing
-
Resource Hints published as a Discontinued Draft. History of Resource Hints
-
Participants
-
2 participants joined.
-
ChangSeok Oh (ByteDance) joined.
-
Jeb Barabanov (Wix.com Ltd.) joined.
-
-
1 organization joined.
-
ByteDance joined.
-
GitHub
w3c/resource-timing
-
3 issues opened.
-
Adding resource discovery time to ResourceTiming API structure w3c/resource-timing#374, by @giacomozecchini.
-
Adding HTTP method to ResourceTiming API structure w3c/resource-timing#373, by @sohomdatta1.
-
Test infrastructure to expose whether a browser intends to expose transferSize across origins with TAO w3c/resource-timing#371, by @achristensen07.
-
-
1 issue closed.
-
2 issues received 7 new comments.
-
Test infrastructure to expose whether a browser intends to expose transferSize across origins with TAO w3c/resource-timing#371 (4 comments by @nicjansma, @sefeng211, @yoavweiss)
-
Adding HTTP method to ResourceTiming API structure w3c/resource-timing#373 (3 comments by @clelland, @nicjansma, @yoavweiss)
-
-
2 pull requests merged.
-
Add delivery type to PerformanceResourceTiming. w3c/resource-timing#343.
-
Allow user agents to enforce cross-origin restrictions w3c/resource-timing#369.
-
-
3 pull requests received 4 new comments.
-
Add delivery type to PerformanceResourceTiming. w3c/resource-timing#343 (2 comments by @jeremyroman, @noamr)
-
w3c/resource-timing#372 (1 comment by @w3cbot)
-
w3c/resource-timing#370 (1 comment by @w3cbot)
-
w3c/longtasks
-
1 issue received 3 new comments.
-
2 pull requests opened.
-
Update w3c.json w3c/longtasks#105, by @caribouW3.
-
Fix spelling errors in loaf-explainer.md w3c/longtasks#104, by @progers.
-
-
2 pull requests merged.
-
Long Animation Frame (LoAF) explainer w3c/longtasks#100.
-
Fix spelling errors in loaf-explainer.md w3c/longtasks#104.
-
-
2 pull requests received 6 new comments.
w3c/navigation-timing
-
2 issues received 9 new comments.
-
NavigationTimingType enum need updates as HTML spec changed w3c/navigation-timing#185 (5 comments by @domenic, @jeremyroman, @tunetheweb, @yoavweiss)
-
Report that Critical-CH was used to restart a navigation w3c/navigation-timing#177 (4 comments by @arichiv, @miketaylr, @nicjansma, @yoavweiss)
-
-
1 pull request opened.
-
Add criticalCHRestart w3c/navigation-timing#188, by @arichiv.
-
-
1 pull request received 10 new comments.
w3c/largest-contentful-paint
-
1 issue closed.
-
How to handle ties? w3c/largest-contentful-paint#69.
-
-
2 issues received 2 new comments.
-
Need a new DOM concept for user-driven events rather than using `isTrusted` w3c/largest-contentful-paint#105 (1 comment by @noamr)
-
w3c/event-timing
-
3 issues received 6 new comments.
-
Consider expose interactionId to keypress, input, and more other event types w3c/event-timing#132 (4 comments by @Biki-das, @daksh-goyal, @zuoaoyuan)
-
Should Section 2.2 reference 'considered for Event Timing' w3c/event-timing#56 (1 comment by @clelland)
-
w3c/web-performance
-
2 issues opened.
-
Consider including userland conventions and protocols w3c/web-performance#52, by @yoavweiss.
-
The charter should discuss open issues around privacy w3c/web-performance#51, by @yoavweiss.
-
w3c/hr-time
-
1 issue opened.
-
now() method doesn't pass required argument to current high resolution time w3c/hr-time#152, by @annevk.
-
-
2 issues received 3 new comments.
-
now() method doesn't pass required argument to current high resolution time w3c/hr-time#152 (1 comment by @yoavweiss)
-
1 pull request opened.
-
editorial: Remove the definition of "epoch-relative timestamp". w3c/hr-time#153, by @jyasskin.
-
-
1 pull request merged.
-
editorial: Remove the definition of "epoch-relative timestamp". w3c/hr-time#153.
-
-
2 pull requests received 6 new comments.
-
editorial: Remove the definition of "epoch-relative timestamp". w3c/hr-time#153 (5 comments by @jyasskin, @noamr)
-
w3c/hr-time#154 (1 comment by @w3cbot)
-
w3c/server-timing
-
2 issues closed.
-
Broken references in Server Timing w3c/server-timing#91.
-
-
1 pull request opened.
-
Fix broken references to INFRA#map. w3c/server-timing#92, by @clelland.
-
-
2 pull requests merged.
-
Fix broken references to INFRA#map. w3c/server-timing#92.
-
Allow user agents to keep same-origin restrictions on PerformanceServ… w3c/server-timing#90.
-
w3c/reporting
-
1 issue received 2 new comments.
-
Allow for custom reports to be generated & queued w3c/reporting#259 (2 comments by @scottpledger, @yoavweiss)
-
w3c/performance-timeline
-
1 issue opened.
-
Gsoc 2023 Proposal clock-drift correction w3c/performance-timeline#208, by @Forchapeatl.
-
-
1 issue closed.
-
Gsoc 2023 Proposal clock-drift correction w3c/performance-timeline#208.
-
-
2 issues received 18 new comments.
-
Proposal: clock-drift correction, potentially with opt-in w3c/performance-timeline#206 (16 comments by @Forchapeatl, @GarretTomlin, @jyasskin, @Nandini99-git, @noamr, @Yougesh978)
-
Gsoc 2023 Proposal clock-drift correction w3c/performance-timeline#208 (2 comments by @Forchapeatl, @noamr)
-
Lifecycle
-
1 charter extension.
-
Charter extended until 31 August 2023.
-
TR publications
-
3 documents published.
-
High Resolution Time published twice as a Working Draft. History of High Resolution Time
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
GitHub
w3c/performance-timeline
-
2 issues opened.
-
Cross-origin timeline support w3c/performance-timeline#207, by @clelland.
-
Proposal: clock-drift correction, potentially with opt-in w3c/performance-timeline#206, by @noamr.
-
-
4 issues received 13 new comments.
-
Proposal: clock-drift correction, potentially with opt-in w3c/performance-timeline#206 (8 comments by @Forchapeatl, @i-m-abbhay, @jyasskin, @noamr, @yoavweiss)
-
Fire Paint Timing events for soft navigations w3c/performance-timeline#168 (2 comments by @dwsmart, @yoavweiss)
-
-
2 pull requests received 2 new comments.
w3c/event-timing
-
2 issues opened.
-
Consider expose interactionId to keypress, input, and more other event types w3c/event-timing#132, by @zuoaoyuan.
-
Integrate PaintTimingMixin into Event Timing. w3c/event-timing#131, by @mmocny.
-
-
3 issues closed.
-
Alternate semantics for processingStart w3c/event-timing#55.
-
It is surprising that 'wheel' event is exluded from the event timing w3c/event-timing#89.
-
-
9 issues received 33 new comments.
-
Consider expose interactionId to keypress, input, and more other event types w3c/event-timing#132 (15 comments by @Biki-das, @zuoaoyuan)
-
How does Event Timing API relate to/overlap with Long Tasks API? w3c/event-timing#122 (9 comments by @clelland, @mmocny, @noamr)
-
Proposal: add more main thread activity information to PerformanceEventTiming entry w3c/event-timing#109 (2 comments by @mmocny, @noamr)
-
Add `targetSelector` attribute to Event Timing API (for cases where target is detached) w3c/event-timing#126 (2 comments by @Ludovic33Fr, @mmocny)
-
Audit the list of events which Event Timing api should report (and consider adding focus/blur) w3c/event-timing#130 (1 comment by @clelland)
-
It is surprising that 'wheel' event is exluded from the event timing w3c/event-timing#89 (1 comment by @clelland)
-
Add element and/or id fields to PerformanceEventTiming to indicate target of the event w3c/event-timing#60 (1 comment by @clelland)
-
w3c/resource-timing
-
2 issues received 2 new comments.
-
Cross-origin IFRAME opting-in to sharing ResourceTiming data w3c/resource-timing#210 (1 comment by @clelland)
-
Consider adding finalResponseHeaders{Start|End} times w3c/resource-timing#345 (1 comment by @LPardue)
-
-
1 pull request received 1 new comment.
w3c/navigation-timing
-
1 issue closed.
-
Broken references in Navigation Timing Level 2 w3c/navigation-timing#186.
-
-
1 issue received 1 new comment.
-
Clarify how PerformanceTiming.responseStart relates to Early Hint responses w3c/navigation-timing#181 (1 comment by @adardesign)
-
-
1 pull request opened.
-
Fix some broken refs after navigation refactor w3c/navigation-timing#187, by @noamr.
-
-
1 pull request merged.
-
Fix some broken refs after navigation refactor w3c/navigation-timing#187.
-
w3c/web-performance
-
7 issues opened.
-
Remove Preload from charter? w3c/web-performance#50, by @clelland.
-
Remove Page Visibility from charter? w3c/web-performance#49, by @clelland.
-
Add Event Timing to charter w3c/web-performance#48, by @clelland.
-
Add LCP to charter w3c/web-performance#47, by @clelland.
-
"Performance APIs, security and privacy" document w3c/web-performance#46, by @yoavweiss.
-
Privacy Preserving Monitoring w3c/web-performance#45, by @yoavweiss.
-
Consider unifying specifications w3c/web-performance#44, by @yoavweiss.
-
-
3 issues closed.
-
Multi-spec non-feature TODOs for web performance WG w3c/web-performance#38.
-
Clarify gdoc in meetings w3c/web-performance#33.
-
Missing TPAC 2019 w3c/web-performance#32.
-
-
1 issue received 2 new comments.
-
Multi-spec non-feature TODOs for web performance WG w3c/web-performance#38 (2 comments by @noamr, @yoavweiss)
-
-
2 pull requests opened.
-
Clarify the role of the agenda doc w3c/web-performance#43, by @yoavweiss.
-
Fix TPAC 2019 link w3c/web-performance#42, by @yoavweiss.
-
-
2 pull requests merged.
-
Clarify the role of the agenda doc w3c/web-performance#43.
-
Fix TPAC 2019 link w3c/web-performance#42.
-
w3c/beacon
-
1 issue received 1 new comment.
w3c/longtasks
-
2 issues opened.
-
New proposal: long animation frames w3c/longtasks#103, by @noamr.
-
Some references are broken after navigation refactor w3c/longtasks#101, by @noamr.
-
-
3 issues closed.
-
Some references are broken after navigation refactor w3c/longtasks#101.
-
Event loop timing reporting seems to ignore reentrancy w3c/longtasks#76.
-
Can we find which script or function is taking longer than 50 ms? w3c/longtasks#28.
-
-
3 issues received 5 new comments.
-
Can we find which script or function is taking longer than 50 ms? w3c/longtasks#28 (1 comment by @noamr)
-
2 pull requests opened.
-
Fix broken refs w3c/longtasks#102, by @noamr.
-
Long Animation Frame (LoAF) explainer w3c/longtasks#100, by @noamr.
-
-
1 pull request merged.
-
Fix broken refs w3c/longtasks#102.
-
-
1 pull request reopened.
-
Long Animation Frame (LoAF) explainer w3c/longtasks#100, by @noamr.
-
-
1 pull request received 18 new comments.
w3c/hr-time
-
1 issue opened.
-
Why is EpochTimeStamp discouraged? w3c/hr-time#149, by @domenic.
-
-
1 issue reopened.
-
Why is EpochTimeStamp discouraged? w3c/hr-time#149, by @noamr.
-
-
1 issue received 8 new comments.
-
Why is EpochTimeStamp discouraged? w3c/hr-time#149 (8 comments by @annevk, @domenic, @inexorabletash, @noamr)
-
-
2 pull requests opened.
-
Editorial: Add note about DOMHighResTimestamp precision w3c/hr-time#150, by @noamr.
-
editorial: Try to explain moments better. w3c/hr-time#147, by @jyasskin.
-
-
2 pull requests merged.
-
Editorial: Add note about DOMHighResTimestamp precision w3c/hr-time#150.
-
editorial: Try to explain moments better. w3c/hr-time#147.
-
-
3 pull requests received 5 new comments.
-
editorial: Try to explain moments better. w3c/hr-time#147 (3 comments by @jyasskin, @xyaoinum, @yoavweiss)
-
w3c/hr-time#151 (1 comment by @w3cbot)
-
w3c/hr-time#148 (1 comment by @w3cbot)
-
w3c/reporting
-
1 issue received 1 new comment.
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 @pablomercadolibre)
-
TR publications
-
2 documents published.
-
High Resolution Time published twice as a Working Draft. History of High Resolution Time
-
Participants
-
4 participants joined.
-
Abhishek Ghosh (Amazon) joined.
-
Mahesh Bharadava (Skynet Technologies) joined.
-
Sunil Jolapara (Skynet Technologies) joined.
-
Noam Rosenthal (Google LLC) joined.
-
-
2 participants left.
-
John Engebretson (Amazon) left.
-
Noam Rosenthal (Google LLC) left.
-
-
1 organization joined.
-
Skynet Technologies joined.
-
GitHub
w3c/resource-timing
-
2 issues opened.
-
Capturing basic auth credentials in URLs, part 2 w3c/resource-timing#368, by @nicjansma.
-
Should the spec mention "Queue entry" at somepoint? w3c/resource-timing#367, by @sefeng211.
-
-
1 issue closed.
-
Should the spec mention "Queue entry" at somepoint? w3c/resource-timing#367.
-
-
5 issues received 8 new comments.
-
Should the spec mention "Queue entry" at somepoint? w3c/resource-timing#367 (3 comments by @noamr, @sefeng211, @yoavweiss)
-
Problematic cases with cross-origin iframes & aborted navigations w3c/resource-timing#340 (2 comments by @bdekoz, @yoavweiss)
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (1 comment by @ZengTianShengZ)
-
User Agent may want to restrict cross-origin transferSize/encodedBodySize/decodedBodySize visibility even with TAO w3c/resource-timing#342 (1 comment by @achristensen07)
-
Why is there noticeable gap between requestStart and connectEnd? w3c/resource-timing#365 (1 comment by @noamr)
-
-
1 pull request opened.
-
Allow user agents to enforce cross-origin restrictions w3c/resource-timing#369, by @achristensen07.
-
-
2 pull requests received 3 new comments.
-
Allow user agents to enforce cross-origin restrictions w3c/resource-timing#369 (2 comments by @achristensen07, @yoavweiss)
-
w3c/reporting
-
3 issues opened.
-
Broken references in Reporting API w3c/reporting#261, by @dontcallmedom-bot.
-
Clarification on Retry mechanisms w3c/reporting#260, by @nicjansma.
-
Allow for custom reports to be generated & queued w3c/reporting#259, by @scottpledger.
-
-
3 issues received 5 new comments.
-
Allow for custom reports to be generated & queued w3c/reporting#259 (2 comments by @scottpledger, @yoavweiss)
w3c/server-timing
-
1 issue opened.
-
Broken references in Server Timing w3c/server-timing#91, by @dontcallmedom-bot.
-
-
2 issues received 3 new comments.
-
add start time to distinguish between cached and active entries w3c/server-timing#43 (2 comments by @hauleth, @murraylchapman)
-
-
1 pull request opened.
-
Allow user agents to keep same-origin restrictions on PerformanceServ… w3c/server-timing#90, by @achristensen07.
-
-
1 pull request received 2 new comments.
-
Allow user agents to keep same-origin restrictions on PerformanceServ… w3c/server-timing#90 (2 comments by @achristensen07, @yoavweiss)
-
w3c/paint-timing
-
1 pull request closed.
-
Remove rendering pipeline note w3c/paint-timing#94.
-
w3c/largest-contentful-paint
-
2 issues received 10 new comments.
-
renderTime should be CORS-protected, not TAO-protected w3c/largest-contentful-paint#111 (9 comments by @annevk, @mmocny, @noamr, @smfr, @yoavweiss)
-
w3c/event-timing
-
1 issue opened.
-
Audit the list of events which Event Timing api should report (and consider adding focus/blur) w3c/event-timing#130, by @mmocny.
-
-
1 issue received 1 new comment.
-
Audit the list of events which Event Timing api should report (and consider adding focus/blur) w3c/event-timing#130 (1 comment by @mmocny)
-
-
1 pull request closed.
-
Enable threshold customization w3c/event-timing#5.
-
w3c/element-timing
-
1 issue opened.
-
Clarify Element Timing's handling of pseudo-elements w3c/element-timing#74, by @brendankenny.
-
w3c/longtasks
-
1 issue closed.
-
Better understand correlating long tasks from different iframes w3c/longtasks#18.
-
-
5 issues received 5 new comments.
-
Combination of paint timing and long tasks can expose precise paint timing w3c/longtasks#80 (1 comment by @noamr)
-
Should LongTasks from same-origin same-event-loop tabs be reported? w3c/longtasks#88 (1 comment by @noamr)
-
Better understand correlating long tasks from different iframes w3c/longtasks#18 (1 comment by @noamr)
-
w3c/hr-time
-
1 issue closed.
-
Spec text isn't clear about time origins and monotonic clocks w3c/hr-time#139.
-
-
2 pull requests opened.
-
Durations actually need to have both endpoints coarsened. w3c/hr-time#144, by @jyasskin.
-
editorial: Use Respec's variable typing, and use the duration-from algorithm. w3c/hr-time#143, by @jyasskin.
-
-
3 pull requests merged.
-
Durations actually need to have both endpoints coarsened. w3c/hr-time#144.
-
editorial: Introduce clocks, moments, and durations w3c/hr-time#140.
-
4 pull requests received 44 new comments.
-
editorial: Introduce clocks, moments, and durations w3c/hr-time#140 (41 comments by @csharrison, @jyasskin, @noamr, @yoavweiss)
-
w3c/hr-time#146 (1 comment by @w3cbot)
-
w3c/hr-time#145 (1 comment by @w3cbot)
-
w3c/hr-time#142 (1 comment by @w3cbot)
-
w3c/performance-timeline
-
1 pull request received 2 new comments.
-
Add support for accessing cross-frame entries. w3c/performance-timeline#202 (2 comments by @clelland, @noamr)
-
w3c/navigation-timing
-
1 issue opened.
-
Broken references in Navigation Timing Level 2 w3c/navigation-timing#186, by @dontcallmedom-bot.
-
-
2 issues closed.
-
Possibility to get the HTTP status code from the Response Header ? w3c/navigation-timing#126.
-
-
2 issues received 2 new comments.
-
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)
w3c/network-error-logging
-
1 issue opened.
-
Broken references in Network Error Logging w3c/network-error-logging#132, by @dontcallmedom-bot.
-
-
1 issue received 1 new comment.