Web Performance Working Group - Activity in 2021
No matches.
TR publications
-
3 documents published.
-
Performance Timeline published as a Candidate Recommendation Snapshot. History of Performance Timeline
-
User Timing published as a Candidate Recommendation Snapshot. History of User Timing
-
High Resolution Time published as a Working Draft. History of High Resolution Time
-
GitHub
w3c/largest-contentful-paint
-
1 issue closed.
-
Better handle auto-playing video content w3c/largest-contentful-paint#88.
-
-
3 issues received 3 new comments.
-
Very large transparent SVG should not count as LCP w3c/largest-contentful-paint#72 (1 comment by @yoavweiss)
w3c/performance-timeline
-
1 issue received 2 new comments.
-
Fire Paint Timing events for soft navigations w3c/performance-timeline#168 (2 comments by @dwsmart, @yoavweiss)
-
w3c/user-timing
-
2 issues opened.
-
Undocumented exception in performance.measure() w3c/user-timing#87, by @hamishwillee.
-
Contextual and GC friendly user timing w3c/user-timing#86, by @legendecas.
-
-
1 issue closed.
-
Undocumented exception in performance.measure() w3c/user-timing#87.
-
-
2 issues received 4 new comments.
-
Undocumented exception in performance.measure() w3c/user-timing#87 (2 comments by @hamishwillee, @npm1)
w3c/resource-timing
-
2 issues received 3 new comments.
-
Consider to limit the max size of resource timing buffer w3c/resource-timing#304 (2 comments by @npm1, @smaug----)
-
-
1 pull request opened.
-
Minor clarity improvement in Privacy & Security section w3c/resource-timing#307, by @patrickhulce.
-
-
1 pull request received 1 new comment.
-
Minor clarity improvement in Privacy & Security section w3c/resource-timing#307 (1 comment by @npm1)
-
w3c/longtasks
-
1 issue received 2 new comments.
-
Generic model for causal attribution (non-sampling based) w3c/longtasks#89 (2 comments by @npm1, @yoavweiss)
-
w3c/event-timing
-
1 issue closed.
-
Expose the number of interactions to the webpage w3c/event-timing#111.
-
-
2 issues received 3 new comments.
-
Proposal: add page visibility attribute to PerformanceEventTiming entry w3c/event-timing#110 (2 comments by @nhelfman, @npm1)
-
interactionID should be harmonized with activation triggering input events w3c/event-timing#105 (1 comment by @npm1)
-
-
1 pull request opened.
-
Add interactionCounts w3c/event-timing#113, by @npm1.
-
-
1 pull request merged.
-
Add interactionCounts w3c/event-timing#113.
-
-
1 pull request received 3 new comments.
w3c/navigation-timing
-
1 issue received 12 new comments.
-
workerStart should be clearly defined as applicable to the last SW w3c/navigation-timing#100 (12 comments by @noamr, @yoavweiss)
-
w3c/beacon
-
1 issue opened.
-
Account for fetch algorithm rename w3c/beacon#73, by @noamr.
-
-
1 issue closed.
-
Account for fetch algorithm rename w3c/beacon#73.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Editorial: align with fetch algorithm rename w3c/beacon#74, by @noamr.
-
-
1 pull request merged.
-
Editorial: align with fetch algorithm rename w3c/beacon#74.
-
w3c/element-timing
-
1 issue opened.
-
Rather than add tagging attributes to elements, allow to "get timings for all elements" via flag. w3c/element-timing#68, by @DerGernTod.
-
-
1 issue received 3 new comments.
-
Rather than add tagging attributes to elements, allow to "get timings for all elements" via flag. w3c/element-timing#68 (3 comments by @npm1, @yoavweiss)
-
w3c/server-timing
-
1 issue closed.
-
Server-Timing header field isn't registered w3c/server-timing#83.
-
-
1 issue received 1 new comment.
w3c/reporting
-
1 issue opened.
-
Sending Reporting API reports cross-origin (Report-To) header w3c/reporting#249, by @abhijoshi2k.
-
-
1 issue closed.
-
Sending Reporting API reports cross-origin (Report-To) header w3c/reporting#249.
-
-
1 issue received 1 new comment.
-
Sending Reporting API reports cross-origin (Report-To) header w3c/reporting#249 (1 comment by @clelland)
-
w3c/requestidlecallback
-
1 pull request opened.
-
Editorial: Use the HTML spec's timers infrastructure for `timeout` w3c/requestidlecallback#98, by @andreubotella.
-
-
1 pull request received 5 new comments.
-
Editorial: Use the HTML spec's timers infrastructure for `timeout` w3c/requestidlecallback#98 (5 comments by @andreubotella, @w3cbot, @yoavweiss)
-
w3c/hr-time
-
1 issue closed.
-
Define `timeOrigin` in the HTML spec w3c/hr-time#131.
-
-
1 pull request merged.
-
Remove own version of `timeOrigin` definition w3c/hr-time#132.
-
-
1 pull request received 1 new comment.
-
w3c/hr-time#133 (1 comment by @w3cbot)
-
TR publications
-
1 document published.
-
Performance Timeline Level 2 published as a Working Draft. History of Performance Timeline Level 2
-
Participants
-
1 participant joined.
-
Leon Brocard (Fastly) joined.
-
-
4 participants left.
-
Beng Eu (Google LLC) left.
-
Michael Blain (Google LLC) left.
-
Gilles Dubuc (Wikimedia Foundation) left.
-
Benoit Girard (Meta) left.
-
GitHub
w3c/resource-timing
-
3 issues closed.
-
4.6 Integrate the processing model with Fetch w3c/resource-timing#252.
-
Timing-Allow-Origin may expose allowed URLs w3c/resource-timing#228.
-
Be a bit more explicit about which subresources are to be ignored from stylesheets w3c/resource-timing#200.
-
-
6 issues received 11 new comments.
-
Reflect preload information (in ResourceTiming?) w3c/resource-timing#303 (4 comments by @noamr, @npm1, @yoavweiss)
-
Should favicon loading times be exposed to the document? w3c/resource-timing#299 (2 comments by @noamr, @yoavweiss)
-
4.6 Integrate the processing model with Fetch w3c/resource-timing#252 (2 comments by @noamr, @yoavweiss)
-
Be a bit more explicit about which subresources are to be ignored from stylesheets w3c/resource-timing#200 (1 comment by @noamr)
-
-
1 pull request opened.
-
Small formatting tweaks w3c/resource-timing#305, by @tommckee1.
-
-
1 pull request merged.
-
Small formatting tweaks w3c/resource-timing#305.
-
-
1 pull request received 1 new comment.
-
w3c/resource-timing#306 (1 comment by @w3cbot)
-
w3c/hr-time
-
1 issue opened.
-
Define `timeOrigin` in the HTML spec w3c/hr-time#131, by @noamr.
-
-
1 issue received 5 new comments.
-
1 pull request opened.
-
Remove own version of `timeOrigin` definition w3c/hr-time#132, by @noamr.
-
-
2 pull requests received 14 new comments.
w3c/event-timing
-
3 issues opened.
-
CfC: Adopt Event Timing into the WebPerfWG as a Working Draft w3c/event-timing#112, by @yoavweiss.
-
Expose the number of interactions to the webpage w3c/event-timing#111, by @npm1.
-
Proposal: add page visibility attribute to PerformanceEventTiming entry w3c/event-timing#110, by @nhelfman.
-
-
1 issue closed.
-
CFC: adopt to WebPerfWG as a Working Draft w3c/event-timing#94.
-
-
2 issues received 3 new comments.
-
Proposal: add more main thread activity information to PerformanceEventTiming entry w3c/event-timing#109 (2 comments by @nhelfman, @yoavweiss)
-
w3c/navigation-timing
-
2 issues opened.
-
Reporting timestamps rely on a global object which might not exist yet w3c/navigation-timing#166, by @noamr.
-
Using "connectStart", "secureConnectionStart" and "connectEnd" with HTTP/3 flows w3c/navigation-timing#165, by @ThierryMajutec.
-
-
3 issues closed.
-
Reporting timestamps rely on a global object which might not exist yet w3c/navigation-timing#166.
-
4.1 Processing model should rely on Fetch/HTML w3c/navigation-timing#136.
-
Add a test that ensures `fetchStart` matches the SW's fetch event start time w3c/navigation-timing#148.
-
-
4 issues received 10 new comments.
-
Using "connectStart", "secureConnectionStart" and "connectEnd" with HTTP/3 flows w3c/navigation-timing#165 (4 comments by @noamr, @yoavweiss)
-
Using navigationStart as a baseline may expose cross-origin timing information w3c/navigation-timing#160 (4 comments by @andydavies, @noamr, @yoavweiss)
-
Reporting timestamps rely on a global object which might not exist yet w3c/navigation-timing#166 (1 comment by @noamr)
-
Add a test that ensures `fetchStart` matches the SW's fetch event start time w3c/navigation-timing#148 (1 comment by @noamr)
-
w3c/largest-contentful-paint
-
5 issues opened.
-
Better handle auto-playing video content w3c/largest-contentful-paint#88, by @yoavweiss.
-
CfC: Adopt LCP into the WebPerfWG as a Working Draft w3c/largest-contentful-paint#87, by @yoavweiss.
-
Improve unimportant image heuristic w3c/largest-contentful-paint#86, by @npm1.
-
Include autoplay videos w3c/largest-contentful-paint#85, by @npm1.
-
Consider including SVG elements w3c/largest-contentful-paint#84, by @npm1.
-
-
1 issue closed.
-
CFC: adopt to WebPerfWG as a Working Draft w3c/largest-contentful-paint#57.
-
-
4 issues received 7 new comments.
-
CFC: adopt to WebPerfWG as a Working Draft w3c/largest-contentful-paint#57 (1 comment by @yoavweiss)
w3c/performance-timeline
-
1 issue opened.
-
Auto-publishing not working w3c/performance-timeline#194, by @yoavweiss.
-
-
1 issue closed.
-
Auto-publishing not working w3c/performance-timeline#194.
-
-
1 issue received 8 new comments.
-
1 pull request opened.
-
Update auto-publish.yml w3c/performance-timeline#195, by @marcoscaceres.
-
-
1 pull request merged.
-
Update auto-publish.yml w3c/performance-timeline#195.
-
-
1 pull request closed.
-
Update shortname w3c/performance-timeline#191.
-
-
3 pull requests received 6 new comments.
-
Add navigationId to PerformanceEntry w3c/performance-timeline#192 (3 comments by @clelland, @marcoscaceres, @noamr)
-
w3c/beacon
-
1 issue opened.
-
Option to request beacon be compressed w3c/beacon#72, by @nicjansma.
-
-
1 issue received 2 new comments.
w3c/requestidlecallback
-
1 issue closed.
-
"deadline" in the "start an idle period algorithm" should be defined in terms of event loop w3c/requestidlecallback#71.
-
-
2 issues received 4 new comments.
-
6.2. invoke idle callbacks algorithm step 1 should be defined in terms of task sources having tasks enqueued w3c/requestidlecallback#86 (2 comments by @noamr, @yoavweiss)
-
timeRemaining() step 4 should define what it means to have a "time-critical task pending" w3c/requestidlecallback#87 (2 comments by @noamr, @yoavweiss)
-
-
1 pull request merged.
-
Rely on HTML spec for deadline computation w3c/requestidlecallback#95.
-
-
1 pull request received 7 new comments.
-
Rely on HTML spec for deadline computation w3c/requestidlecallback#95 (7 comments by @marcoscaceres, @noamr)
-
w3c/reporting
-
3 issues opened.
-
The document in TR space hasn't been updated since 2018. w3c/reporting#248, by @mikewest.
-
HPKP is deprecated and unshipped – should not be used as example w3c/reporting#247, by @johnwilander.
-
Report requests: use Sec-CH-UA? w3c/reporting#246, by @maudnals.
-
-
2 issues received 7 new comments.
-
The document in TR space hasn't been updated since 2018. w3c/reporting#248 (5 comments by @clelland, @mikewest, @samuelweiler, @sideshowbarker)
-
w3c/element-timing
-
1 issue opened.
-
Automatically use other references by exporting them as needed w3c/element-timing#67, by @npm1.
-
-
3 issues closed.
-
url getter should use URL serializer w3c/element-timing#63.
-
url getter does not handle request being null w3c/element-timing#62.
-
PerformanceObserver api return result not what i need w3c/element-timing#60.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Use URL serializer w3c/element-timing#66, by @npm1.
-
-
1 pull request merged.
-
Use URL serializer w3c/element-timing#66.
-
-
1 pull request received 7 new comments.
w3c/web-performance
-
1 issue opened.
-
API to detect bad performance/dropped frames/jank w3c/web-performance#39, by @emattias.
-
-
1 issue received 2 new comments.
-
API to detect bad performance/dropped frames/jank w3c/web-performance#39 (2 comments by @mmocny, @nhelfman)
-
TR publications
-
4 documents published.
-
High Resolution Time published 4 times as a Working Draft. History of High Resolution Time
-
Participants
-
6 participants joined.
-
Paul Calvano (Akamai Technologies) joined.
-
. Ms2ger (Igalia) joined.
-
Vaspol Ruamviboonsuk (Akamai Technologies) joined.
-
mancang sun (Alibaba Group) joined.
-
Dan Shappir (W3C Invited Experts) joined.
-
Wooseok Jeong (Meta) joined.
-
-
1 organization joined.
-
Igalia joined.
-
GitHub
w3c/event-timing
-
2 issues opened.
-
Proposal: add more main thread activity information to PerformanceEventTiming entry w3c/event-timing#109, by @nhelfman.
-
Proposal: DOM event identifier which can map to EventTimingPerformance entry w3c/event-timing#108, by @nhelfman.
-
-
1 issue closed.
-
An event is not its type w3c/event-timing#104.
-
-
2 pull requests opened.
-
Fix interactionID on IME w3c/event-timing#107, by @npm1.
-
Be explicit about event type w3c/event-timing#106, by @npm1.
-
-
2 pull requests merged.
-
Fix interactionID on IME w3c/event-timing#107.
-
Be explicit about event type w3c/event-timing#106.
-
-
2 pull requests received 16 new comments.
w3c/resource-timing
-
4 issues opened.
-
Consider to limit the max size of resource timing buffer w3c/resource-timing#304, by @smaug----.
-
Reflect preload information (in ResourceTiming?) w3c/resource-timing#303, by @noamr.
-
Should favicon loading times be exposed to the document? w3c/resource-timing#299, by @noamr.
-
initiatorType for favicon w3c/resource-timing#298, by @noamr.
-
-
3 issues closed.
-
4.5 intro includes normative language but is not properly defined w3c/resource-timing#250.
-
Clarify when entry is added to performance entry buffer w3c/resource-timing#82.
-
4.5.1 "timing allow check" should be called from somewhere and get "the resource" as input w3c/resource-timing#251.
-
-
1 issue reopened.
-
Should favicon loading times be exposed to the document? w3c/resource-timing#299, by @noamr.
-
-
9 issues received 24 new comments.
-
Reflect preload information (in ResourceTiming?) w3c/resource-timing#303 (6 comments by @andydavies, @noamr, @yoavweiss)
-
initiatorType for favicon w3c/resource-timing#298 (5 comments by @achristensen07, @noamr, @npm1, @yoavweiss)
-
Clarify when entry is added to performance entry buffer w3c/resource-timing#82 (3 comments by @noamr, @yoavweiss)
-
Consider to limit the max size of resource timing buffer w3c/resource-timing#304 (2 comments by @npm1, @yoavweiss)
-
Should favicon loading times be exposed to the document? w3c/resource-timing#299 (2 comments by @noamr, @yoavweiss)
-
4.5 intro includes normative language but is not properly defined w3c/resource-timing#250 (2 comments by @noamr, @yoavweiss)
-
Be a bit more explicit about which subresources are to be ignored from stylesheets w3c/resource-timing#200 (2 comments by @noamr)
-
4.5.1 "timing allow check" should be called from somewhere and get "the resource" as input w3c/resource-timing#251 (1 comment by @yoavweiss)
-
-
2 pull requests opened.
-
Expose everywhere w3c/resource-timing#302, by @Ms2ger.
-
Be more specific about initiator types w3c/resource-timing#300, by @noamr.
-
-
1 pull request merged.
-
Be more specific about initiator types w3c/resource-timing#300.
-
-
1 pull request received 1 new comment.
-
w3c/resource-timing#301 (1 comment by @w3cbot)
-
w3c/performance-timeline
-
2 issues received 3 new comments.
-
API shape for monitoring new navigation-like entries such as App History, BFCache, etc w3c/performance-timeline#182 (1 comment by @clelland)
-
1 pull request opened.
-
Expose everywhere w3c/performance-timeline#193, by @Ms2ger.
-
-
2 pull requests received 3 new comments.
-
Add navigationId to PerformanceEntry w3c/performance-timeline#192 (2 comments by @clelland, @yoavweiss)
-
w3c/navigation-timing
-
2 issues opened.
-
Processing Model: Should 'prompt for unload' box actually be unload? w3c/navigation-timing#164, by @andydavies.
-
How should prefetch be exposed? w3c/navigation-timing#163, by @jeremyroman.
-
-
2 issues closed.
-
3.1 duration definition should be done in a single place w3c/navigation-timing#133.
-
Please integrate directly with HTML w3c/navigation-timing#63.
-
-
8 issues received 67 new comments.
-
Using navigationStart as a baseline may expose cross-origin timing information w3c/navigation-timing#160 (48 comments by @annevk, @noamr, @npm1, @sgomes, @tdresser, @terjanq, @yoavweiss)
-
The "Obsolete" label is rendered in a seemingly random place w3c/navigation-timing#149 (8 comments by @marcoscaceres, @noamr, @npm1)
-
Should about:blank have a PerformanceNavigationTiming? w3c/navigation-timing#155 (4 comments by @noamr, @yoavweiss)
-
A scenario where transferSize is 0 for non cached loads (or may be not) w3c/navigation-timing#146 (1 comment by @noamr)
-
-
1 pull request opened.
-
Fix typo in markup w3c/navigation-timing#162, by @clelland.
-
-
1 pull request received 4 new comments.
-
Add a landing attribute to PerformanceNavigationTiming w3c/navigation-timing#161 (4 comments by @achristensen07, @domenic, @yoavweiss)
-
w3c/reporting
-
1 issue opened.
-
Editorial: header names and values are byte sequences w3c/reporting#241, by @annevk.
-
-
1 issue closed.
-
Editorial: header names and values are byte sequences w3c/reporting#241.
-
-
1 issue received 2 new comments.
-
Editorial: header names and values are byte sequences w3c/reporting#241 (2 comments by @annevk, @clelland)
-
-
4 pull requests opened.
-
ABNF grammar fix for STRUCTURED-HEADERS w3c/reporting#245, by @freddieleeman.
-
URL fix for Structured Field Values for HTTP w3c/reporting#244, by @freddieleeman.
-
URL to version history fixed w3c/reporting#243, by @freddieleeman.
-
URL to W3C Editor's Draft fixed in README.md w3c/reporting#242, by @freddieleeman.
-
-
4 pull requests merged.
-
URL fix for Structured Field Values for HTTP w3c/reporting#244.
-
ABNF grammar fix for STRUCTURED-HEADERS w3c/reporting#245.
-
URL to version history fixed w3c/reporting#243.
-
URL to W3C Editor's Draft fixed in README.md w3c/reporting#242.
-
-
4 pull requests received 11 new comments.
-
URL fix for Structured Field Values for HTTP w3c/reporting#244 (5 comments by @clelland, @freddieleeman, @w3cbot)
-
URL to W3C Editor's Draft fixed in README.md w3c/reporting#242 (3 comments by @clelland, @freddieleeman, @w3cbot)
-
w3c/hr-time
-
1 issue closed.
-
Define LegacyTimeStamp w3c/hr-time#123.
-
-
1 issue received 3 new comments.
-
Cross-Origin Isolation in S&P section w3c/hr-time#128 (3 comments by @camillelamy, @npm1, @yoavweiss)
-
-
3 pull requests opened.
-
Expose everywhere w3c/hr-time#130, by @Ms2ger.
-
Editorial: clarify leap seconds are excluded w3c/hr-time#127, by @marcoscaceres.
-
Editorial: cleanup stray DOMTimeStamp usage w3c/hr-time#126, by @marcoscaceres.
-
-
3 pull requests merged.
-
Editorial: clarify leap seconds are excluded w3c/hr-time#127.
-
Editorial: cleanup stray DOMTimeStamp usage w3c/hr-time#126.
-
Define the EpochTimeStamp typedef w3c/hr-time#124.
-
-
5 pull requests received 22 new comments.
-
Define the EpochTimeStamp typedef w3c/hr-time#124 (12 comments by @annevk, @marcoscaceres, @TimothyGu, @yoavweiss)
-
Editorial: clarify leap seconds are excluded w3c/hr-time#127 (3 comments by @marcoscaceres, @TimothyGu)
-
w3c/hr-time#129 (1 comment by @w3cbot)
-
w3c/hr-time#125 (1 comment by @w3cbot)
-
w3c/requestidlecallback
-
2 issues opened.
-
Suggestion: expose specific information instead of deadline w3c/requestidlecallback#97, by @noamr.
-
Relying on an event loop might restart an idle period for each task w3c/requestidlecallback#96, by @noamr.
-
-
1 issue closed.
-
Relying on an event loop might restart an idle period for each task w3c/requestidlecallback#96.
-
-
4 issues received 4 new comments.
-
Suggestion: expose specific information instead of deadline w3c/requestidlecallback#97 (1 comment by @yoavweiss)
-
The order of idle callbacks across windows is inconsistent between spec & UAs w3c/requestidlecallback#82 (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)
-
timeRemaining() step 4 should define what it means to have a "time-critical task pending" w3c/requestidlecallback#87 (1 comment by @noamr)
-
-
1 pull request opened.
-
Rely on HTML spec for deadline computation w3c/requestidlecallback#95, by @noamr.
-
-
1 pull request received 9 new comments.
-
Rely on HTML spec for deadline computation w3c/requestidlecallback#95 (9 comments by @marcoscaceres, @noamr, @yoavweiss)
-
w3c/server-timing
-
2 issues opened.
-
Make it clearer what the units for `duration` are w3c/server-timing#86, by @npm1.
-
Should PerformanceServerTiming inherit from PerformanceEntry? w3c/server-timing#85, by @npm1.
-
-
2 issues received 3 new comments.
-
Server-Timing header field isn't registered w3c/server-timing#83 (2 comments by @caribouW3, @yoavweiss)
-
-
1 pull request opened.
-
Expose everywhere w3c/server-timing#84, by @Ms2ger.
-
w3c/element-timing
-
4 issues opened.
-
What is "load time"? w3c/element-timing#65, by @annevk.
-
url getter special cases data: URLs w3c/element-timing#64, by @annevk.
-
url getter should use URL serializer w3c/element-timing#63, by @annevk.
-
url getter does not handle request being null w3c/element-timing#62, by @annevk.
-
-
3 issues received 16 new comments.
w3c/user-timing
-
1 pull request opened.
-
Expose everywhere w3c/user-timing#85, by @Ms2ger.
-
w3c/largest-contentful-paint
-
2 issues opened.
-
Better handle animated images w3c/largest-contentful-paint#83, by @yoavweiss.
-
Should we skip images with an existing LCP entry? w3c/largest-contentful-paint#82, by @yoavweiss.
-
-
1 issue closed.
-
Are the units of LargestContentfulPaint.size in pixels? w3c/largest-contentful-paint#76.
-
-
1 issue received 5 new comments.
-
Should we skip images with an existing LCP entry? w3c/largest-contentful-paint#82 (5 comments by @npm1, @yoavweiss)
-
-
1 pull request merged.
-
Explain units of size w3c/largest-contentful-paint#80.
-
-
1 pull request received 1 new comment.
w3c/beacon
-
1 issue closed.
-
Integrate with Resource Timing w3c/beacon#70.
-
-
1 pull request merged.
-
Report timing for beacon when fetch is done w3c/beacon#71.
-
-
1 pull request received 1 new comment.
TR publications
-
2 documents published.
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
User Timing Level 3 published as a Working Draft. History of User Timing Level 3
-
Participants
-
2 participants joined.
-
Scott Gifford (Amazon) joined.
-
Patrick Meenan (Google LLC) joined.
-
-
1 participant left.
-
Patrick Meenan (Google LLC) left.
-
-
1 organization joined.
-
Amazon joined.
-
GitHub
w3c/navigation-timing
-
4 issues opened.
-
Using navigationStart as a baseline may expose cross-origin timing information w3c/navigation-timing#160, by @noamr.
-
Clarify spec and tests with respect to redirect info w3c/navigation-timing#158, by @npm1.
-
Add non-normative explanations for each of the attributes and when they are set or unset w3c/navigation-timing#157, by @npm1.
-
Should about:blank have a PerformanceNavigationTiming? w3c/navigation-timing#155, by @achristensen07.
-
-
2 issues closed.
-
Add non-normative explanations for each of the attributes and when they are set or unset w3c/navigation-timing#157.
-
list of possible initiator types from the resource timing API? w3c/navigation-timing#145.
-
-
6 issues received 26 new comments.
-
Using navigationStart as a baseline may expose cross-origin timing information w3c/navigation-timing#160 (13 comments by @achristensen07, @annevk, @jyasskin, @mikewest, @noamr, @yoavweiss)
-
Better integration with ResourceTiming w3c/navigation-timing#117 (5 comments by @noamr, @npm1, @yoavweiss)
-
Add non-normative explanations for each of the attributes and when they are set or unset w3c/navigation-timing#157 (3 comments by @noamr, @yoavweiss)
-
Clarify spec and tests with respect to redirect info w3c/navigation-timing#158 (2 comments by @noamr)
-
Should about:blank have a PerformanceNavigationTiming? w3c/navigation-timing#155 (2 comments by @npm1, @yoavweiss)
-
list of possible initiator types from the resource timing API? w3c/navigation-timing#145 (1 comment by @noamr)
-
-
2 pull requests opened.
-
Add a landing attribute to PerformanceNavigationTiming w3c/navigation-timing#161, by @yoavweiss.
-
Add non-normative notes for attributes. w3c/navigation-timing#159, by @noamr.
-
-
1 pull request merged.
-
Add non-normative notes for attributes. w3c/navigation-timing#159.
-
-
2 pull requests received 2 new comments.
-
Add a landing attribute to PerformanceNavigationTiming w3c/navigation-timing#161 (1 comment by @yoavweiss)
-
w3c/largest-contentful-paint
-
1 issue closed.
-
Exclude full viewport images w3c/largest-contentful-paint#73.
-
-
1 issue received 5 new comments.
-
Refine LCP to take progressive loading into account w3c/largest-contentful-paint#71 (5 comments by @DamonHD, @jonsneyers, @jyrkialakuijala, @yoavweiss)
-
-
1 pull request opened.
-
Ignore images that take the full page viewport w3c/largest-contentful-paint#81, by @npm1.
-
-
1 pull request merged.
-
Ignore images that take the full page viewport w3c/largest-contentful-paint#81.
-
-
1 pull request received 4 new comments.
-
Ignore images that take the full page viewport w3c/largest-contentful-paint#81 (4 comments by @npm1, @yoavweiss)
-
w3c/beacon
-
1 issue opened.
-
Integrate with Resource Timing w3c/beacon#70, by @noamr.
-
-
1 pull request opened.
-
Report timing for beacon when fetch is done w3c/beacon#71, by @noamr.
-
w3c/resource-timing
-
8 issues closed.
-
Examples in 4.2 are not normative, but look like ones w3c/resource-timing#243.
-
Point "current time" definition to hr-time "current high resolution time" algorithm w3c/resource-timing#235.
-
Network aborted resources SHOULD be present (not MAY) w3c/resource-timing#242.
-
Definition of initiatorType removed w3c/resource-timing#276.
-
Remove reference to "relevant application cache" and replace it with Fetch concepts w3c/resource-timing#256.
-
Syntax w3c/resource-timing#289.
-
Current definition of `startTime` exposes total redirect time even when TAO fails w3c/resource-timing#260.
-
4.3 attribute getters should all be defined as part of the processing model w3c/resource-timing#248.
-
-
11 issues received 15 new comments.
-
Consider removing wildcard option of the `Timing-Allow-Origin` header to prevent browser history leakage w3c/resource-timing#222 (1 comment by @noamr)
-
4.5.1 "timing allow check" should be called from somewhere and get "the resource" as input w3c/resource-timing#251 (1 comment by @noamr)
-
Be a bit more explicit about which subresources are to be ignored from stylesheets w3c/resource-timing#200 (1 comment by @noamr)
-
Remove reference to "relevant application cache" and replace it with Fetch concepts w3c/resource-timing#256 (1 comment by @noamr)
-
Current definition of `startTime` exposes total redirect time even when TAO fails w3c/resource-timing#260 (1 comment by @noamr)
-
4.3 attribute getters should all be defined as part of the processing model w3c/resource-timing#248 (1 comment by @noamr)
-
5 pull requests opened.
-
Remove SHOULD from non-normative example w3c/resource-timing#296, by @noamr.
-
Remove unused 'current time' definition w3c/resource-timing#295, by @noamr.
-
Bring back some non-normative notes w3c/resource-timing#293, by @noamr.
-
Pre -> code to make links work w3c/resource-timing#291, by @noamr.
-
Make 4.2 non-normative w3c/resource-timing#290, by @noamr.
-
-
5 pull requests merged.
-
Remove SHOULD from non-normative example w3c/resource-timing#296.
-
Remove unused 'current time' definition w3c/resource-timing#295.
-
Bring back some non-normative notes w3c/resource-timing#293.
-
Make 4.2 non-normative w3c/resource-timing#290.
-
Pre -> code to make links work w3c/resource-timing#291.
-
-
6 pull requests received 8 new comments.
-
replaced a number of data-cite with corresponding xref w3c/resource-timing#287 (2 comments by @marcoscaceres, @yoavweiss)
-
w3c/resource-timing#297 (1 comment by @w3cbot)
-
w3c/resource-timing#294 (1 comment by @w3cbot)
-
w3c/resource-timing#292 (1 comment by @w3cbot)
w3c/hr-time
-
2 issues opened.
-
Define LegacyTimeStamp w3c/hr-time#123, by @marcoscaceres.
-
Cross-Origin Isolation in S&P section w3c/hr-time#128, by @yoavweiss.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Define the EpochTimeStamp typedef w3c/hr-time#124, by @marcoscaceres.
-
-
1 pull request received 11 new comments.
-
Define the EpochTimeStamp typedef w3c/hr-time#124 (11 comments by @annevk, @marcoscaceres, @yoavweiss)
-
w3c/server-timing
-
1 issue opened.
-
Server-Timing header field isn't registered w3c/server-timing#83, by @mnot.
-
-
1 issue received 3 new comments.
-
Clarify security context for PerformanceResourceTiming w3c/server-timing#79 (3 comments by @fred-wang, @noamr)
-
w3c/event-timing
-
2 issues opened.
-
interactionID should be harmonized with activation triggering input events w3c/event-timing#105, by @annevk.
-
An event is not its type w3c/event-timing#104, by @annevk.
-
-
1 issue received 3 new comments.
-
interactionID should be harmonized with activation triggering input events w3c/event-timing#105 (3 comments by @annevk, @npm1)
-
-
2 pull requests opened.
-
Fix duration setting for pending pointerdowns w3c/event-timing#103, by @npm1.
-
Spec interactionId w3c/event-timing#102, by @npm1.
-
-
2 pull requests merged.
-
Fix duration setting for pending pointerdowns w3c/event-timing#103.
-
Spec interactionId w3c/event-timing#102.
-
-
1 pull request received 47 new comments.
w3c/reporting
-
1 issue received 1 new comment.
w3c/web-performance
-
1 issue opened.
-
Multi-spec non-feature TODOs for web performance WG w3c/web-performance#38, by @noamr.
-
w3c/performance-timeline
-
3 pull requests opened.
-
Add navigationId to PerformanceEntry w3c/performance-timeline#192, by @clelland.
-
Update shortname w3c/performance-timeline#191, by @npm1.
-
Update HR-Time links w3c/performance-timeline#190, by @npm1.
-
-
1 pull request merged.
-
Update HR-Time links w3c/performance-timeline#190.
-
-
2 pull requests received 10 new comments.
-
Add navigationId to PerformanceEntry w3c/performance-timeline#192 (8 comments by @clelland, @npm1, @yoavweiss)
-
w3c/user-timing
-
1 issue opened.
-
Add a null check around `detail`'s {,de}serialization, to improve readability w3c/user-timing#83, by @yoavweiss.
-
-
1 issue closed.
-
Add a null check around `detail`'s {,de}serialization, to improve readability w3c/user-timing#83.
-
-
1 pull request opened.
-
Null check for detail w3c/user-timing#84, by @npm1.
-
-
1 pull request merged.
-
Null check for detail w3c/user-timing#84.
-
w3c/device-memory
-
1 pull request received 1 new comment.
TR publications
-
2 documents published.
-
Performance Timeline Level 2 published as a Working Draft. History of Performance Timeline Level 2
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Participants
-
2 participants joined.
-
Corentin Pescheloche (Meta) joined.
-
Marcel Duran (Google LLC) joined.
-
GitHub
w3c/resource-timing
-
3 issues closed.
-
Drop all data-cite="" for known specs w3c/resource-timing#280.
-
Duplicate definitions w3c/resource-timing#279.
-
Use ByteString for nextHopProtocol w3c/resource-timing#274.
-
-
4 issues received 5 new comments.
-
Clean up cross references/versioning w3c/resource-timing#271 (2 comments by @caribouW3, @marcoscaceres)
-
-
2 pull requests opened.
-
[chore] Fix up tidy errors w3c/resource-timing#288, by @yoavweiss.
-
replaced a number of data-cite with corresponding xref w3c/resource-timing#287, by @caribouW3.
-
-
2 pull requests merged.
-
[chore] Fix up tidy errors w3c/resource-timing#288.
-
replaced a number of data-cite with corresponding xref w3c/resource-timing#287.
-
-
1 pull request closed.
-
TAO-Protect nextHopProtocol w3c/resource-timing#224.
-
-
2 pull requests received 2 new comments.
-
replaced a number of data-cite with corresponding xref w3c/resource-timing#287 (1 comment by @yoavweiss)
-
w3c/performance-timeline
-
1 issue closed.
-
Should droppedEntriesCount be frozen on each observer? w3c/performance-timeline#181.
-
-
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)
-
-
2 pull requests opened.
-
Create explainer.md w3c/performance-timeline#188, by @npm1.
-
Update dropped entries count processing logic w3c/performance-timeline#187, by @npm1.
-
-
3 pull requests merged.
-
Create explainer.md w3c/performance-timeline#188.
-
Tweak for respec config w3c/performance-timeline#185.
-
Update dropped entries count processing logic w3c/performance-timeline#187.
-
-
1 pull request received 2 new comments.
-
Update dropped entries count processing logic w3c/performance-timeline#187 (2 comments by @npm1, @yoavweiss)
-
w3c/beacon
-
1 pull request opened.
-
Fix up editor data w3c/beacon#69, by @jyasskin.
-
-
1 pull request merged.
-
Fix up editor data w3c/beacon#69.
-
w3c/navigation-timing
-
1 issue opened.
-
Lack of Feature Parity with Performace.measure() in Level 2 w3c/navigation-timing#154, by @c3-ThomasHuo.
-
-
1 issue closed.
-
The unloadEventEnd attribute w3c/navigation-timing#151.
-
-
2 issues received 2 new comments.
-
Lack of Feature Parity with Performace.measure() in Level 2 w3c/navigation-timing#154 (1 comment by @npm1)
-
-
1 pull request merged.
-
Improve processing model diagram by illustrating that unload happens out-of-sequence w3c/navigation-timing#152.
-
-
1 pull request received 2 new comments.
-
Improve processing model diagram by illustrating that unload happens out-of-sequence w3c/navigation-timing#152 (2 comments by @nicjansma, @sgomes)
-
w3c/hr-time
-
1 issue closed.
-
`timeOrigin` is not clamped w3c/hr-time#105.
-
-
1 issue received 1 new comment.
w3c/element-timing
-
1 issue closed.
-
ElementTiming in CustomElements w3c/element-timing#61.
-
-
1 issue received 2 new comments.
w3c/largest-contentful-paint
-
1 pull request received 1 new comment.
TR publications
-
3 documents published.
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
High Resolution Time published as a Working Draft. History of High Resolution Time
-
User Timing Level 3 published as a Working Draft. History of User Timing Level 3
-
GitHub
w3c/resource-timing
-
2 issues opened.
-
Missing tests following the Fetch integration w3c/resource-timing#286, by @yoavweiss.
-
Running tidy locally results in churn w3c/resource-timing#282, by @yoavweiss.
-
-
1 issue closed.
-
Running tidy locally results in churn w3c/resource-timing#282.
-
-
3 issues received 9 new comments.
-
Running tidy locally results in churn w3c/resource-timing#282 (3 comments by @marcoscaceres, @yoavweiss)
-
3 pull requests opened.
-
chore: add tidy workflow w3c/resource-timing#284, by @marcoscaceres.
-
Update and rename pr-push.yml to auto-publish.yml w3c/resource-timing#283, by @marcoscaceres.
-
Change nextHopProtocol to a ByteString w3c/resource-timing#281, by @marcoscaceres.
-
-
5 pull requests merged.
-
chore: add tidy workflow w3c/resource-timing#284.
-
Update and rename pr-push.yml to auto-publish.yml w3c/resource-timing#283.
-
Add a revalidation cache state and adapt transferSize to it w3c/resource-timing#272.
-
Change nextHopProtocol to a ByteString w3c/resource-timing#281.
-
chore: tidy up spec w3c/resource-timing#278.
-
-
1 pull request closed.
-
Change nextHopProtocol to a ByteString w3c/resource-timing#277.
-
-
5 pull requests received 11 new comments.
-
Update and rename pr-push.yml to auto-publish.yml w3c/resource-timing#283 (3 comments by @plehegar, @yoavweiss)
-
Change nextHopProtocol to a ByteString w3c/resource-timing#281 (3 comments by @marcoscaceres, @yoavweiss)
-
w3c/network-error-logging
-
1 pull request opened.
-
chore: small respec config cleanup w3c/network-error-logging#130, by @marcoscaceres.
-
-
1 pull request merged.
-
chore: small respec config cleanup w3c/network-error-logging#130.
-
-
1 pull request received 3 new comments.
-
chore: small respec config cleanup w3c/network-error-logging#130 (3 comments by @clelland, @marcoscaceres)
-
w3c/navigation-timing
-
2 issues opened.
-
Fix the auto-publish w3c/navigation-timing#153, by @plehegar.
-
The unloadEventEnd attribute w3c/navigation-timing#151, by @yujun-0127.
-
-
1 issue closed.
-
Fix the auto-publish w3c/navigation-timing#153.
-
-
3 issues received 6 new comments.
-
A scenario where transferSize is 0 for non cached loads (or may be not) w3c/navigation-timing#146 (3 comments by @Nithanaroy, @yoavweiss)
-
-
1 pull request opened.
-
Improve processing model diagram by illustrating that unload happens out-of-sequence w3c/navigation-timing#152, by @sgomes.
-
-
1 pull request merged.
-
Switch to GitHub action w3c/navigation-timing#150.
-
-
1 pull request received 2 new comments.
-
Improve processing model diagram by illustrating that unload happens out-of-sequence w3c/navigation-timing#152 (2 comments by @w3cbot, @yoavweiss)
-
w3c/largest-contentful-paint
-
1 issue received 1 new comment.
-
Are the units of LargestContentfulPaint.size in pixels? w3c/largest-contentful-paint#76 (1 comment by @npm1)
-
-
1 pull request opened.
-
Explain units of size w3c/largest-contentful-paint#80, by @npm1.
-
-
1 pull request received 2 new comments.
w3c/paint-timing
-
1 pull request opened.
-
chore: Added workflow_dispatch to GitHub action w3c/paint-timing#93, by @plehegar.
-
-
2 pull requests merged.
-
chore: Added workflow_dispatch to GitHub action w3c/paint-timing#93.
-
Chore: Add w3cids to editors w3c/paint-timing#92.
-
w3c/element-timing
-
1 issue opened.
-
ElementTiming in CustomElements w3c/element-timing#61, by @ghost.
-
-
1 issue received 2 new comments.
w3c/event-timing
-
2 issues closed.
-
Event's delay is rather vague w3c/event-timing#90.
-
Clarify arbitrary constants in the spec w3c/event-timing#86.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Explain the 16ms minimum durationThreshold w3c/event-timing#98.
-
-
1 pull request received 1 new comment.
w3c/beacon
-
1 issue opened.
-
Drop dependencies section w3c/beacon#68, by @marcoscaceres.
-
w3c/longtasks
-
1 issue closed.
-
Demo links don't work w3c/longtasks#92.
-
-
1 issue reopened.
-
Demo links don't work w3c/longtasks#92, by @npm1.
-
-
2 issues received 4 new comments.
-
Generic model for causal attribution (non-sampling based) w3c/longtasks#89 (1 comment by @omriariav)
-
4 pull requests opened.
-
Update demo websites w3c/longtasks#96, by @npm1.
-
Fix demo links w3c/longtasks#95, by @npm1.
-
Add demo in gh-pages w3c/longtasks#94, by @npm1.
-
-
4 pull requests merged.
-
Update demo websites w3c/longtasks#96.
-
Fix demo links w3c/longtasks#95.
-
Add demo in gh-pages w3c/longtasks#94.
-
Demo w3c/longtasks#93.
-
-
1 pull request received 4 new comments.
w3c/hr-time
-
1 pull request opened.
-
Editorial: remove merge garbage from example w3c/hr-time#122, by @marcoscaceres.
-
-
2 pull requests merged.
-
chore: add PULL_REQUEST_TEMPLATE.md w3c/hr-time#121.
-
Editorial: remove merge garbage from example w3c/hr-time#122.
-
-
2 pull requests received 5 new comments.
w3c/device-memory
-
1 issue opened.
-
Drop/Adjust link to ED? w3c/device-memory#44, by @tidoust.
-
-
1 issue received 3 new comments.
-
Setup auto-publish workflow for index.html; deprecate README.md w3c/device-memory#11 (3 comments by @plehegar, @tidoust)
-
-
2 pull requests opened.
-
Add editor ID w3c/device-memory#45, by @tidoust.
-
Fix override to WD in auto-publish workflow w3c/device-memory#43, by @tidoust.
-
-
5 pull requests merged.
-
Add editor ID w3c/device-memory#45.
-
Fix override to WD in auto-publish workflow w3c/device-memory#43.
-
Gh pages redirect w3c/device-memory#42.
-
Publish as a WD w3c/device-memory#41.
-
Obsolete. GH action deploys to /TR directly w3c/device-memory#40.
-
-
2 pull requests received 6 new comments.
-
Fix override to WD in auto-publish workflow w3c/device-memory#43 (4 comments by @dontcallmedom, @plehegar, @tidoust)
-
w3c/user-timing
-
1 issue closed.
-
Use WHATWG/INFRA 'is' definition for 'match' w3c/user-timing#80.
-
-
1 pull request opened.
-
Use 'is' instead of match w3c/user-timing#82, by @npm1.
-
-
2 pull requests merged.
-
Switch to GitHub action w3c/user-timing#81.
-
Use 'is' instead of match w3c/user-timing#82.
-
-
1 pull request received 3 new comments.
TR publications
-
3 documents published.
-
Performance Timeline Level 2 published as a Working Draft. History of Performance Timeline Level 2
-
Server Timing published as a Working Draft. History of Server Timing
-
High Resolution Time published as a Working Draft. History of High Resolution Time
-
Participants
-
1 participant left.
-
Ulan Degenbaev (Google LLC) left.
-
GitHub
w3c/performance-timeline
-
2 issues opened.
-
Unused flag "add to performance entry buffer flag" on queueing a PerformanceEntry w3c/performance-timeline#183, by @legendecas.
-
API shape for monitoring new navigation-like entries such as App History, BFCache, etc w3c/performance-timeline#182, by @nicjansma.
-
-
1 issue closed.
-
Unused flag "add to performance entry buffer flag" on queueing a PerformanceEntry w3c/performance-timeline#183.
-
-
2 issues received 4 new comments.
-
Unused flag "add to performance entry buffer flag" on queueing a PerformanceEntry w3c/performance-timeline#183 (2 comments by @npm1)
-
API shape for monitoring new navigation-like entries such as App History, BFCache, etc w3c/performance-timeline#182 (2 comments by @domenic, @yoavweiss)
-
-
3 pull requests opened.
-
w3c.json tweaks w3c/performance-timeline#186, by @plehegar.
-
Tweak for respec config w3c/performance-timeline#185, by @plehegar.
-
Switch to GitHub action w3c/performance-timeline#184, by @plehegar.
-
-
2 pull requests merged.
-
Switch to GitHub action w3c/performance-timeline#184.
-
w3c.json tweaks w3c/performance-timeline#186.
-
-
1 pull request received 2 new comments.
w3c/paint-timing
-
1 issue closed.
-
Set up auto-publishing? w3c/paint-timing#87.
-
-
1 issue received 2 new comments.
-
2 pull requests opened.
-
Chore: Add w3cids to editors w3c/paint-timing#92, by @plehegar.
-
Switch to auto-publish in /TR w3c/paint-timing#91, by @plehegar.
-
-
1 pull request merged.
-
Switch to auto-publish in /TR w3c/paint-timing#91.
-
w3c/beacon
-
1 pull request opened.
-
Switch to GitHub action w3c/beacon#67, by @plehegar.
-
-
1 pull request merged.
-
Switch to GitHub action w3c/beacon#67.
-
w3c/server-timing
-
1 pull request opened.
-
Switch to GitHub action w3c/server-timing#81, by @plehegar.
-
-
1 pull request merged.
-
Switch to GitHub action w3c/server-timing#81.
-
w3c/resource-timing
-
5 issues opened.
-
Drop all data-cite="" for known specs w3c/resource-timing#280, by @marcoscaceres.
-
Duplicate definitions w3c/resource-timing#279, by @marcoscaceres.
-
Definition of initiatorType removed w3c/resource-timing#276, by @MasonM.
-
No mention to WebIDL in conformance section w3c/resource-timing#275, by @himorin.
-
Use ByteString for nextHopProtocol w3c/resource-timing#274, by @annevk.
-
-
2 issues closed.
-
No mention to WebIDL in conformance section w3c/resource-timing#275.
-
Exposing Early Hints preloads to ResourceTiming w3c/resource-timing#273.
-
-
5 issues received 13 new comments.
-
Exposing Early Hints preloads to ResourceTiming w3c/resource-timing#273 (5 comments by @kinu, @yoavweiss)
-
No mention to WebIDL in conformance section w3c/resource-timing#275 (4 comments by @marcoscaceres, @nicjansma, @npm1, @yoavweiss)
-
-
2 pull requests opened.
-
chore: tidy up spec w3c/resource-timing#278, by @marcoscaceres.
-
Change nextHopProtocol to a ByteString w3c/resource-timing#277, by @yoavweiss.
-
-
3 pull requests received 3 new comments.
-
Add a revalidation cache state and adapt transferSize to it w3c/resource-timing#272 (1 comment by @yoavweiss)
w3c/user-timing
-
1 issue opened.
-
Use WHATWG/INFRA 'is' definition for 'match' w3c/user-timing#80, by @himorin.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Switch to GitHub action w3c/user-timing#81, by @plehegar.
-
w3c/navigation-timing
-
1 issue opened.
-
The "Obsolete" label is rendered in a seemingly random place w3c/navigation-timing#149, by @Krinkle.
-
-
1 issue received 1 new comment.
-
The "Obsolete" label is rendered in a seemingly random place w3c/navigation-timing#149 (1 comment by @marcoscaceres)
-
-
1 pull request opened.
-
Switch to GitHub action w3c/navigation-timing#150, by @plehegar.
-
w3c/device-memory
-
1 issue closed.
-
Setup auto-publishing w3c/device-memory#31.
-
-
1 issue received 2 new comments.
-
8 pull requests opened.
-
Gh pages redirect w3c/device-memory#42, by @plehegar.
-
Publish as a WD w3c/device-memory#41, by @plehegar.
-
Obsolete. GH action deploys to /TR directly w3c/device-memory#40, by @plehegar.
-
chore: update README w3c/device-memory#39, by @marcoscaceres.
-
chore: cleanup root dir w3c/device-memory#38, by @marcoscaceres.
-
Delete .travis.yml w3c/device-memory#37, by @caribouW3.
-
Create auto-publish.yml w3c/device-memory#36, by @caribouW3.
-
chore: add pr_preview.json w3c/device-memory#35, by @marcoscaceres.
-
-
3 pull requests merged.
-
chore: add pr_preview.json w3c/device-memory#35.
-
Create auto-publish.yml w3c/device-memory#36.
-
Delete .travis.yml w3c/device-memory#37.
-
-
1 pull request closed.
-
chore: cleanup root dir w3c/device-memory#38.
-
-
3 pull requests received 7 new comments.
w3c/event-timing
-
2 issues received 5 new comments.
-
Support for mousemove and other continuous events w3c/event-timing#99 (4 comments by @bennym7n, @npm1)
-
w3c/largest-contentful-paint
-
1 issue opened.
-
Specify exclusions for opacity:0, display:none, etc. w3c/largest-contentful-paint#79, by @npm1.
-
w3c/requestidlecallback
-
1 issue opened.
-
Can we rename this spec? w3c/requestidlecallback#91, by @marcoscaceres.
-
-
4 pull requests opened.
-
chore: auto-publish w3c/requestidlecallback#94, by @marcoscaceres.
-
chore: add .pr-preview.json support w3c/requestidlecallback#93, by @marcoscaceres.
-
Editorial: rename spec to requestIdleCallback() w3c/requestidlecallback#92, by @marcoscaceres.
-
Editorial: xref cleanup w3c/requestidlecallback#90, by @marcoscaceres.
-
-
2 pull requests merged.
-
chore: add .pr-preview.json support w3c/requestidlecallback#93.
-
Editorial: xref cleanup w3c/requestidlecallback#90.
-
-
2 pull requests received 8 new comments.
-
chore: auto-publish w3c/requestidlecallback#94 (5 comments by @caribouW3, @marcoscaceres, @yoavweiss)
-
w3c/hr-time
-
5 pull requests opened.
-
chore: add PULL_REQUEST_TEMPLATE.md w3c/hr-time#121, by @marcoscaceres.
-
chore: cleanup repo root w3c/hr-time#120, by @marcoscaceres.
-
chore: auto-publish spec as WD w3c/hr-time#119, by @marcoscaceres.
-
chore: automatic tidy w3c/hr-time#118, by @marcoscaceres.
-
chore: cleanup config w3c/hr-time#117, by @marcoscaceres.
-
-
4 pull requests merged.
-
chore: auto-publish spec as WD w3c/hr-time#119.
-
chore: automatic tidy w3c/hr-time#118.
-
chore: cleanup config w3c/hr-time#117.
-
chore: cleanup repo root w3c/hr-time#120.
-
-
4 pull requests received 14 new comments.
-
chore: add PULL_REQUEST_TEMPLATE.md w3c/hr-time#121 (5 comments by @marcoscaceres, @nicjansma, @yoavweiss)
-
chore: auto-publish spec as WD w3c/hr-time#119 (4 comments by @caribouW3, @marcoscaceres, @yoavweiss)
-
w3c/web-performance
-
1 issue opened.
-
Add .pr_preview.json to specs w3c/web-performance#37, by @marcoscaceres.
-
-
1 issue closed.
-
Add .pr_preview.json to specs w3c/web-performance#37.
-
-
2 issues received 4 new comments.
w3c/longtasks
-
1 issue opened.
-
Demo links don't work w3c/longtasks#92, by @niieani.
-
-
1 issue received 1 new comment.
w3c/element-timing
-
1 issue opened.
-
PerformanceObserver api return result not what i need w3c/element-timing#60, by @nextdoorUncleLiu.
-
-
1 issue received 5 new comments.
-
PerformanceObserver api return result not what i need w3c/element-timing#60 (5 comments by @nextdoorUncleLiu, @npm1)
-
TR publications
-
1 document published.
-
Page Visibility Level 2 published as a Candidate Recommendation Snapshot. History of Page Visibility Level 2
-
GitHub
w3c/web-performance
-
3 issues opened.
-
Add pull request template w3c/web-performance#36, by @marcoscaceres.
-
Cleanup specs w3c/web-performance#35, by @marcoscaceres.
-
Autopublish specs w3c/web-performance#34, by @marcoscaceres.
-
-
1 issue closed.
-
Put in place a process to improve link validation w3c/web-performance#26.
-
-
4 issues received 13 new comments.
-
Put in place a process to improve link validation w3c/web-performance#26 (1 comment by @marcoscaceres)
w3c/navigation-timing
-
2 issues opened.
-
Add a test that ensures `fetchStart` matches the SW's fetch event start time w3c/navigation-timing#148, by @yoavweiss.
-
Spec needs a serious rewrite w3c/navigation-timing#147, by @marcoscaceres.
-
-
2 issues closed.
-
Spec needs a serious rewrite w3c/navigation-timing#147.
-
3.2 workerTime definition w3c/navigation-timing#134.
-
-
2 issues received 6 new comments.
-
1 pull request merged.
-
Integrate with service worker timing w3c/navigation-timing#143.
-
-
1 pull request received 25 new comments.
-
Integrate with service worker timing w3c/navigation-timing#143 (25 comments by @marcoscaceres, @noamr, @yoavweiss)
-
w3c/resource-timing
-
1 issue opened.
-
Exposing Early Hints preloads to ResourceTiming w3c/resource-timing#273, by @yoavweiss.
-
-
7 issues received 22 new comments.
-
Exposing Early Hints preloads to ResourceTiming w3c/resource-timing#273 (10 comments by @bashi, @colinbendell, @yoavweiss)
-
Clean up cross references/versioning w3c/resource-timing#271 (4 comments by @caribouW3, @marcoscaceres, @yoavweiss)
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (3 comments by @andydavies, @nicjansma)
-
Resource initiator information to enable creation of dependency trees w3c/resource-timing#263 (2 comments by @marcelduran, @nicjansma)
-
Consider removing nextHopProtocol as it may expose whether visitor is using VPN / proxy w3c/resource-timing#221 (1 comment by @sleevi)
-
-
1 pull request opened.
-
Add a revalidation cache state and adapt transferSize to it w3c/resource-timing#272, by @yoavweiss.
-
w3c/event-timing
-
2 pull requests opened.
-
Use main branch in workflow w3c/event-timing#101, by @npm1.
-
Remove context object usage w3c/event-timing#100, by @npm1.
-
-
2 pull requests merged.
-
Use main branch in workflow w3c/event-timing#101.
-
Remove context object usage w3c/event-timing#100.
-
-
2 pull requests received 2 new comments.
w3c/element-timing
-
2 pull requests opened.
-
Use main branch in build.yml w3c/element-timing#59, by @npm1.
-
Remove context object w3c/element-timing#58, by @npm1.
-
-
2 pull requests merged.
-
Use main branch in build.yml w3c/element-timing#59.
-
Remove context object w3c/element-timing#58.
-
w3c/largest-contentful-paint
-
1 issue opened.
-
Are the units of LargestContentfulPaint.size in pixels? w3c/largest-contentful-paint#76, by @dashed.
-
-
1 issue received 2 new comments.
-
Are the units of LargestContentfulPaint.size in pixels? w3c/largest-contentful-paint#76 (2 comments by @dashed, @npm1)
-
-
3 pull requests opened.
-
Update build.yml w3c/largest-contentful-paint#78, by @npm1.
-
Remove MDN panels w3c/largest-contentful-paint#77, by @npm1.
-
Remove context object w3c/largest-contentful-paint#75, by @npm1.
-
-
3 pull requests merged.
-
Update build.yml w3c/largest-contentful-paint#78.
-
Remove MDN panels w3c/largest-contentful-paint#77.
-
Remove context object w3c/largest-contentful-paint#75.
-
w3c/network-error-logging
-
1 issue received 4 new comments.
-
Proposal: Include certificate fingerprint(s) in NEL reports w3c/network-error-logging#127 (4 comments by @ivanr, @sleevi)
-
w3c/performance-timeline
-
1 issue opened.
-
Should droppedEntriesCount be frozen on each observer? w3c/performance-timeline#181, by @npm1.
-
-
1 issue received 6 new comments.
-
Should droppedEntriesCount be frozen on each observer? w3c/performance-timeline#181 (6 comments by @nicjansma, @npm1, @sefeng211)
-
-
1 pull request opened.
-
Remove context object w3c/performance-timeline#180, by @npm1.
-
-
1 pull request merged.
-
Remove context object w3c/performance-timeline#180.
-
-
1 pull request received 2 new comments.
w3c/hr-time
-
1 issue opened.
-
1 issue received 4 new comments.
-
Suggestions: ticking during sleep, comparison across contexts, time origin + now semantics, and skew definition w3c/hr-time#115 (4 comments by @jonathanmayer, @npm1)
-
-
1 pull request opened.
-
Remove context object usage w3c/hr-time#116, by @npm1.
-
-
1 pull request merged.
-
Remove context object usage w3c/hr-time#116.
-
w3c/reporting
-
1 issue opened.
-
1 issue closed.
-
1 issue received 1 new comment.
-
Is the definition of HTTP response header endpoints mandatory or can it be left out in the syntax? w3c/reporting#236 (1 comment by @clelland)
-
TR publications
-
1 document published.
-
Resource Timing Level 2 published as a Working Draft. History of Resource Timing Level 2
-
Participants
-
6 participants joined.
-
Alex Christensen (Apple Inc.) joined.
-
Ryosuke Niwa (Apple Inc.) joined.
-
Cameron McCormack (Apple Inc.) joined.
-
Patrick Hamann (Fastly) joined.
-
Hemanth Kishen Udupi Vedavysa (Adobe) joined.
-
yi lin (Baidu, Inc.) joined.
-
-
4 organizations joined.
-
Apple Inc. joined.
-
Adobe joined.
-
Fastly joined.
-
Baidu, Inc. joined.
-
GitHub
w3c/performance-timeline
-
1 issue closed.
-
When should a UA clear its entry buffers? w3c/performance-timeline#178.
-
-
1 issue received 1 new comment.
w3c/resource-timing
-
4 issues opened.
-
Clean up cross references/versioning w3c/resource-timing#271, by @annevk.
-
Add tests for TAO-fail behavior changes since FETCH integration w3c/resource-timing#264, by @noamr.
-
Resource initiator information to enable creation of dependency trees w3c/resource-timing#263, by @yoavweiss.
-
Render blocking status of resources w3c/resource-timing#262, by @yoavweiss.
-
-
8 issues closed.
-
Add tests for TAO-fail behavior changes since FETCH integration w3c/resource-timing#264.
-
transferSize might reveal HttpOnly cookies w3c/resource-timing#238.
-
Pass realm when creating PerformanceResourceTiming w3c/resource-timing#226.
-
`nextHopProtocol` needs to be defined in terms of Fetch w3c/resource-timing#247.
-
`initiatorType` processing model needs to be defined in terms of Fetch w3c/resource-timing#246.
-
4.3 `startTime` and `duration` should point to the processing model w3c/resource-timing#245.
-
Define Resource Timing in terms of Fetch w3c/resource-timing#39.
-
Definition of `name` needs to be more precise w3c/resource-timing#244.
-
-
11 issues received 14 new comments.
-
Add tests for TAO-fail behavior changes since FETCH integration w3c/resource-timing#264 (2 comments by @noamr, @npm1)
-
Remove reference to "relevant application cache" and replace it with Fetch concepts w3c/resource-timing#256 (2 comments by @bdekoz, @nicjansma)
-
Clarify when entry is added to performance entry buffer w3c/resource-timing#82 (1 comment by @noamr)
-
Add response status codes for resources in Resource Timing API. w3c/resource-timing#90 (1 comment by @mehulkar)
-
4.3 `startTime` and `duration` should point to the processing model w3c/resource-timing#245 (1 comment by @noamr)
-
`initiatorType` processing model needs to be defined in terms of Fetch w3c/resource-timing#246 (1 comment by @noamr)
-
`nextHopProtocol` needs to be defined in terms of Fetch w3c/resource-timing#247 (1 comment by @noamr)
-
-
6 pull requests opened.
-
Remove stray <<< HEAD w3c/resource-timing#270, by @noamr.
-
Remove stray <<<< w3c/resource-timing#269, by @noamr.
-
Fix exports w3c/resource-timing#268, by @yoavweiss.
-
Initial attempt at autopublishing w3c/resource-timing#267, by @yoavweiss.
-
Expose transferSize, encodedBodySize, decodedBodySize w3c/resource-timing#266, by @noamr.
-
Export setup function w3c/resource-timing#265, by @noamr.
-
-
6 pull requests merged.
-
Remove stray <<< HEAD w3c/resource-timing#270.
-
Expose transferSize, encodedBodySize, decodedBodySize w3c/resource-timing#266.
-
Fix exports w3c/resource-timing#268.
-
Initial attempt at autopublishing w3c/resource-timing#267.
-
Export setup function w3c/resource-timing#265.
-
Prepare for FETCH integration w3c/resource-timing#261.
-
-
2 pull requests closed.
-
Remove stray <<<< w3c/resource-timing#269.
-
Pass realm when creating PerformanceResourceTiming w3c/resource-timing#225.
-
-
5 pull requests received 21 new comments.
-
Expose transferSize, encodedBodySize, decodedBodySize w3c/resource-timing#266 (10 comments by @noamr, @yoavweiss)
-
Pass realm when creating PerformanceResourceTiming w3c/resource-timing#225 (3 comments by @dudss37, @noamr, @yoavweiss)
-
w3c/navigation-timing
-
3 issues opened.
-
A scenario where transferSize is 0 for non cached loads (or may be not) w3c/navigation-timing#146, by @Nithanaroy.
-
list of possible initiator types from the resource timing API? w3c/navigation-timing#145, by @ThierryMajutec.
-
Clarify security context for PerformanceNavigationTiming w3c/navigation-timing#144, by @fred-wang.
-
-
3 issues closed.
-
3.3 Getters should not replicate processing model definitions w3c/navigation-timing#135.
-
4.2 Same origin check should have clear inputs w3c/navigation-timing#137.
-
PerformanceNavigationTiming needs a realm w3c/navigation-timing#125.
-
-
11 issues received 20 new comments.
-
A scenario where transferSize is 0 for non cached loads (or may be not) w3c/navigation-timing#146 (4 comments by @Nithanaroy, @npm1)
-
Clarify security context for PerformanceNavigationTiming w3c/navigation-timing#144 (4 comments by @fred-wang, @noamr, @npm1)
-
list of possible initiator types from the resource timing API? w3c/navigation-timing#145 (2 comments by @noamr, @npm1)
-
3.1 duration definition should be done in a single place w3c/navigation-timing#133 (2 comments by @noamr)
-
3.3 Getters should not replicate processing model definitions w3c/navigation-timing#135 (1 comment by @noamr)
-
Possibility to get the HTTP status code from the Response Header ? w3c/navigation-timing#126 (1 comment by @nicjansma)
-
-
2 pull requests opened.
-
Integrate with service worker timing w3c/navigation-timing#143, by @noamr.
-
Use real refs for DOM metrics w3c/navigation-timing#142, by @noamr.
-
-
2 pull requests merged.
-
Use real refs for DOM metrics w3c/navigation-timing#142.
-
Integration with the HTML spec w3c/navigation-timing#141.
-
-
2 pull requests received 12 new comments.
w3c/largest-contentful-paint
-
1 issue opened.
-
Canvas image w3c/largest-contentful-paint#74, by @npm1.
-
-
1 issue received 1 new comment.
-
"Contentful style-background-images" definition is too vague to be relied upon? w3c/largest-contentful-paint#55 (1 comment by @itcomindo)
-
w3c/server-timing
-
1 issue opened.
-
Clarify security context for PerformanceResourceTiming w3c/server-timing#79, by @fred-wang.
-
TR publications
-
5 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
-
User Timing Level 3 published as a Working Draft. History of User Timing Level 3
-
Resource Timing Level 2 published as a Working Draft. History of Resource Timing Level 2
-
Participants
-
3 participants joined.
-
Aditya Punjani (Airbnb Inc) joined.
-
Andrew Galloni (Cloudflare) joined.
-
Marcos Caceres (Apple Inc.) joined.
-
-
17 participants left.
-
yajun chen (China Mobile Communications Corporation) left.
-
Yanling Feng (Shenzhen University of Information Technology（深圳信息职业技术大学）) left.
-
Keiko Itakura (Rakuten Group, Inc.) left.
-
Ziran Sun (Igalia) left.
-
Rob Buis (Igalia) left.
-
Narifumi Iwamoto (Intel Corporation) left.
-
Aditya Punjani (Airbnb Inc) left.
-
Hong Zheng (Intel Corporation) left.
-
峰 高 (360) left.
-
Yuchen Liu (360) left.
-
Joseph Pecoraro (Apple Inc.) left.
-
Alex Christensen (Apple Inc.) left.
-
Ryosuke Niwa (Apple Inc.) left.
-
Xiaoqian Wu (W3C) left.
-
Jonathan Ding (Intel Corporation) left.
-
Ganesh Rao (Intel Corporation) left.
-
Marcos Caceres (Apple Inc.) left.
-
-
5 organizations joined.
-
Airbnb Inc joined.
-
Cloudflare joined.
-
The New York Times joined.
-
Alibaba Group joined.
-
British Broadcasting Corporation joined.
-
GitHub
w3c/resource-timing
-
2 issues opened.
-
Current definition of `startTime` exposes total redirect time even when TAO fails w3c/resource-timing#260, by @noamr.
-
Which DNS timings should be exposed when fetching redirected resource w3c/resource-timing#258, by @tommckee1.
-
-
2 issues closed.
-
Which DNS timings should be exposed when fetching redirected resource w3c/resource-timing#258.
-
Update the editors list w3c/resource-timing#241.
-
-
5 issues received 28 new comments.
-
4.6 Integrate the processing model with Fetch w3c/resource-timing#252 (8 comments by @annevk, @noamr)
-
Current definition of `startTime` exposes total redirect time even when TAO fails w3c/resource-timing#260 (7 comments by @annevk, @noamr, @npm1)
-
Be a bit more explicit about which subresources are to be ignored from stylesheets w3c/resource-timing#200 (6 comments by @annevk, @mfalken, @yoavweiss)
-
Which DNS timings should be exposed when fetching redirected resource w3c/resource-timing#258 (5 comments by @npm1, @tommckee1, @yoavweiss)
-
Would like a precise way to map PerformanceTimings to FetchEvent w3c/resource-timing#259 (2 comments by @annevk, @npm1)
-
-
1 pull request opened.
-
Prepare for FETCH integration w3c/resource-timing#261, by @noamr.
-
-
1 pull request merged.
-
Change editors and fixup respec errors w3c/resource-timing#253.
-
-
1 pull request closed.
-
Use FETCH#URL to describe the name of a request w3c/resource-timing#257.
-
-
5 pull requests received 82 new comments.
-
Prepare for FETCH integration w3c/resource-timing#261 (68 comments by @annevk, @mikewest, @noamr, @npm1, @yoavweiss)
-
Use FETCH#URL to describe the name of a request w3c/resource-timing#257 (7 comments by @annevk, @noamr, @yoavweiss)
-
Conform 'current time' definition to the current hr-time spec w3c/resource-timing#236 (1 comment by @yoavweiss)
-
Pass realm when creating PerformanceResourceTiming w3c/resource-timing#225 (1 comment by @yoavweiss)
-
w3c/navigation-timing
-
1 issue opened.
-
AppCache meaning w3c/navigation-timing#140, by @ThierryMajutec.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Integration with the HTML spec w3c/navigation-timing#141, by @noamr.
-
Change editors w3c/navigation-timing#139, by @yoavweiss.
-
-
1 pull request merged.
-
Change editors w3c/navigation-timing#139.
-
-
2 pull requests received 10 new comments.
w3c/network-error-logging
-
1 issue opened.
-
Proposal: Convey Extended DNS Errors w3c/network-error-logging#129, by @bemasc.
-
-
1 issue received 9 new comments.
-
Proposal: Convey Extended DNS Errors w3c/network-error-logging#129 (9 comments by @chris-wood, @dcreager, @rniwa)
-
w3c/hr-time
-
3 issues closed.
-
Comments on "Define 'relative high resolution time'" w3c/hr-time#96.
-
High resolution time is not defined w3c/hr-time#88.
-
Expose "unsafe now" for internal uses w3c/hr-time#99.
-
-
2 issues received 3 new comments.
-
Comments on "Define 'relative high resolution time'" w3c/hr-time#96 (2 comments by @annevk, @yoavweiss)
-
-
8 pull requests opened.
-
Expose "relative high resolution coarse time" w3c/hr-time#114, by @noamr.
-
Meta: export coarsen time for Fetch w3c/hr-time#113, by @annevk.
-
Add coarsened shared current time w3c/hr-time#112, by @annevk.
-
Coarsen relative time w3c/hr-time#111, by @yoavweiss.
-
Change editors w3c/hr-time#110, by @yoavweiss.
-
Fix reference to unsafe shared time w3c/hr-time#109, by @yoavweiss.
-
Fix links to shared monotonic clock w3c/hr-time#108, by @noamr.
-
-
9 pull requests merged.
-
Expose "relative high resolution coarse time" w3c/hr-time#114.
-
Meta: export coarsen time for Fetch w3c/hr-time#113.
-
Add coarsened shared current time w3c/hr-time#112.
-
Coarsen relative time w3c/hr-time#111.
-
Coarsen timeOrigin w3c/hr-time#106.
-
Change editors w3c/hr-time#110.
-
Fix reference to unsafe shared time w3c/hr-time#109.
-
Fix links to shared monotonic clock w3c/hr-time#108.
-
-
4 pull requests received 26 new comments.
-
Change "global monotonic clock" to "shared" and expose new algorithm "unsafe shared current time" w3c/hr-time#107 (12 comments by @noamr, @npm1, @yoavweiss)
-
w3c/element-timing
-
1 issue opened.
-
Element opt-out from being considered in timing? w3c/element-timing#57, by @getify.
-
-
1 issue closed.
-
Element opt-out from being considered in timing? w3c/element-timing#57.
-
-
1 issue received 1 new comment.
w3c/largest-contentful-paint
-
1 issue received 8 new comments.
-
Refine LCP to take progressive loading into account w3c/largest-contentful-paint#71 (8 comments by @jonsneyers, @jyrkialakuijala, @mo271, @npm1, @yoavweiss)
-
w3c/event-timing
-
1 pull request received 6 new comments.
w3c/performance-timeline
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Change editors w3c/performance-timeline#179, by @yoavweiss.
-
-
2 pull requests merged.
-
Change hasDroppedEntries to droppedEntriesCount w3c/performance-timeline#177.
-
Change editors w3c/performance-timeline#179.
-
-
1 pull request received 1 new comment.
-
Change hasDroppedEntries to droppedEntriesCount w3c/performance-timeline#177 (1 comment by @yoavweiss)
-
w3c/reporting
-
1 issue closed.
-
Spec should be clear about requiring extensions to declare observability w3c/reporting#222.
-
-
2 issues received 4 new comments.
-
Spec should be clear about requiring extensions to declare observability w3c/reporting#222 (2 comments by @clelland)
w3c/user-timing
-
2 pull requests opened.
-
Remove DOS newlines w3c/user-timing#79, by @yoavweiss.
-
Change editors w3c/user-timing#78, by @yoavweiss.
-
-
2 pull requests merged.
-
Change editors w3c/user-timing#78.
-
Remove DOS newlines w3c/user-timing#79.
-
-
1 pull request received 2 new comments.
Lifecycle
Participants
-
6 participants joined.
-
Patrick Meenan (Google LLC) joined.
-
Marcos Caceres (Apple Inc.) joined.
-
Michelle Vu (W3C Invited Experts) joined.
-
Charles-Philippe Clermont (Shopify) joined.
-
Colin Bendell (Shopify) joined.
-
Ilya Grigorik (Shopify) joined.
-
-
2 participants left.
-
Michelle Vu (W3C Invited Experts) left.
-
Ilya Grigorik (Shopify) left.
-
-
8 organizations joined.
-
Mozilla Foundation joined.
-
Microsoft Corporation joined.
-
Google LLC joined.
-
Akamai Technologies joined.
-
Wikimedia Foundation joined.
-
Meta joined.
-
Shopify joined.
-
Salesforce joined.
-
-
25 organizations left.
-
eyeo GmbH left.
-
Shenzhen University of Information Technology（深圳信息职业技术大学） left.
-
Rakuten Group, Inc. left.
-
The New York Times left.
-
China Mobile Communications Corporation left.
-
Igalia left.
-
Cloudflare left.
-
The Washington Post left.
-
British Broadcasting Corporation left.
-
Search Engine Optimization Inc left.
-
Mitsubishi Electric Corporation left.
-
Salesforce left.
-
Wikimedia Foundation left.
-
Shopify left.
-
Apple Inc. left.
-
Microsoft Corporation left.
-
360 left.
-
Intel Corporation left.
-
Alibaba Group left.
-
Airbnb Inc left.
-
Baidu, Inc. left.
-
Google LLC left.
-
Meta left.
-
Akamai Technologies left.
-
Mozilla Foundation left.
-
GitHub
w3c/resource-timing
-
2 issues opened.
-
Remove reference to "relevant application cache" and replace it with Fetch concepts w3c/resource-timing#256, by @yoavweiss.
-
Resource direct lookup support w3c/resource-timing#255, by @sean-roberts.
-
-
1 issue received 5 new comments.
-
1 pull request opened.
-
Use FETCH#URL to describe the name of a request w3c/resource-timing#257, by @noamr.
-
w3c/reporting
-
4 issues opened.
-
Formalize how subsetting sending reports works w3c/reporting#234, by @zcorpan.
-
Fetch integration: missing at least "method" when creating a request w3c/reporting#232, by @zcorpan.
-
Batch reports from related documents? w3c/reporting#226, by @clelland.
-
6 issues closed.
-
Fetch integration: missing at least "method" when creating a request w3c/reporting#232.
-
GCing an active but failing endpoint is counterproductive w3c/reporting#23.
-
Capability URL problem bigger than advertized w3c/reporting#155.
-
Privacy considerations should describe how user IDs can leak w3c/reporting#192.
-
Disallow include_subdomains from eTLDs w3c/reporting#159.
-
Use Infra types to create JSON w3c/reporting#224.
-
-
7 issues received 17 new comments.
-
Fetch integration: missing at least "method" when creating a request w3c/reporting#232 (5 comments by @annevk, @clelland, @zcorpan)
-
Report delivery - executing steps "asynchronously" and queueing tasks on which event loop? w3c/reporting#235 (4 comments by @annevk, @clelland, @zcorpan)
-
Formalize how subsetting sending reports works w3c/reporting#234 (2 comments by @clelland, @zcorpan)
-
Privacy considerations should describe how user IDs can leak w3c/reporting#192 (2 comments by @clelland, @jyasskin)
-
-
6 pull requests opened.
-
Set report request mode to POST w3c/reporting#233, by @clelland.
-
Add note on leaking user identifiers. w3c/reporting#231, by @clelland.
-
Expand on capability URL privacy hazards. w3c/reporting#230, by @clelland.
-
Remove undefined 'replace' operation. w3c/reporting#229, by @clelland.
-
Remove GC of failing endpoint groups. w3c/reporting#228, by @clelland.
-
Use Infra's 'Serialize an Infra value to JSON bytes' w3c/reporting#227, by @clelland.
-
-
4 pull requests merged.
-
Set report request mode to POST w3c/reporting#233.
-
Remove GC of failing endpoint groups. w3c/reporting#228.
-
Expand on capability URL privacy hazards. w3c/reporting#230.
-
Use Infra's 'Serialize an Infra value to JSON bytes' w3c/reporting#227.
-
-
1 pull request received 2 new comments.
w3c/web-performance
-
2 issues opened.
-
Clarify gdoc in meetings w3c/web-performance#33, by @npm1.
-
Missing TPAC 2019 w3c/web-performance#32, by @npm1.
-
w3c/largest-contentful-paint
-
2 issues opened.
-
Exclude full viewport images w3c/largest-contentful-paint#73, by @npm1.
-
Very large transparent SVG should not count as LCP w3c/largest-contentful-paint#72, by @rik.
-
-
1 issue received 4 new comments.
-
Refine LCP to take progressive loading into account w3c/largest-contentful-paint#71 (4 comments by @jyrkialakuijala, @mo271, @yoavweiss)
-
w3c/hr-time
-
1 issue opened.
-
`timeOrigin` is not clamped w3c/hr-time#105, by @yoavweiss.
-
-
2 issues closed.
-
Make high resolution time dependant on cross-origin isolated w3c/hr-time#89.
-
Add sub-millisecond timer use-cases w3c/hr-time#101.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Coarsen timeOrigin w3c/hr-time#106, by @yoavweiss.
-
-
2 pull requests merged.
-
Limit the timer resolution in non-isolated contexts w3c/hr-time#93.
-
Add a use cases section w3c/hr-time#103.
-
-
3 pull requests received 22 new comments.
-
Limit the timer resolution in non-isolated contexts w3c/hr-time#93 (18 comments by @annevk, @npm1, @yoavweiss)
-
w3c/element-timing
-
2 issues opened.
-
Should SVG be supported? w3c/element-timing#56, by @npm1.
-
Starting point shift with countering transform change should be ignored w3c/element-timing#55, by @wangxianzhu.
-
-
1 issue closed.
-
Starting point shift with countering transform change should be ignored w3c/element-timing#55.
-
-
3 issues received 4 new comments.
-
Starting point shift with countering transform change should be ignored w3c/element-timing#55 (2 comments by @npm1, @wangxianzhu)
-
w3c/paint-timing
-
2 pull requests opened.
-
Trigger Github Actions for the main branch w3c/paint-timing#90, by @rik.
-
Use modern JavaScript loop for examples w3c/paint-timing#89, by @rik.
-
-
2 pull requests merged.
-
Trigger Github Actions for the main branch w3c/paint-timing#90.
-
Use modern JavaScript loop for examples w3c/paint-timing#89.
-
w3c/performance-timeline
-
1 issue opened.
-
When should a UA clear its entry buffers? w3c/performance-timeline#178, by @sefeng211.
-
-
2 issues received 3 new comments.
-
PerformanceEntries are affected by backgrounded status w3c/performance-timeline#105 (2 comments by @npm1)
-
-
1 pull request received 1 new comment.
w3c/navigation-timing
-
1 issue opened.
-
Connection time missing after redirection... w3c/navigation-timing#138, by @ThierryMajutec.
-
-
1 issue closed.
-
Connection time missing after redirection... w3c/navigation-timing#138.
-
-
1 issue received 2 new comments.
-
Connection time missing after redirection... w3c/navigation-timing#138 (2 comments by @npm1, @ThierryMajutec)
-
w3c/longtasks
-
1 issue received 2 new comments.
-
Generic model for causal attribution (non-sampling based) w3c/longtasks#89 (2 comments by @npm1, @patrickhulce)
-
Participants
-
1 participant joined.
-
yajun chen (China Mobile Communications Corporation) joined.
-
-
3 participants left.
-
Xing PENG (Baidu, Inc.) left.
-
Li Yin (Baidu, Inc.) left.
-
Siyang Liu (Baidu, Inc.) left.
-
-
1 organization joined.
-
eyeo GmbH joined.
-
GitHub
w3c/event-timing
-
1 issue opened.
-
Support for mousemove and other continuous events w3c/event-timing#99, by @bennym7n.
-
-
1 issue closed.
-
toJSON() shouldn't include target attribute w3c/event-timing#97.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Explain the 16ms minimum durationThreshold w3c/event-timing#98, by @npm1.
-
-
1 pull request received 2 new comments.
w3c/performance-timeline
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Change hasDroppedEntries to droppedEntriesCount w3c/performance-timeline#177, by @npm1.
-
w3c/element-timing
-
1 issue opened.
-
Image rendering stages: finer granularity w3c/element-timing#54, by @jonsneyers.
-
-
2 issues received 5 new comments.
-
Image rendering stages: finer granularity w3c/element-timing#54 (2 comments by @jonsneyers, @jyrkialakuijala)
w3c/resource-timing
-
13 issues opened.
-
WPT Cleanup w3c/resource-timing#254, by @tommckee1.
-
4.6 Integrate the processing model with Fetch w3c/resource-timing#252, by @yoavweiss.
-
4.5.1 "timing allow check" should be called from somewhere and get "the resource" as input w3c/resource-timing#251, by @yoavweiss.
-
4.5 intro includes normative language but is not properly defined w3c/resource-timing#250, by @yoavweiss.
-
"Queue a task to run fire a buffer full event" needs to have a task queue w3c/resource-timing#249, by @yoavweiss.
-
4.3 attribute getters should all be defined as part of the processing model w3c/resource-timing#248, by @yoavweiss.
-
`nextHopProtocol` needs to be defined in terms of Fetch w3c/resource-timing#247, by @yoavweiss.
-
`initiatorType` processing model needs to be defined in terms of Fetch w3c/resource-timing#246, by @yoavweiss.
-
4.3 `startTime` and `duration` should point to the processing model w3c/resource-timing#245, by @yoavweiss.
-
Definition of `name` needs to be more precise w3c/resource-timing#244, by @yoavweiss.
-
Examples in 4.2 are not normative, but look like ones w3c/resource-timing#243, by @yoavweiss.
-
Network aborted resources SHOULD be present (not MAY) w3c/resource-timing#242, by @yoavweiss.
-
Update the editors list w3c/resource-timing#241, by @yoavweiss.
-
-
2 issues closed.
-
Are fetchStart, connectStart, redirectStart relative to navigationStart? w3c/resource-timing#237.
-
Why not consider to add "fetchStart" event? w3c/resource-timing#239.
-
-
8 issues received 12 new comments.
-
transferSize might reveal HttpOnly cookies w3c/resource-timing#238 (2 comments by @Krinkle, @yoavweiss)
-
Are fetchStart, connectStart, redirectStart relative to navigationStart? w3c/resource-timing#237 (2 comments by @Krinkle, @nicjansma)
-
spec what requestStart, responseStart, and responseEnd should represent when service worker is involved w3c/resource-timing#119 (1 comment by @mfalken)
-
Rationalize Resource-Timing opt-ins with CORS/CORP w3c/resource-timing#240 (1 comment by @arturjanc)
-
`nextHopProtocol` needs to be defined in terms of Fetch w3c/resource-timing#247 (1 comment by @yoavweiss)
-
1 pull request opened.
-
Change editors and fixup respec errors w3c/resource-timing#253, by @yoavweiss.
-
w3c/largest-contentful-paint
-
1 issue opened.
-
Refine LCP to take progressive loading into account w3c/largest-contentful-paint#71, by @jonsneyers.
-
-
2 issues closed.
-
"Contentful style-background-images" definition is too vague to be relied upon? w3c/largest-contentful-paint#55.
-
Reward progressive images w3c/largest-contentful-paint#68.
-
-
4 issues received 8 new comments.
-
Reward progressive images w3c/largest-contentful-paint#68 (4 comments by @jonsneyers, @jyrkialakuijala, @mo271)
-
Refine LCP to take progressive loading into account w3c/largest-contentful-paint#71 (2 comments by @csswizardry, @DamonHD)
-
"Contentful style-background-images" definition is too vague to be relied upon? w3c/largest-contentful-paint#55 (1 comment by @npm1)
-
Call back to indicate that the observer is about to stop w3c/largest-contentful-paint#43 (1 comment by @npm1)
-
w3c/longtasks
-
1 issue received 1 new comment.
-
Should LongTasks from same-origin same-event-loop tabs be reported? w3c/longtasks#88 (1 comment by @npm1)
-
w3c/server-timing
-
1 issue opened.
-
Nested hierarchy and grouping of sub-tasks w3c/server-timing#78, by @ibnesayeed.
-
w3c/navigation-timing
-
5 issues opened.
-
4.2 Same origin check should have clear inputs w3c/navigation-timing#137, by @yoavweiss.
-
4.1 Processing model should rely on Fetch/HTML w3c/navigation-timing#136, by @yoavweiss.
-
3.3 Getters should not replicate processing model definitions w3c/navigation-timing#135, by @yoavweiss.
-
3.2 workerTime definition w3c/navigation-timing#134, by @yoavweiss.
-
3.1 duration definition should be done in a single place w3c/navigation-timing#133, by @yoavweiss.
-
-
1 issue closed.
-
a bit confused with the "Redirect" timing in Time Navigation w3c/navigation-timing#132.
-
-
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 @mfalken)
-
a bit confused with the "Redirect" timing in Time Navigation w3c/navigation-timing#132 (1 comment by @nicjansma)
-
w3c/hr-time
-
1 issue opened.
-
WebCodecs Time Stamps w3c/hr-time#104, by @sandersdan.
-
-
1 issue closed.
-
WebCodecs Time Stamps w3c/hr-time#104.
-
-
1 issue received 3 new comments.
w3c/reporting
-
2 issues opened.
-
How to indicate that a report type is not supported w3c/reporting#225, by @clelland.
-
Use Infra types to create JSON w3c/reporting#224, by @annevk.
-