Web Performance Working Group - Activity in 2019
No matches.
TR publications
-
1 document published.
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
GitHub
w3c/performance-timeline
-
2 pull requests opened.
-
chore: fix ReSpec errors w3c/performance-timeline#157, by @sidvishnoi.
-
Remove unused [hr-time] reference. w3c/performance-timeline#156, by @jyasskin.
-
-
2 pull requests merged.
-
chore: fix ReSpec errors w3c/performance-timeline#157.
-
Remove unused [hr-time] reference. w3c/performance-timeline#156.
-
-
1 pull request reopened.
-
chore: fix ReSpec errors w3c/performance-timeline#157, by @marcoscaceres.
-
-
1 pull request received 4 new comments.
-
chore: fix ReSpec errors w3c/performance-timeline#157 (4 comments by @marcoscaceres, @sideshowbarker)
-
w3c/perf-security-privacy
-
1 pull request opened.
-
chore: disable markdown parsing as spec is HTML w3c/perf-security-privacy#6, by @marcoscaceres.
-
-
1 pull request merged.
-
chore: disable markdown parsing as spec is HTML w3c/perf-security-privacy#6.
-
-
1 pull request received 1 new comment.
-
chore: disable markdown parsing as spec is HTML w3c/perf-security-privacy#6 (1 comment by @igrigorik)
-
w3c/largest-contentful-paint
-
1 pull request opened.
-
Add limitation regarding aborts to explainer w3c/largest-contentful-paint#47, by @npm1.
-
-
1 pull request merged.
-
Add limitation regarding aborts to explainer w3c/largest-contentful-paint#47.
-
w3c/hr-time
-
1 pull request opened.
-
chore: remove ReSpec format option, spec uses HTML w3c/hr-time#86, by @marcoscaceres.
-
w3c/server-timing
-
2 issues opened.
-
Creation time of PerformanceServerTiming objects unclear w3c/server-timing#69, by @annevk.
-
Multiple trailer "chunks" each containing server-timing w3c/server-timing#68, by @annevk.
-
-
1 issue received 2 new comments.
-
add start time to distinguish between cached and active entries w3c/server-timing#43 (2 comments by @colinbendell, @hauleth)
-
-
1 pull request opened.
-
chore: update ReSpec syntax and error fixes w3c/server-timing#70, by @sidvishnoi.
-
-
1 pull request received 10 new comments.
-
chore: update ReSpec syntax and error fixes w3c/server-timing#70 (10 comments by @marcoscaceres, @plehegar, @sidvishnoi)
-
w3c/network-error-logging
-
1 pull request opened.
-
chore: switch to fast/lighter ReSpec w3c/network-error-logging#122, by @marcoscaceres.
-
-
1 pull request merged.
-
chore: switch to fast/lighter ReSpec w3c/network-error-logging#122.
-
w3c/timing-entrytypes-registry
-
1 pull request opened.
-
chore: switch to faster/lighter ReSpec w3c/timing-entrytypes-registry#10, by @marcoscaceres.
-
-
1 pull request merged.
-
Fix formatting w3c/timing-entrytypes-registry#9.
-
w3c/reporting
-
1 issue opened.
-
Remove concrete reporting types from Reporting API spec w3c/reporting#189, by @clelland.
-
-
2 issues received 3 new comments.
-
2 pull requests opened.
-
Remove persistent non-document reporting from spec. w3c/reporting#191, by @clelland.
-
Remove concrete reports w3c/reporting#190, by @clelland.
-
-
1 pull request received 1 new comment.
w3c/resource-timing
-
2 issues received 3 new comments.
-
Cross-origin IFRAME opting-in to sharing ResourceTiming data w3c/resource-timing#210 (1 comment by @nicjansma)
w3c/navigation-timing
-
1 pull request opened.
-
fix: add missing brace w3c/navigation-timing#119, by @amio.
-
-
1 pull request merged.
-
fix: add missing brace w3c/navigation-timing#119.
-
-
1 pull request received 1 new comment.
w3c/requestidlecallback
-
1 pull request received 21 new comments.
-
Define algorithm for determining whether high priority work exists. w3c/requestidlecallback#88 (21 comments by @rmcilroy, @rniwa)
-
w3c/longtasks
-
2 issues closed.
-
Reporting work outside of event loop can cause leaks w3c/longtasks#77.
-
The processing model only works for iframes, not object/embed/etc. w3c/longtasks#52.
-
-
2 issues received 10 new comments.
-
Reporting work outside of event loop can cause leaks w3c/longtasks#77 (6 comments by @annevk, @domenic, @npm1)
-
Event loop timing reporting seems to ignore reentrancy w3c/longtasks#76 (4 comments by @annevk, @npm1)
-
-
1 pull request merged.
-
Add attribution for <frame>, <embed>, <object> w3c/longtasks#78.
-
-
1 pull request closed.
-
Add support for <embed> and <object> containerTypes. w3c/longtasks#65.
-
-
1 pull request received 7 new comments.
-
Add attribution for <frame>, <embed>, <object> w3c/longtasks#78 (7 comments by @domenic, @npm1, @tdresser)
-
w3c/beacon
-
1 pull request merged.
-
Add conformance section w3c/beacon#65.
-
TR publications
-
3 documents published.
-
High Resolution Time published as a Recommendation. History of High Resolution Time
-
High Resolution Time Level 2 published as a Recommendation. History of High Resolution Time Level 2
-
Resource Timing Level 2 published as a Working Draft. History of Resource Timing Level 2
-
GitHub
w3c/timing-entrytypes-registry
-
2 pull requests opened.
-
Fix formatting w3c/timing-entrytypes-registry#9, by @npm1.
-
Add longtasks buffering support w3c/timing-entrytypes-registry#8, by @npm1.
-
-
1 pull request merged.
-
Add longtasks buffering support w3c/timing-entrytypes-registry#8.
-
w3c/longtasks
-
3 issues opened.
-
Reporting work outside of event loop can cause leaks w3c/longtasks#77, by @annevk.
-
Event loop timing reporting seems to ignore reentrancy w3c/longtasks#76, by @annevk.
-
Top-level browsing context scoping w3c/longtasks#75, by @annevk.
-
-
3 issues received 9 new comments.
-
Reporting work outside of event loop can cause leaks w3c/longtasks#77 (3 comments by @annevk, @npm1)
-
Event loop timing reporting seems to ignore reentrancy w3c/longtasks#76 (3 comments by @annevk, @npm1)
-
3 pull requests opened.
-
Add attribution for <frame>, <embed>, <object> w3c/longtasks#78, by @npm1.
-
Update spec with buffered flag w3c/longtasks#74, by @npm1.
-
Update explainer with buffered flag support w3c/longtasks#73, by @npm1.
-
-
2 pull requests merged.
-
Update spec with buffered flag w3c/longtasks#74.
-
Update explainer with buffered flag support w3c/longtasks#73.
-
-
2 pull requests received 4 new comments.
w3c/resource-timing
-
1 issue closed.
-
should redirected navigations have a workerStart value if a previous redirect URL was intercepted w3c/resource-timing#118.
-
-
1 issue reopened.
-
should redirected navigations have a workerStart value if a previous redirect URL was intercepted w3c/resource-timing#118, by @yoavweiss.
-
-
2 issues received 8 new comments.
-
Handling of 0-RTT interactions w3c/resource-timing#199 (7 comments by @davidben, @foolip, @Hexcles, @yoavweiss)
-
should redirected navigations have a workerStart value if a previous redirect URL was intercepted w3c/resource-timing#118 (1 comment by @yoavweiss)
-
-
2 pull requests opened.
-
Update timing allow check algorithm w3c/resource-timing#218, by @npm1.
-
Protect workerStart with a TAO check w3c/resource-timing#217, by @yoavweiss.
-
-
1 pull request merged.
-
Protect workerStart with a TAO check w3c/resource-timing#217.
-
-
1 pull request received 10 new comments.
w3c/reporting
-
1 issue received 3 new comments.
-
Switch reporting to Structured Headers w3c/reporting#177 (3 comments by @clelland, @dcreager, @igrigorik)
-
w3c/server-timing
-
2 issues opened.
-
Server Timing can be used a persistent 3rd party identifier w3c/server-timing#67, by @JibberJim.
-
Using Server-timing to carry TraceID w3c/server-timing#65, by @plehegar.
-
-
1 issue closed.
-
Server Timing can be used a persistent 3rd party identifier w3c/server-timing#67.
-
-
3 issues received 12 new comments.
-
Server Timing can be used a persistent 3rd party identifier w3c/server-timing#67 (9 comments by @bripkens, @JibberJim, @mikewest, @yoavweiss)
-
Using Server-timing to carry TraceID w3c/server-timing#65 (2 comments by @SergeyKanzhelev, @yoavweiss)
-
-
1 pull request opened.
-
Add conformance section w3c/server-timing#66, by @tidoust.
-
w3c/network-error-logging
-
3 issues opened.
-
False claim in privacy section w3c/network-error-logging#121, by @MattMenke2.
-
server_ip is likely not defined correctly. w3c/network-error-logging#120, by @MattMenke2.
-
Define HTTP/3 Error Type w3c/network-error-logging#119, by @flano-yuki.
-
-
1 issue received 1 new comment.
w3c/requestidlecallback
-
2 issues opened.
-
timeRemaining() step 4 should define what it means to have a "time-critical task pending" w3c/requestidlecallback#87, by @rniwa.
-
6.2. invoke idle callbacks algorithm step 1 should be defined in terms of task sources having tasks enqueued w3c/requestidlecallback#86, by @rniwa.
-
-
2 issues received 3 new comments.
-
"deadline" in the "start an idle period algorithm" should be defined in terms of event loop w3c/requestidlecallback#71 (2 comments by @rniwa)
-
The order of idle callbacks across windows is inconsistent between spec & UAs w3c/requestidlecallback#82 (1 comment by @rniwa)
-
-
1 pull request opened.
-
Define algorithm for determining whether high priority work exists. w3c/requestidlecallback#88, by @rmcilroy.
-
-
1 pull request merged.
-
Avoid calling start an idle period directly now that the event loop does it w3c/requestidlecallback#85.
-
-
2 pull requests received 3 new comments.
-
Define algorithm for determining whether high priority work exists. w3c/requestidlecallback#88 (2 comments by @rmcilroy, @yoavweiss)
-
Avoid calling start an idle period directly now that the event loop does it w3c/requestidlecallback#85 (1 comment by @rmcilroy)
-
w3c/element-timing
-
2 issues opened.
-
Element Timings and below-the-fold content report arbitrary timings and not useful intersectionRect. w3c/element-timing#42, by @valiantvu.
-
Document status is wrong w3c/element-timing#40, by @yoavweiss.
-
-
1 issue closed.
-
Document status is wrong w3c/element-timing#40.
-
-
1 issue received 3 new comments.
-
Element Timings and below-the-fold content report arbitrary timings and not useful intersectionRect. w3c/element-timing#42 (3 comments by @npm1, @valiantvu)
-
-
1 pull request opened.
-
Change Status to CG-DRAFT w3c/element-timing#41, by @npm1.
-
-
1 pull request merged.
-
Change Status to CG-DRAFT w3c/element-timing#41.
-
w3c/hr-time
-
1 pull request opened.
-
Prep for upcoming w3c/hr-time#85, by @plehegar.
-
-
2 pull requests merged.
-
Prep for upcoming w3c/hr-time#85.
-
Some minor editorial changes w3c/hr-time#82.
-
-
1 pull request received 7 new comments.
w3c/beacon
-
1 pull request opened.
-
Add conformance section w3c/beacon#65, by @tidoust.
-
w3c/user-timing
-
1 issue opened.
-
1 issue received 11 new comments.
-
Allow marks and measures to be shown in developer tooling without adding it to the performance timeline w3c/user-timing#68 (11 comments by @anniesullie, @bgirard, @bvaughn, @npm1, @rniwa, @tdresser)
-
w3c/largest-contentful-paint
-
1 issue opened.
-
Document status is wrong w3c/largest-contentful-paint#45, by @yoavweiss.
-
-
1 issue closed.
-
Document status is wrong w3c/largest-contentful-paint#45.
-
-
1 issue received 2 new comments.
-
2 pull requests opened.
-
Change status to CG DRAFT w3c/largest-contentful-paint#46, by @npm1.
-
Clarification about element removal in explainer w3c/largest-contentful-paint#44, by @npm1.
-
-
2 pull requests merged.
-
Change status to CG DRAFT w3c/largest-contentful-paint#46.
-
Clarification about element removal in explainer w3c/largest-contentful-paint#44.
-
-
1 pull request received 2 new comments.
w3c/event-timing
-
1 issue closed.
-
First Input Delay and first-input event type w3c/event-timing#61.
-
-
2 pull requests opened.
-
Add FID clarification on spec w3c/event-timing#63, by @npm1.
-
Revamp First Input Timing section in explainer w3c/event-timing#62, by @npm1.
-
-
2 pull requests merged.
-
Add FID clarification on spec w3c/event-timing#63.
-
Revamp First Input Timing section in explainer w3c/event-timing#62.
-
-
1 pull request received 6 new comments.
-
Revamp First Input Timing section in explainer w3c/event-timing#62 (6 comments by @anniesullie, @npm1)
-
TR publications
-
2 documents published.
-
High Resolution Time Level 2 published as a Proposed Recommendation. History of High Resolution Time Level 2
-
Performance Timeline Level 2 published as a Working Draft. History of Performance Timeline Level 2
-
GitHub
w3c/requestidlecallback
-
3 issues opened.
-
The invoke idle callbacks algorithm should check if list of runnable idle callbacks is empty or not. w3c/requestidlecallback#83, by @rniwa.
-
The order of idle callbacks across windows is inconsistent between spec & UAs w3c/requestidlecallback#82, by @rniwa.
-
Starting of an idle period algorithm should take origin into account w3c/requestidlecallback#81, by @rniwa.
-
-
2 issues closed.
-
The invoke idle callbacks algorithm should check if list of runnable idle callbacks is empty or not. w3c/requestidlecallback#83.
-
Starting of an idle period algorithm should take origin into account w3c/requestidlecallback#81.
-
-
3 issues received 13 new comments.
-
The order of idle callbacks across windows is inconsistent between spec & UAs w3c/requestidlecallback#82 (7 comments by @annevk, @rmcilroy, @rniwa)
-
Starting of an idle period algorithm should take origin into account w3c/requestidlecallback#81 (4 comments by @annevk, @rniwa)
-
The invoke idle callbacks algorithm should check if list of runnable idle callbacks is empty or not. w3c/requestidlecallback#83 (2 comments by @rmcilroy, @rniwa)
-
-
2 pull requests opened.
-
Avoid calling start an idle period directly now that the event loop does it w3c/requestidlecallback#85, by @rmcilroy.
-
Check if runnable idle callback list is non-empty before popping from it w3c/requestidlecallback#84, by @rmcilroy.
-
-
1 pull request merged.
-
Check if runnable idle callback list is non-empty before popping from it w3c/requestidlecallback#84.
-
w3c/element-timing
-
1 issue opened.
-
Does not work when attribute "elementtiming" has no value w3c/element-timing#37, by @jashsayani.
-
-
2 issues closed.
-
Define a better way to provide 'implicit registration' w3c/element-timing#9.
-
Does not work when attribute "elementtiming" has no value w3c/element-timing#37.
-
-
2 issues received 3 new comments.
-
Does not work when attribute "elementtiming" has no value w3c/element-timing#37 (2 comments by @npm1)
-
-
2 pull requests opened.
-
Explainer: improve definition of text belonging w3c/element-timing#39, by @npm1.
-
Allow just setting the elementtiming attribute w3c/element-timing#38, by @npm1.
-
-
2 pull requests merged.
-
Explainer: improve definition of text belonging w3c/element-timing#39.
-
Allow just setting the elementtiming attribute w3c/element-timing#38.
-
-
2 pull requests received 6 new comments.
-
Explainer: improve definition of text belonging w3c/element-timing#39 (3 comments by @npm1, @yoavweiss)
-
Allow just setting the elementtiming attribute w3c/element-timing#38 (3 comments by @npm1, @yoavweiss)
-
w3c/event-timing
-
2 issues opened.
-
First Input Delay and first-input event type w3c/event-timing#61, by @nicjansma.
-
Add element and/or id fields to PerformanceEventTiming to indicate target of the event w3c/event-timing#60, by @DanShappir.
-
-
1 issue received 2 new comments.
-
Add element and/or id fields to PerformanceEventTiming to indicate target of the event w3c/event-timing#60 (2 comments by @DanShappir, @npm1)
-
-
2 pull requests merged.
-
Remove wrong description of processingStart/End w3c/event-timing#58.
-
Fix description of processingStart/End in spec w3c/event-timing#59.
-
-
2 pull requests received 4 new comments.
w3c/performance-timeline
-
1 issue opened.
-
DOMHighResTimeStamp not found in level2 w3c/performance-timeline#153, by @npm1.
-
-
1 issue closed.
-
DOMHighResTimeStamp not found in level2 w3c/performance-timeline#153.
-
-
1 issue reopened.
-
Ensure tests are clean w3c/performance-timeline#100, by @npm1.
-
-
2 issues received 4 new comments.
-
DOMHighResTimeStamp not found in level2 w3c/performance-timeline#153 (2 comments by @npm1, @plehegar)
-
-
3 pull requests opened.
-
Level2: more ReSpec fixes w3c/performance-timeline#155, by @npm1.
-
chore: fixup some xrefs w3c/performance-timeline#154, by @marcoscaceres.
-
L2 branch: move constructor to a method w3c/performance-timeline#152, by @npm1.
-
-
3 pull requests merged.
-
Level2: more ReSpec fixes w3c/performance-timeline#155.
-
chore: fixup some xrefs w3c/performance-timeline#154.
-
L2 branch: move constructor to a method w3c/performance-timeline#152.
-
-
1 pull request received 2 new comments.
w3c/hr-time
-
1 issue opened.
-
How to cite "timeOrigin" and "now()"? w3c/hr-time#83, by @siusin.
-
-
1 issue closed.
-
How to cite "timeOrigin" and "now()"? w3c/hr-time#83.
-
-
2 pull requests opened.
-
chore: xref fixes w3c/hr-time#84, by @marcoscaceres.
-
Some minor editorial changes w3c/hr-time#82, by @chrisn.
-
-
1 pull request merged.
-
chore: xref fixes w3c/hr-time#84.
-
-
1 pull request received 1 new comment.
w3c/paint-timing
-
1 issue opened.
-
The code example incorrectly mentions observing "long tasks" w3c/paint-timing#46, by @philipwalton.
-
-
1 issue received 2 new comments.
-
The code example incorrectly mentions observing "long tasks" w3c/paint-timing#46 (2 comments by @npm1, @yoavweiss)
-
-
1 pull request opened.
-
Editorial: use camelCase for vars w3c/paint-timing#47, by @npm1.
-
-
1 pull request merged.
-
Editorial: use camelCase for vars w3c/paint-timing#47.
-
w3c/navigation-timing
-
3 issues opened.
-
Add a new entry type for navigations from the BFCache w3c/navigation-timing#118, by @philipwalton.
-
Better integration with ResourceTiming w3c/navigation-timing#117, by @npm1.
-
Can hitting enter on address bar to same URL be considered a navigation of type 'reload'? w3c/navigation-timing#116, by @npm1.
-
-
2 issues received 2 new comments.
-
Definition of "back_forward" navigation type does not make sense w3c/navigation-timing#115 (1 comment by @rniwa)
-
Can hitting enter on address bar to same URL be considered a navigation of type 'reload'? w3c/navigation-timing#116 (1 comment by @rniwa)
-
w3c/reporting
-
1 issue closed.
-
Add toJSON() method to Report and ReportBody w3c/reporting#164.
-
-
1 issue received 19 new comments.
-
Privacy concerns regarding Reporting API w3c/reporting#169 (19 comments by @annevk, @clelland, @dcreager, @mconca, @pes10k, @vdjeric, @yoavweiss)
-
-
1 pull request opened.
-
Remove crash ID references from the explainer w3c/reporting#188, by @jpchase.
-
-
2 pull requests merged.
-
Add toJSON methods to Report and the various ReportBody classes w3c/reporting#187.
-
Remove crash ID references from the explainer w3c/reporting#188.
-
w3c/resource-timing
-
2 issues opened.
-
Use "cross-origin-resource-policy: cross-origin" for timing-allow-origin w3c/resource-timing#216, by @yutakahirano.
-
The step to queue a task to run fire a buffer full event should specify its source w3c/resource-timing#215, by @rniwa.
-
-
2 issues closed.
-
Use "cross-origin-resource-policy: cross-origin" for timing-allow-origin w3c/resource-timing#216.
-
Clarify cross-origin resources w3c/resource-timing#173.
-
-
4 issues received 8 new comments.
-
Use "cross-origin-resource-policy: cross-origin" for timing-allow-origin w3c/resource-timing#216 (5 comments by @annevk, @npm1, @yoavweiss, @yutakahirano)
-
Cross-origin IFRAME opting-in to sharing ResourceTiming data w3c/resource-timing#210 (1 comment by @thebengeu)
-
w3c/longtasks
-
1 issue closed.
-
containerType is confusing w3c/longtasks#61.
-
-
1 pull request opened.
-
Fix containerType for tasks without culprit w3c/longtasks#72, by @npm1.
-
-
1 pull request merged.
-
Fix containerType for tasks without culprit w3c/longtasks#72.
-
-
1 pull request received 1 new comment.
w3c/largest-contentful-paint
-
1 issue opened.
-
Call back to indicate that the observer is about to stop w3c/largest-contentful-paint#43, by @DanShappir.
-
-
1 issue received 2 new comments.
-
Call back to indicate that the observer is about to stop w3c/largest-contentful-paint#43 (2 comments by @DanShappir, @npm1)
-
-
1 pull request opened.
-
Add a content map to handle element removal w3c/largest-contentful-paint#42, by @npm1.
-
-
2 pull requests merged.
-
Add more to introduction w3c/largest-contentful-paint#40.
-
Add a content map to handle element removal w3c/largest-contentful-paint#42.
-
-
2 pull requests received 19 new comments.
-
Add a content map to handle element removal w3c/largest-contentful-paint#42 (18 comments by @npm1, @yoavweiss)
-
TR publications
-
3 documents published.
-
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
-
Performance Timeline Level 2 published as a Working Draft. History of Performance Timeline Level 2
-
GitHub
w3c/reporting
-
3 issues opened.
-
Define a max size for storage w3c/reporting#178, by @hawkinsw.
-
Switch reporting to Structured Headers w3c/reporting#177, by @clelland.
-
Report calls to console-methods like "console.error" w3c/reporting#176, by @nuxodin.
-
-
10 issues closed.
-
"endpoints" is not defined as concept w3c/reporting#165.
-
Relative URLs in endpoints configuration. w3c/reporting#147.
-
Reporting API should be exposed to workers w3c/reporting#131.
-
ReportingObserver::observe() should be Promise-based w3c/reporting#126.
-
Format of dates w3c/reporting#132.
-
Observing reports (via ReportingObserver) cross-frame w3c/reporting#74.
-
Update spec to new IDL syntax for optional dictionaries w3c/reporting#172.
-
Update to constructor operations w3c/reporting#174.
-
No definition found for "serialize json to bytes" w3c/reporting#148.
-
-
12 issues received 37 new comments.
-
Switch reporting to Structured Headers w3c/reporting#177 (9 comments by @clelland, @dcreager, @igrigorik, @mnot)
-
Privacy concerns regarding Reporting API w3c/reporting#169 (7 comments by @annevk, @clelland, @dcreager, @pes10k, @yoavweiss)
-
Relative URLs in endpoints configuration. w3c/reporting#147 (6 comments by @clelland, @igrigorik, @koto, @yoavweiss)
-
Clarify input to HTTP-JFV in "Parse reporting endpoint tuples from _value_" w3c/reporting#12 (1 comment by @clelland)
-
-
9 pull requests opened.
-
Add toJSON methods to Report and the various ReportBody classes w3c/reporting#187, by @clelland.
-
Disallow credentials from cross-origin reports w3c/reporting#186, by @clelland.
-
Fix internal references to 'endpoints' w3c/reporting#185, by @clelland.
-
Allow relative URLs in Report-To configurations w3c/reporting#184, by @clelland.
-
Add processing steps for WebDriver integration. w3c/reporting#183, by @clelland.
-
Expose interfaces on workers as well w3c/reporting#182, by @clelland.
-
Enqueue reports for ReportingObserver asynchronously w3c/reporting#181, by @clelland.
-
Update for recent WebIDL changes w3c/reporting#180, by @clelland.
-
editorial: use new IDL constructor syntax w3c/reporting#179, by @marcoscaceres.
-
-
8 pull requests merged.
-
Fix internal references to 'endpoints' w3c/reporting#185.
-
Allow relative URLs in Report-To configurations w3c/reporting#184.
-
Add processing steps for WebDriver integration. w3c/reporting#183.
-
Expose interfaces on workers as well w3c/reporting#182.
-
Enqueue reports for ReportingObserver asynchronously w3c/reporting#181.
-
Add explicit [Exposed] w3c/reporting#173.
-
editorial: use new IDL constructor syntax w3c/reporting#179.
-
Update the editors. w3c/reporting#175.
-
-
2 pull requests closed.
-
Add explicit [Exposed] + dictionary default value w3c/reporting#171.
-
Update for recent WebIDL changes w3c/reporting#180.
-
-
3 pull requests received 3 new comments.
w3c/resource-timing
-
2 issues closed.
-
Should 404 codes be considered aborts? w3c/resource-timing#165.
-
Clarify that TAO needs to be set even on same origin resource after cross-origin redirects w3c/resource-timing#207.
-
-
3 issues received 5 new comments.
-
Should 404 codes be considered aborts? w3c/resource-timing#165 (3 comments by @mikesalvia, @yoavweiss)
-
Cross-origin IFRAME opting-in to sharing ResourceTiming data w3c/resource-timing#210 (1 comment by @npm1)
-
Be a bit more explicit about which subresources are to be ignored from stylesheets w3c/resource-timing#200 (1 comment by @yoavweiss)
-
-
1 pull request opened.
-
Align TAO processing with CORS w3c/resource-timing#214, by @yoavweiss.
-
-
1 pull request merged.
-
Align TAO processing with CORS w3c/resource-timing#214.
-
-
1 pull request received 2 new comments.
w3c/user-timing
-
1 pull request opened.
-
[user-timing-2] Align with Web IDL specification w3c/user-timing#67, by @autokagami.
-
-
1 pull request merged.
-
[user-timing-2] Align with Web IDL specification w3c/user-timing#67.
-
-
1 pull request received 1 new comment.
w3c/navigation-timing
-
2 issues received 14 new comments.
-
Definition of "back_forward" navigation type does not make sense w3c/navigation-timing#115 (12 comments by @bzbarsky, @igrigorik, @nicjansma, @philipwalton, @yoavweiss)
-
Spec for PerformanceNavigationTiming.type does not match any implementations w3c/navigation-timing#114 (2 comments by @bzbarsky, @yoavweiss)
-
w3c/network-error-logging
-
1 issue opened.
-
One origin can set a policy for a different origin w3c/network-error-logging#117, by @zcorpan.
-
-
1 issue received 2 new comments.
-
One origin can set a policy for a different origin w3c/network-error-logging#117 (2 comments by @dcreager, @zcorpan)
-
-
1 pull request opened.
-
Editorial: fix some ReSpec issues w3c/network-error-logging#118, by @marcoscaceres.
-
-
1 pull request merged.
-
Update the editors. w3c/network-error-logging#116.
-
-
1 pull request received 3 new comments.
w3c/event-timing
-
3 issues opened.
-
Set baseline of 100ms for duration w3c/event-timing#57, by @hawkinsw.
-
Should Section 2.2 reference 'considered for Event Timing' w3c/event-timing#56, by @hawkinsw.
-
Alternate semantics for processingStart w3c/event-timing#55, by @hawkinsw.
-
-
1 issue closed.
-
Set baseline of 100ms for duration w3c/event-timing#57.
-
-
2 issues received 12 new comments.
-
Alternate semantics for processingStart w3c/event-timing#55 (9 comments by @hawkinsw, @npm1, @tdresser)
-
-
2 pull requests opened.
-
Fix description of processingStart/End in spec w3c/event-timing#59, by @npm1.
-
Remove wrong description of processingStart/End w3c/event-timing#58, by @npm1.
-
-
1 pull request received 4 new comments.
w3c/hr-time
-
1 issue received 4 new comments.
-
Reducing the precision of the DOMHighResTimeStamp resolution w3c/hr-time#56 (4 comments by @dakom, @yoavweiss)
-
w3c/longtasks
-
1 issue received 1 new comment.
w3c/performance-timeline
-
1 issue closed.
-
Update to constructor operations w3c/performance-timeline#150.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
editorial: fix ReSpec warnings w3c/performance-timeline#151, by @marcoscaceres.
-
-
1 pull request merged.
-
editorial: fix ReSpec warnings w3c/performance-timeline#151.
-
w3c/device-memory
-
1 issue received 1 new comment.
-
Expose CPU clock speed and GPU info in the same manner as device memory w3c/device-memory#15 (1 comment by @yoavweiss)
-
w3c/web-performance
-
1 issue opened.
-
Performance considerations for spec developers? w3c/web-performance#28, by @Malvoz.
-
-
1 issue received 1 new comment.
TR publications
-
1 document published.
-
User Timing Level 3 published as a Working Draft. History of User Timing Level 3
-
GitHub
w3c/network-error-logging
-
1 issue received 3 new comments.
-
Disambiguate definitions w3c/network-error-logging#115 (3 comments by @clelland, @igrigorik, @jyasskin)
-
-
1 pull request opened.
-
Update the editors. w3c/network-error-logging#116, by @jyasskin.
-
-
1 pull request received 4 new comments.
w3c/reporting
-
2 issues opened.
-
Update to constructor operations w3c/reporting#174, by @Ms2ger.
-
Update spec to new IDL syntax for optional dictionaries w3c/reporting#172, by @Ms2ger.
-
-
1 issue received 10 new comments.
-
Feedback from Mozilla w3c/reporting#158 (10 comments by @annevk, @clelland, @dcreager, @igrigorik, @martinthomson)
-
-
3 pull requests opened.
-
Update the editors. w3c/reporting#175, by @jyasskin.
-
Add explicit [Exposed] w3c/reporting#173, by @saschanaz.
-
Add explicit [Exposed] + dictionary default value w3c/reporting#171, by @saschanaz.
-
-
2 pull requests received 3 new comments.
w3c/device-memory
-
1 issue opened.
-
Apple's WebKit team's feedback w3c/device-memory#24, by @rniwa.
-
w3c/largest-contentful-paint
-
3 issues opened.
-
Investigate element removal w3c/largest-contentful-paint#41, by @npm1.
-
Separation between LCP and Paint Timing is confusing from a user perspective w3c/largest-contentful-paint#36, by @andydavies.
-
Explainer incorrectly claims LCP reports the visual size of images w3c/largest-contentful-paint#35, by @philipwalton.
-
-
1 issue closed.
-
Explainer incorrectly claims LCP reports the visual size of images w3c/largest-contentful-paint#35.
-
-
2 issues received 5 new comments.
-
Separation between LCP and Paint Timing is confusing from a user perspective w3c/largest-contentful-paint#36 (3 comments by @andydavies, @npm1)
-
LargestContentfulPaint is difficult to efficiently implement w3c/largest-contentful-paint#31 (2 comments by @maxlgu, @npm1)
-
-
4 pull requests opened.
-
Add more to introduction w3c/largest-contentful-paint#40, by @npm1.
-
Add explicit [Exposed] w3c/largest-contentful-paint#39, by @saschanaz.
-
Add intrinsic size section w3c/largest-contentful-paint#38, by @npm1.
-
Penalize stretched images w3c/largest-contentful-paint#37, by @npm1.
-
-
3 pull requests merged.
-
Add explicit [Exposed] w3c/largest-contentful-paint#39.
-
Add intrinsic size section w3c/largest-contentful-paint#38.
-
Penalize stretched images w3c/largest-contentful-paint#37.
-
-
3 pull requests received 12 new comments.
w3c/performance-timeline
-
1 issue opened.
-
Update to constructor operations w3c/performance-timeline#150, by @Ms2ger.
-
-
2 pull requests opened.
-
Add buffered flag explanation in Introduction w3c/performance-timeline#148, by @npm1.
-
2 pull requests merged.
-
Fix links w3c/performance-timeline#149.
-
Add buffered flag explanation in Introduction w3c/performance-timeline#148.
-
-
1 pull request received 5 new comments.
-
Add buffered flag explanation in Introduction w3c/performance-timeline#148 (5 comments by @igrigorik, @npm1)
-
w3c/element-timing
-
5 issues opened.
-
Number of PerformanceElementTiming entries for background-image that contains multiple layers w3c/element-timing#35, by @hawkinsw.
-
Text nodes do not have a "border box" w3c/element-timing#33, by @bzbarsky.
-
<video> elements are not listed in the "Elements exposed" section w3c/element-timing#32, by @philipwalton.
-
Report image Element Timing algorithm doesn't report intrinsic size for LCP w3c/element-timing#31, by @philipwalton.
-
Specify the mapping of containing block to element w3c/element-timing#30, by @hawkinsw.
-
-
4 issues closed.
-
Wait for image to be decoded for renderTime w3c/element-timing#28.
-
<video> elements are not listed in the "Elements exposed" section w3c/element-timing#32.
-
Improve definition of "associated element" w3c/element-timing#8.
-
Should text and image have different entryType w3c/element-timing#4.
-
-
7 issues received 30 new comments.
-
Wait for image to be decoded for renderTime w3c/element-timing#28 (14 comments by @hawkinsw, @npm1, @yoavweiss)
-
Number of PerformanceElementTiming entries for background-image that contains multiple layers w3c/element-timing#35 (5 comments by @hawkinsw, @npm1)
-
Specify the mapping of containing block to element w3c/element-timing#30 (4 comments by @bzbarsky, @npm1)
-
Report image Element Timing algorithm doesn't report intrinsic size for LCP w3c/element-timing#31 (2 comments by @npm1, @philipwalton)
-
-
3 pull requests opened.
-
Wait for image to be decoded for images pending rendering w3c/element-timing#36, by @npm1.
-
Add poster of video to Elements Exposed w3c/element-timing#34, by @npm1.
-
Suggested changes w3c/element-timing#29, by @hawkinsw.
-
-
3 pull requests merged.
-
Wait for image to be decoded for images pending rendering w3c/element-timing#36.
-
Add poster of video to Elements Exposed w3c/element-timing#34.
-
Suggested changes w3c/element-timing#29.
-
-
2 pull requests received 5 new comments.
-
Wait for image to be decoded for images pending rendering w3c/element-timing#36 (2 comments by @hawkinsw, @npm1)
w3c/requestidlecallback
-
1 issue closed.
-
The timeRemaining language is confusing w3c/requestidlecallback#77.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Add default dictionary value w3c/requestidlecallback#80, by @saschanaz.
-
-
1 pull request merged.
-
Add default dictionary value w3c/requestidlecallback#80.
-
-
1 pull request received 2 new comments.
w3c/server-timing
-
1 issue opened.
-
Support in the Firefox DevTools? w3c/server-timing#64, by @SilentImp.
-
-
1 issue closed.
-
Support in the Firefox DevTools? w3c/server-timing#64.
-
-
1 issue received 2 new comments.
w3c/paint-timing
-
2 issues opened.
-
Add attribution information about what triggers paint w3c/paint-timing#44, by @npm1.
-
LargestContentfulPaint and PaintTiming are separate specs w3c/paint-timing#43, by @andydavies.
-
-
1 issue received 3 new comments.
-
LargestContentfulPaint and PaintTiming are separate specs w3c/paint-timing#43 (3 comments by @npm1, @yoavweiss)
-
-
1 pull request opened.
-
Add explicit [Exposed] w3c/paint-timing#45, by @saschanaz.
-
-
1 pull request merged.
-
Add explicit [Exposed] w3c/paint-timing#45.
-
w3c/longtasks
-
1 issue closed.
-
supported entry types needs to be context aware w3c/longtasks#57.
-
-
4 issues received 5 new comments.
-
supported entry types needs to be context aware w3c/longtasks#57 (2 comments by @toddreifsteck, @yoavweiss)
-
Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? w3c/longtasks#41 (1 comment by @toddreifsteck)
-
-
1 pull request opened.
-
Add explicit [Exposed] w3c/longtasks#71, by @saschanaz.
-
-
1 pull request merged.
-
Add explicit [Exposed] w3c/longtasks#71.
-
w3c/user-timing
-
1 pull request merged.
-
Giving markOptions a default value for IDL conformance. w3c/user-timing#66.
-
-
1 pull request received 1 new comment.
-
Giving markOptions a default value for IDL conformance. w3c/user-timing#66 (1 comment by @tommckee1)
-
w3c/hr-time
-
1 issue opened.
-
Time origin of event timestamps across iframes w3c/hr-time#81, by @querymetrics.
-
-
1 issue closed.
-
Time origin of event timestamps across iframes w3c/hr-time#81.
-
-
1 issue received 3 new comments.
-
Time origin of event timestamps across iframes w3c/hr-time#81 (3 comments by @rniwa, @toddreifsteck)
-
w3c/resource-timing
-
2 issues received 2 new comments.
-
Clarify that TAO needs to be set even on same origin resource after cross-origin redirects w3c/resource-timing#207 (1 comment by @toddreifsteck)
-
Be a bit more explicit about which subresources are to be ignored from stylesheets w3c/resource-timing#200 (1 comment by @toddreifsteck)
-
w3c/navigation-timing
-
1 issue received 1 new comment.
-
Spec for PerformanceNavigationTiming.type does not match any implementations w3c/navigation-timing#114 (1 comment by @toddreifsteck)
-
TR publications
-
4 documents published.
-
User Timing Level 3 published as a Working Draft. History of User Timing Level 3
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Resource Hints published as a Working Draft. History of Resource Hints
-
Timing Entry Names Registry published as a First Public Working Draft. History of Timing Entry Names Registry
-
Participants
-
1 organization left.
-
Orange left.
-
GitHub
w3c/element-timing
-
4 issues opened.
-
Wait for image to be decoded for renderTime w3c/element-timing#28, by @hawkinsw.
-
PerformanceElementTiming keeps its Element alive w3c/element-timing#21, by @foolip.
-
Definition of `identifier` and `id` IDL attributes don't match Chromium w3c/element-timing#20, by @foolip.
-
The "elementtiming" attribute + "smaller than 15% of the viewport size" check appears wrong w3c/element-timing#18, by @foolip.
-
-
3 issues closed.
-
PerformanceElementTiming keeps its Element alive w3c/element-timing#21.
-
Definition of `identifier` and `id` IDL attributes don't match Chromium w3c/element-timing#20.
-
The "elementtiming" attribute + "smaller than 15% of the viewport size" check appears wrong w3c/element-timing#18.
-
-
4 issues received 11 new comments.
-
PerformanceElementTiming keeps its Element alive w3c/element-timing#21 (5 comments by @domenic, @foolip, @npm1, @yoavweiss)
-
How should Element Timing interact with Shadow DOM? w3c/element-timing#3 (2 comments by @foolip, @npm1)
-
The "elementtiming" attribute + "smaller than 15% of the viewport size" check appears wrong w3c/element-timing#18 (2 comments by @foolip, @npm1)
-
Definition of `identifier` and `id` IDL attributes don't match Chromium w3c/element-timing#20 (2 comments by @foolip, @npm1)
-
-
10 pull requests opened.
-
Set startTime to the either renderTime or loadTime w3c/element-timing#27, by @yoavweiss.
-
Fix the naming/URL of the call to LCP w3c/element-timing#26, by @foolip.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/element-timing#25, by @foolip.
-
Add fully active check w3c/element-timing#24, by @npm1.
-
Remove responseEnd section w3c/element-timing#23, by @npm1.
-
Set identifier and id on entry creation w3c/element-timing#22, by @npm1.
-
Define `elementTiming` as reflecting "elementtiming" w3c/element-timing#19, by @foolip.
-
Add loadTime to potentially-add-LCP w3c/element-timing#17, by @npm1.
-
Update spec to use loadTime w3c/element-timing#16, by @npm1.
-
Set rendering timestamp in renderTime w3c/element-timing#15, by @npm1.
-
-
11 pull requests merged.
-
Set startTime to the either renderTime or loadTime w3c/element-timing#27.
-
Add loadTime to potentially-add-LCP w3c/element-timing#17.
-
Fix the naming/URL of the call to LCP w3c/element-timing#26.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/element-timing#25.
-
Add fully active check w3c/element-timing#24.
-
Remove responseEnd section w3c/element-timing#23.
-
Set identifier and id on entry creation w3c/element-timing#22.
-
Define `elementTiming` as reflecting "elementtiming" w3c/element-timing#19.
-
Update spec to use loadTime w3c/element-timing#16.
-
Set rendering timestamp in renderTime w3c/element-timing#15.
-
Add support for data URL images w3c/element-timing#14.
-
-
5 pull requests received 33 new comments.
w3c/timing-entrytypes-registry
-
2 issues opened.
-
"Deprecate" rather than "delete" entries w3c/timing-entrytypes-registry#6, by @swickr.
-
registry stability w3c/timing-entrytypes-registry#5, by @dret.
-
-
2 pull requests opened.
-
Add more entryTypes to the registry w3c/timing-entrytypes-registry#4, by @npm1.
-
Correct maxBufferSize for PaintTiming w3c/timing-entrytypes-registry#3, by @npm1.
-
-
2 pull requests merged.
-
Add more entryTypes to the registry w3c/timing-entrytypes-registry#4.
-
Correct maxBufferSize for PaintTiming w3c/timing-entrytypes-registry#3.
-
-
1 pull request received 2 new comments.
-
Add more entryTypes to the registry w3c/timing-entrytypes-registry#4 (2 comments by @npm1, @yoavweiss)
-
w3c/largest-contentful-paint
-
15 issues opened.
-
LargestContentfulPaint is difficult to efficiently implement w3c/largest-contentful-paint#31, by @progers.
-
Should script-created events set the "has dispatched scroll event" flag? w3c/largest-contentful-paint#30, by @foolip.
-
LargestContentfulPaint keeps its Element alive w3c/largest-contentful-paint#29, by @foolip.
-
Background purposed images is not properly defined in the spec w3c/largest-contentful-paint#28, by @yoavweiss.
-
Explainer should define which events are included in user input, not which ones are not w3c/largest-contentful-paint#27, by @yoavweiss.
-
Frame viewport clipping is not properly specified w3c/largest-contentful-paint#26, by @yoavweiss.
-
Setup PR preview w3c/largest-contentful-paint#24, by @yoavweiss.
-
Rules and heuristics from explainer missing from spec w3c/largest-contentful-paint#21, by @foolip.
-
Where does the request come from? w3c/largest-contentful-paint#20, by @foolip.
-
What is the id attribute for? w3c/largest-contentful-paint#19, by @foolip.
-
Modifications to the DOM specification look like they won't work w3c/largest-contentful-paint#18, by @foolip.
-
"potentially add a LargestContentfulPaint entry" is never invoked w3c/largest-contentful-paint#17, by @foolip.
-
Can LargestContentfulPaint's element attribute be null? w3c/largest-contentful-paint#16, by @foolip.
-
Reset LCP for Single Page App soft navigations w3c/largest-contentful-paint#6, by @nicjansma.
-
Stop computations upon user input w3c/largest-contentful-paint#5, by @npm1.
-
-
11 issues closed.
-
Should script-created events set the "has dispatched scroll event" flag? w3c/largest-contentful-paint#30.
-
LargestContentfulPaint keeps its Element alive w3c/largest-contentful-paint#29.
-
What is the id attribute for? w3c/largest-contentful-paint#19.
-
Can LargestContentfulPaint's element attribute be null? w3c/largest-contentful-paint#16.
-
Rules and heuristics from explainer missing from spec w3c/largest-contentful-paint#21.
-
"potentially add a LargestContentfulPaint entry" is never invoked w3c/largest-contentful-paint#17.
-
Setup PR preview w3c/largest-contentful-paint#24.
-
Any polyfill could be used currently? w3c/largest-contentful-paint#1.
-
Where does the request come from? w3c/largest-contentful-paint#20.
-
Modifications to the DOM specification look like they won't work w3c/largest-contentful-paint#18.
-
Stop computations upon user input w3c/largest-contentful-paint#5.
-
-
1 issue reopened.
-
Can LargestContentfulPaint's element attribute be null? w3c/largest-contentful-paint#16, by @npm1.
-
-
12 issues received 49 new comments.
-
LargestContentfulPaint is difficult to efficiently implement w3c/largest-contentful-paint#31 (11 comments by @chrishtr, @npm1, @progers)
-
"potentially add a LargestContentfulPaint entry" is never invoked w3c/largest-contentful-paint#17 (9 comments by @foolip, @npm1, @yoavweiss)
-
Can LargestContentfulPaint's element attribute be null? w3c/largest-contentful-paint#16 (5 comments by @foolip, @npm1)
-
Modifications to the DOM specification look like they won't work w3c/largest-contentful-paint#18 (4 comments by @foolip, @npm1, @yoavweiss)
-
Rules and heuristics from explainer missing from spec w3c/largest-contentful-paint#21 (3 comments by @foolip, @yoavweiss)
-
Reset LCP for Single Page App soft navigations w3c/largest-contentful-paint#6 (3 comments by @nicjansma, @npm1, @yoavweiss)
-
Where does the request come from? w3c/largest-contentful-paint#20 (3 comments by @foolip, @yoavweiss)
-
Should script-created events set the "has dispatched scroll event" flag? w3c/largest-contentful-paint#30 (2 comments by @foolip, @npm1)
-
LargestContentfulPaint keeps its Element alive w3c/largest-contentful-paint#29 (1 comment by @yoavweiss)
-
-
17 pull requests opened.
-
Set startTime to the either renderTime or loadTime w3c/largest-contentful-paint#34, by @yoavweiss.
-
Only take trusted scroll events into account w3c/largest-contentful-paint#33, by @yoavweiss.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/largest-contentful-paint#32, by @foolip.
-
Add PR preview w3c/largest-contentful-paint#25, by @yoavweiss.
-
Reference target's relevant global object w3c/largest-contentful-paint#23, by @yoavweiss.
-
Handle the case of a null Request w3c/largest-contentful-paint#22, by @yoavweiss.
-
Fix Bikeshed markup of request's URL w3c/largest-contentful-paint#15, by @foolip.
-
Tweak wording on LCP limitations w3c/largest-contentful-paint#14, by @foolip.
-
Add missing word "avoid" w3c/largest-contentful-paint#13, by @foolip.
-
Remove extra `)` trailing link w3c/largest-contentful-paint#12, by @foolip.
-
Fix typo "as describe" w3c/largest-contentful-paint#11, by @foolip.
-
Replace responseEnd with loadTime w3c/largest-contentful-paint#10, by @npm1.
-
Improve JS snippet in explainer, add loadTime w3c/largest-contentful-paint#9, by @npm1.
-
Stop measuring LCP at first scroll or input event w3c/largest-contentful-paint#8, by @yoavweiss.
-
Change rendering timestamp to renderTime w3c/largest-contentful-paint#7, by @npm1.
-
Naming updates in index.bs w3c/largest-contentful-paint#4, by @npm1.
-
Name fixes in README w3c/largest-contentful-paint#3, by @npm1.
-
-
16 pull requests merged.
-
Set startTime to the either renderTime or loadTime w3c/largest-contentful-paint#34.
-
Only take trusted scroll events into account w3c/largest-contentful-paint#33.
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/largest-contentful-paint#32.
-
Add PR preview w3c/largest-contentful-paint#25.
-
Handle the case of a null Request w3c/largest-contentful-paint#22.
-
Reference target's relevant global object w3c/largest-contentful-paint#23.
-
Remove extra `)` trailing link w3c/largest-contentful-paint#12.
-
Fix typo "as describe" w3c/largest-contentful-paint#11.
-
Tweak wording on LCP limitations w3c/largest-contentful-paint#14.
-
Add missing word "avoid" w3c/largest-contentful-paint#13.
-
Improve JS snippet in explainer, add loadTime w3c/largest-contentful-paint#9.
-
Replace responseEnd with loadTime w3c/largest-contentful-paint#10.
-
Stop measuring LCP at first scroll or input event w3c/largest-contentful-paint#8.
-
Change rendering timestamp to renderTime w3c/largest-contentful-paint#7.
-
Naming updates in index.bs w3c/largest-contentful-paint#4.
-
Name fixes in README w3c/largest-contentful-paint#3.
-
-
1 pull request closed.
-
Fix Bikeshed markup of request's URL w3c/largest-contentful-paint#15.
-
-
6 pull requests received 12 new comments.
-
Fix Bikeshed markup of request's URL w3c/largest-contentful-paint#15 (4 comments by @foolip, @yoavweiss)
-
Stop measuring LCP at first scroll or input event w3c/largest-contentful-paint#8 (3 comments by @npm1, @yoavweiss)
-
Reference target's relevant global object w3c/largest-contentful-paint#23 (2 comments by @foolip, @npm1)
-
Ask for tests for normative changes in CONTRIBUTING.md w3c/largest-contentful-paint#32 (1 comment by @foolip)
-
w3c/performance-timeline
-
1 issue opened.
-
`buffered: true` not adding entries to PerformanceObserver's buffer w3c/performance-timeline#145, by @hsm2.
-
-
4 issues closed.
-
`buffered: true` not adding entries to PerformanceObserver's buffer w3c/performance-timeline#145.
-
How does "queue a PerformanceEntry" algorithm interact with other specs? w3c/performance-timeline#128.
-
"relevant performance entry tuple" usage is still broken w3c/performance-timeline#130.
-
buffered flag should not be removed from PerformanceObserverInit w3c/performance-timeline#139.
-
-
4 issues received 5 new comments.
-
`buffered: true` not adding entries to PerformanceObserver's buffer w3c/performance-timeline#145 (2 comments by @npm1, @tdresser)
-
How does "queue a PerformanceEntry" algorithm interact with other specs? w3c/performance-timeline#128 (1 comment by @npm1)
-
"relevant performance entry tuple" usage is still broken w3c/performance-timeline#130 (1 comment by @bzbarsky)
-
buffered flag should not be removed from PerformanceObserverInit w3c/performance-timeline#139 (1 comment by @npm1)
-
-
7 pull requests opened.
-
Add default value to observe() parameter w3c/performance-timeline#147, by @npm1.
-
Give optional dictionary a default value of {} w3c/performance-timeline#146, by @dsanders11.
-
Fix input ordering w3c/performance-timeline#144, by @npm1.
-
Add a basic explainer w3c/performance-timeline#143, by @npm1.
-
Fix relevant performance entry tuple usage w3c/performance-timeline#142, by @npm1.
-
Fix link to availableFromTimeline w3c/performance-timeline#141, by @npm1.
-
Revert deletion of buffered flag w3c/performance-timeline#140, by @npm1.
-
-
6 pull requests merged.
-
Add default value to observe() parameter w3c/performance-timeline#147.
-
Fix input ordering w3c/performance-timeline#144.
-
Add a basic explainer w3c/performance-timeline#143.
-
Fix link to availableFromTimeline w3c/performance-timeline#141.
-
Fix relevant performance entry tuple usage w3c/performance-timeline#142.
-
Revert deletion of buffered flag w3c/performance-timeline#140.
-
-
2 pull requests closed.
-
Give optional dictionary a default value of {} w3c/performance-timeline#146.
-
More fixes w3c/performance-timeline#137.
-
-
5 pull requests received 8 new comments.
-
Add default value to observe() parameter w3c/performance-timeline#147 (2 comments by @npm1, @yoavweiss)
-
Give optional dictionary a default value of {} w3c/performance-timeline#146 (1 comment by @yoavweiss)
-
w3c/navigation-timing
-
2 issues opened.
-
Definition of "back_forward" navigation type does not make sense w3c/navigation-timing#115, by @bzbarsky.
-
Spec for PerformanceNavigationTiming.type does not match any implementations w3c/navigation-timing#114, by @bzbarsky.
-
-
1 issue closed.
-
secureConnectionStart definition is inconsistent with ResourceTiming w3c/navigation-timing#84.
-
-
2 issues received 4 new comments.
-
Spec for PerformanceNavigationTiming.type does not match any implementations w3c/navigation-timing#114 (3 comments by @bzbarsky, @hawkinsw)
-
Definition of "back_forward" navigation type does not make sense w3c/navigation-timing#115 (1 comment by @bzbarsky)
-
-
1 pull request merged.
-
Avoid redefining secureConnectionStart w3c/navigation-timing#106.
-
-
1 pull request closed.
-
Fold the secureConnectionStart processing to ResourceTiming's processing w3c/navigation-timing#92.
-
-
2 pull requests received 5 new comments.
-
Fold the secureConnectionStart processing to ResourceTiming's processing w3c/navigation-timing#92 (1 comment by @yoavweiss)
w3c/reporting
-
6 issues opened.
-
Privacy concerns regarding Reporting API w3c/reporting#169, by @pes10k.
-
Reporting API should be opt-in w3c/reporting#168, by @pes10k.
-
Remove "nel" example from standard text w3c/reporting#167, by @pes10k.
-
Clarify behavior of duplicate endpoint URLs w3c/reporting#166, by @sburnett.
-
"endpoints" is not defined as concept w3c/reporting#165, by @annevk.
-
Add toJSON() method to Report and ReportBody w3c/reporting#164, by @chrisguttandin.
-
-
1 issue closed.
-
Testing ReportingObserver in web platform tests. w3c/reporting#71.
-
-
8 issues received 24 new comments.
-
Disallow include_subdomains from eTLDs w3c/reporting#159 (6 comments by @chlily1, @clelland, @igrigorik, @mikewest, @sburnett)
-
Privacy concerns regarding Reporting API w3c/reporting#169 (5 comments by @igrigorik, @pes10k, @yoavweiss)
-
Testing ReportingObserver in web platform tests. w3c/reporting#71 (2 comments by @clelland, @jpchase)
-
-
1 pull request opened.
-
Remove include_subdomains flag and associated machinery w3c/reporting#170, by @clelland.
-
-
2 pull requests received 3 new comments.
-
Remove include_subdomains flag and associated machinery w3c/reporting#170 (2 comments by @dcreager, @igrigorik)
-
w3c/event-timing
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Change the entryType of first input entries w3c/event-timing#54, by @npm1.
-
-
1 pull request merged.
-
Change the entryType of first input entries w3c/event-timing#54.
-
w3c/web-performance
-
1 pull request opened.
-
Updated HAR Overview.html stylesheet to HTTPS w3c/web-performance#27, by @tompazourek.
-
-
1 pull request merged.
-
Updated HAR Overview.html stylesheet to HTTPS w3c/web-performance#27.
-
w3c/hr-time
-
2 issues opened.
-
Security and privacy considerations for DOMHighResTimeStamp resolution w3c/hr-time#79, by @igrigorik.
-
Use section/headings for attributes and methods w3c/hr-time#77, by @marcoscaceres.
-
-
2 issues closed.
-
Use section/headings for attributes and methods w3c/hr-time#77.
-
ReSpec errors w3c/hr-time#76.
-
-
3 issues received 21 new comments.
-
Privacy (PING) review w3c/hr-time#20 (13 comments by @hober, @igrigorik, @pes10k, @rniwa, @samuelweiler, @tildelowengrimm, @yoavweiss)
-
Security and privacy considerations for DOMHighResTimeStamp resolution w3c/hr-time#79 (7 comments by @igrigorik, @pes10k, @samuelweiler, @tildelowengrimm, @yoavweiss)
-
-
2 pull requests opened.
-
update clock resolution recommendation + reference w3c/hr-time#80, by @igrigorik.
-
Editorial: add headings/sections w3c/hr-time#78, by @marcoscaceres.
-
-
2 pull requests merged.
-
update clock resolution recommendation + reference w3c/hr-time#80.
-
Editorial: add headings/sections w3c/hr-time#78.
-
-
2 pull requests received 9 new comments.
-
update clock resolution recommendation + reference w3c/hr-time#80 (8 comments by @igrigorik, @yoavweiss)
-
w3c/user-timing
-
2 pull requests opened.
-
Giving markOptions a default value for IDL conformance. w3c/user-timing#66, by @tommckee1.
-
Giving startOrOptions a default value for IDL conformance. w3c/user-timing#65, by @tommckee1.
-
-
1 pull request merged.
-
Giving startOrOptions a default value for IDL conformance. w3c/user-timing#65.
-
-
1 pull request received 8 new comments.
-
Giving startOrOptions a default value for IDL conformance. w3c/user-timing#65 (8 comments by @marcoscaceres, @npm1, @tommckee1)
-
w3c/longtasks
-
3 issues received 14 new comments.
-
containerSrc could be long (a data URI) w3c/longtasks#64 (7 comments by @hawkinsw, @npm1, @rniwa, @toddreifsteck, @yoavweiss)
-
Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? w3c/longtasks#41 (6 comments by @nicjansma, @npm1, @philipwalton)
-
-
1 pull request opened.
-
Suggest some readability updates to the intro paragraphs. w3c/longtasks#70, by @hawkinsw.
-
-
1 pull request merged.
-
Suggest some readability updates to the intro paragraphs. w3c/longtasks#70.
-
-
1 pull request closed.
-
Suggest some readability updates to the intro paragraphs. w3c/longtasks#69.
-
-
2 pull requests received 8 new comments.
-
Suggest some readability updates to the intro paragraphs. w3c/longtasks#69 (7 comments by @hawkinsw, @npm1)
-
w3c/requestidlecallback
-
1 pull request merged.
-
Clarify timeRemaining() algorithm. w3c/requestidlecallback#79.
-
w3c/network-error-logging
-
1 issue opened.
-
Disambiguate definitions w3c/network-error-logging#115, by @jyasskin.
-
TR publications
-
12 documents published.
-
High Resolution Time Level 2 published as a Candidate Recommendation Snapshot. History of High Resolution Time Level 2
-
Preload published as a Candidate Recommendation Snapshot. History of Preload
-
User Timing Level 3 published 4 times as a Working Draft. History of User Timing Level 3
-
Navigation Timing Level 2 published twice as a Working Draft. History of Navigation Timing Level 2
-
Resource Hints published as a Working Draft. History of Resource Hints
-
Performance Timeline Level 2 published as a Working Draft. History of Performance Timeline Level 2
-
Resource Timing Level 2 published twice as a Working Draft. History of Resource Timing Level 2
-
Participants
-
1 participant joined.
-
Philippe Le Hegaret (W3C) joined.
-
GitHub
w3c/hr-time
-
1 issue opened.
-
ReSpec errors w3c/hr-time#76, by @npm1.
-
-
2 issues received 2 new comments.
-
4 pull requests opened.
-
chore(travis): use https for w3c manifest w3c/hr-time#75, by @marcoscaceres.
-
chore(travis): use https for w3c manifest w3c/hr-time#74, by @marcoscaceres.
-
Editorial: give SPECTRE paper a title w3c/hr-time#73, by @marcoscaceres.
-
Adding export, no-export, and improving some refs w3c/hr-time#72, by @plehegar.
-
-
5 pull requests merged.
-
chore(travis): use https for w3c manifest w3c/hr-time#75.
-
chore(travis): use https for w3c manifest w3c/hr-time#74.
-
Editorial: give SPECTRE paper a title w3c/hr-time#73.
-
Adding export, no-export, and improving some refs w3c/hr-time#72.
-
Fixed respec references w3c/hr-time#71.
-
-
2 pull requests received 10 new comments.
w3c/longtasks
-
3 issues opened.
-
"multiple-contexts" doesn't seem useful w3c/longtasks#67, by @rniwa.
-
Container information should be hidden if container appeared in cross-origin frames w3c/longtasks#66, by @rniwa.
-
containerSrc could be long (a data URI) w3c/longtasks#64, by @tdresser.
-
-
6 issues closed.
-
Document reasons for "unknown" attribution w3c/longtasks#25.
-
toJSON w3c/longtasks#37.
-
Specifying the attributes of each object more rigorously w3c/longtasks#11.
-
Long tasks v2 scriptUrl -> scriptURL w3c/longtasks#36.
-
Needs toJSON defined w3c/longtasks#31.
-
Indicate script parse time in attribution w3c/longtasks#30.
-
-
11 issues received 25 new comments.
-
containerSrc could be long (a data URI) w3c/longtasks#64 (4 comments by @domenic, @hawkinsw, @tdresser, @toddreifsteck)
-
The processing model only works for iframes, not object/embed/etc. w3c/longtasks#52 (2 comments by @domenic, @tdresser)
-
Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? w3c/longtasks#41 (1 comment by @tdresser)
-
5 pull requests opened.
-
Suggest some readability updates to the intro paragraphs. w3c/longtasks#69, by @hawkinsw.
-
Replace supportedEntryTypes registration with Note w3c/longtasks#68, by @npm1.
-
Add support for <embed> and <object> containerTypes. w3c/longtasks#65, by @tdresser.
-
Add explicit toJSON. w3c/longtasks#63, by @tdresser.
-
Describe name attributes's "unknown" and "multiple-contexts" values. w3c/longtasks#62, by @tdresser.
-
-
3 pull requests merged.
-
Replace supportedEntryTypes registration with Note w3c/longtasks#68.
-
Describe name attributes's "unknown" and "multiple-contexts" values. w3c/longtasks#62.
-
Add explicit toJSON. w3c/longtasks#63.
-
-
2 pull requests received 11 new comments.
-
Add support for <embed> and <object> containerTypes. w3c/longtasks#65 (10 comments by @domenic, @npm1, @tdresser)
-
w3c/user-timing
-
1 issue closed.
-
1 issue received 1 new comment.
-
StructuredDeserialize should be used; serialization records cannot be returned from IDL getters w3c/user-timing#59 (1 comment by @npm1)
-
-
5 pull requests opened.
-
Fix a couple of links w3c/user-timing#64, by @npm1.
-
chore(travis): use https for w3c manifest w3c/user-timing#63, by @marcoscaceres.
-
Fix <li> element w3c/user-timing#62, by @plehegar.
-
Deserialize the serialized detail w3c/user-timing#61, by @npm1.
-
Replace supportedEntryTypes registration with Note w3c/user-timing#60, by @npm1.
-
-
5 pull requests merged.
-
Fix a couple of links w3c/user-timing#64.
-
chore(travis): use https for w3c manifest w3c/user-timing#63.
-
Fix <li> element w3c/user-timing#62.
-
Deserialize the serialized detail w3c/user-timing#61.
-
Replace supportedEntryTypes registration with Note w3c/user-timing#60.
-
-
1 pull request received 1 new comment.
w3c/reporting
-
3 issues opened.
-
Consider credential-less reporting w3c/reporting#161, by @johnwilander.
-
Are include_subdomains configurations allowed for raw IPs? w3c/reporting#160, by @chlily1.
-
Disallow include_subdomains from eTLDs w3c/reporting#159, by @chlily1.
-
-
5 issues received 21 new comments.
-
Disallow include_subdomains from eTLDs w3c/reporting#159 (12 comments by @chlily1, @dcreager, @igrigorik)
-
Consider credential-less reporting w3c/reporting#161 (4 comments by @dcreager, @igrigorik, @mikewest)
-
Are include_subdomains configurations allowed for raw IPs? w3c/reporting#160 (2 comments by @dcreager)
-
-
2 pull requests opened.
-
Clean up subdomain match logic w3c/reporting#163, by @dcreager.
-
Add note about capability URLs w3c/reporting#162, by @dcreager.
-
-
1 pull request received 1 new comment.
w3c/element-timing
-
2 issues opened.
-
`naturalWidth` and `naturalHeight`? w3c/element-timing#12, by @yoavweiss.
-
ResourceTiming's responseEnd is earlier than image real render complete time w3c/element-timing#11, by @xcodebuild.
-
-
2 issues closed.
-
`naturalWidth` and `naturalHeight`? w3c/element-timing#12.
-
ResourceTiming's responseEnd is earlier than image real render complete time w3c/element-timing#11.
-
-
3 issues received 13 new comments.
-
`naturalWidth` and `naturalHeight`? w3c/element-timing#12 (7 comments by @npm1, @tdresser, @yoavweiss)
-
ResourceTiming's responseEnd is earlier than image real render complete time w3c/element-timing#11 (3 comments by @npm1, @xcodebuild)
-
-
2 pull requests opened.
-
Add support for data URL images w3c/element-timing#14, by @npm1.
-
Add hooks for LCP integration w3c/element-timing#13, by @yoavweiss.
-
-
1 pull request merged.
-
Add hooks for LCP integration w3c/element-timing#13.
-
-
1 pull request received 13 new comments.
w3c/performance-timeline
-
2 issues opened.
-
buffered flag should not be removed from PerformanceObserverInit w3c/performance-timeline#139, by @npm1.
-
Spec errors related to DOMHighResTimestamp w3c/performance-timeline#136, by @yoavweiss.
-
-
4 issues closed.
-
Spec errors related to DOMHighResTimestamp w3c/performance-timeline#136.
-
Relevant global object for 'relevant performance entry buffer' w3c/performance-timeline#122.
-
supportedEntryTypes API has some issues w3c/performance-timeline#117.
-
supported entry types needs to be context aware w3c/performance-timeline#113.
-
-
1 issue reopened.
-
How does "queue a PerformanceEntry" algorithm interact with other specs? w3c/performance-timeline#128, by @npm1.
-
-
4 issues received 8 new comments.
-
How does "queue a PerformanceEntry" algorithm interact with other specs? w3c/performance-timeline#128 (3 comments by @jdm, @npm1)
-
Spec errors related to DOMHighResTimestamp w3c/performance-timeline#136 (3 comments by @marcoscaceres, @plehegar, @yoavweiss)
-
Relevant global object for 'relevant performance entry buffer' w3c/performance-timeline#122 (1 comment by @yoavweiss)
-
PerformanceEntries are affected by backgrounded status w3c/performance-timeline#105 (1 comment by @mikesherov)
-
-
5 pull requests opened.
-
Remove remaining `buffered` flag w3c/performance-timeline#138, by @saschanaz.
-
More fixes w3c/performance-timeline#137, by @plehegar.
-
Update buffer map initialization w3c/performance-timeline#135, by @ehanley324.
-
Merge using registry to L2 w3c/performance-timeline#134, by @npm1.
-
Use registry for supportedEntryTypes w3c/performance-timeline#133, by @npm1.
-
-
5 pull requests merged.
-
Auto pub level2 w3c/performance-timeline#127.
-
Update buffer map initialization w3c/performance-timeline#135.
-
References cleanup w3c/performance-timeline#132.
-
Merge using registry to L2 w3c/performance-timeline#134.
-
Use registry for supportedEntryTypes w3c/performance-timeline#133.
-
-
2 pull requests closed.
-
Remove remaining `buffered` flag w3c/performance-timeline#138.
-
supported entry types needs to be context aware w3c/performance-timeline#121.
-
-
6 pull requests received 26 new comments.
-
Update buffer map initialization w3c/performance-timeline#135 (4 comments by @ehanley324, @yoavweiss)
w3c/navigation-timing
-
1 issue opened.
-
Plenty of refs seem unhappy w3c/navigation-timing#109, by @yoavweiss.
-
-
3 issues closed.
-
supported entry types needs to be context aware w3c/navigation-timing#102.
-
"timing allow check" is not well defined in the context of NavTiming w3c/navigation-timing#104.
-
Plenty of refs seem unhappy w3c/navigation-timing#109.
-
-
5 issues received 8 new comments.
-
"timing allow check" is not well defined in the context of NavTiming w3c/navigation-timing#104 (2 comments by @annevk, @igrigorik)
-
workerStart should be gated on same-origin check w3c/navigation-timing#99 (2 comments by @yoavweiss)
-
workerStart should be clearly defined as applicable to the last SW w3c/navigation-timing#100 (1 comment by @yoavweiss)
-
5 pull requests opened.
-
chore(travis): use https for w3c manifest w3c/navigation-timing#113, by @marcoscaceres.
-
chore: use formerEditors ReSpec option w3c/navigation-timing#112, by @marcoscaceres.
-
Fixes a bunch of links w3c/navigation-timing#111, by @plehegar.
-
Replace supportedEntryTypes registration with Note w3c/navigation-timing#110, by @npm1.
-
Replace TAO checks with same origin check w3c/navigation-timing#108, by @yoavweiss.
-
-
5 pull requests merged.
-
chore(travis): use https for w3c manifest w3c/navigation-timing#113.
-
chore: use formerEditors ReSpec option w3c/navigation-timing#112.
-
Replace TAO checks with same origin check w3c/navigation-timing#108.
-
Replace supportedEntryTypes registration with Note w3c/navigation-timing#110.
-
Fixes a bunch of links w3c/navigation-timing#111.
-
-
1 pull request closed.
-
supported entry types needs to be context aware w3c/navigation-timing#105.
-
-
4 pull requests received 28 new comments.
-
Replace TAO checks with same origin check w3c/navigation-timing#108 (24 comments by @npm1, @yoavweiss)
-
Replace supportedEntryTypes registration with Note w3c/navigation-timing#110 (1 comment by @yoavweiss)
-
w3c/timing-entrytypes-registry
-
2 pull requests opened.
-
Export `availableFromTimeline` w3c/timing-entrytypes-registry#2, by @saschanaz.
-
Update registry to include buffer map values w3c/timing-entrytypes-registry#1, by @ehanley324.
-
-
1 pull request merged.
-
Update registry to include buffer map values w3c/timing-entrytypes-registry#1.
-
-
2 pull requests received 20 new comments.
-
Update registry to include buffer map values w3c/timing-entrytypes-registry#1 (12 comments by @ehanley324, @npm1, @yoavweiss)
-
Export `availableFromTimeline` w3c/timing-entrytypes-registry#2 (8 comments by @marcoscaceres, @saschanaz)
-
w3c/resource-timing
-
2 issues opened.
-
Spec errors related to DOMHighResTimestamp and EventHandler w3c/resource-timing#212, by @yoavweiss.
-
Cross-origin IFRAME opting-in to sharing ResourceTiming data w3c/resource-timing#210, by @nicjansma.
-
-
1 issue closed.
-
Spec errors related to DOMHighResTimestamp and EventHandler w3c/resource-timing#212.
-
-
1 issue received 1 new comment.
-
Cross-origin IFRAME opting-in to sharing ResourceTiming data w3c/resource-timing#210 (1 comment by @igrigorik)
-
-
2 pull requests opened.
-
fix: small xref fixes w3c/resource-timing#213, by @marcoscaceres.
-
Replace supportedEntryTypes registration with Note w3c/resource-timing#211, by @npm1.
-
-
2 pull requests merged.
-
fix: small xref fixes w3c/resource-timing#213.
-
Replace supportedEntryTypes registration with Note w3c/resource-timing#211.
-
w3c/largest-contentful-paint
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Link to image and text considerations w3c/largest-contentful-paint#2, by @npm1.
-
-
1 pull request merged.
-
Link to image and text considerations w3c/largest-contentful-paint#2.
-
-
1 pull request received 1 new comment.
w3c/requestidlecallback
-
1 issue received 10 new comments.
-
"deadline" in the "start an idle period algorithm" should be defined in terms of event loop w3c/requestidlecallback#71 (10 comments by @bzbarsky, @rmcilroy, @rniwa, @yoavweiss)
-
-
1 pull request received 4 new comments.
w3c/event-timing
-
3 issues received 8 new comments.
-
1 pull request opened.
-
Remove "Queueing other entries" w3c/event-timing#53, by @npm1.
-
-
1 pull request merged.
-
Remove "Queueing other entries" w3c/event-timing#53.
-
w3c/paint-timing
-
2 pull requests opened.
-
Replace entryType registration hook with Note w3c/paint-timing#42, by @npm1.
-
Add PR Preview to paint-timing w3c/paint-timing#41, by @npm1.
-
-
2 pull requests merged.
-
Replace entryType registration hook with Note w3c/paint-timing#42.
-
Add PR Preview to paint-timing w3c/paint-timing#41.
-
-
1 pull request received 7 new comments.
-
Replace entryType registration hook with Note w3c/paint-timing#42 (7 comments by @domenic, @npm1, @yoavweiss)
-
TR publications
-
1 document published.
-
Resource Timing Level 2 published as a Working Draft. History of Resource Timing Level 2
-
Participants
-
1 organization joined.
-
Mitsubishi Electric Corporation joined.
-
GitHub
w3c/element-timing
-
4 issues opened.
-
Define a better way to provide 'implicit registration' w3c/element-timing#9, by @npm1.
-
Improve definition of "associated element" w3c/element-timing#8, by @npm1.
-
Should text and image have different entryType w3c/element-timing#4, by @npm1.
-
How should Element Timing interact with Shadow DOM? w3c/element-timing#3, by @npm1.
-
-
2 issues received 11 new comments.
-
How should Element Timing interact with Shadow DOM? w3c/element-timing#3 (9 comments by @annevk, @hayatoito, @npm1)
-
Should text and image have different entryType w3c/element-timing#4 (2 comments by @npm1, @tdresser)
-
-
4 pull requests opened.
-
Remove implicit registration from spec w3c/element-timing#10, by @npm1.
-
Add text support w3c/element-timing#7, by @npm1.
-
Update image attributes w3c/element-timing#6, by @npm1.
-
Address feedback w3c/element-timing#5, by @npm1.
-
-
4 pull requests merged.
-
Remove implicit registration from spec w3c/element-timing#10.
-
Add text support w3c/element-timing#7.
-
Update image attributes w3c/element-timing#6.
-
Address feedback w3c/element-timing#5.
-
-
2 pull requests received 31 new comments.
w3c/performance-timeline
-
3 issues opened.
-
PerformanceObserver is unable to measure some timing attributes w3c/performance-timeline#131, by @SemihGk.
-
"relevant performance entry tuple" usage is still broken w3c/performance-timeline#130, by @bzbarsky.
-
How does "queue a PerformanceEntry" algorithm interact with other specs? w3c/performance-timeline#128, by @jdm.
-
-
2 issues closed.
-
PerformanceObserver is unable to measure some timing attributes w3c/performance-timeline#131.
-
Republish L2 based on the latest "level2" branch w3c/performance-timeline#124.
-
-
5 issues received 13 new comments.
-
"relevant performance entry tuple" usage is still broken w3c/performance-timeline#130 (2 comments by @bzbarsky, @npm1)
-
How does "queue a PerformanceEntry" algorithm interact with other specs? w3c/performance-timeline#128 (2 comments by @jdm)
-
PerformanceObserver is unable to measure some timing attributes w3c/performance-timeline#131 (1 comment by @SemihGk)
-
2 pull requests opened.
-
References cleanup w3c/performance-timeline#132, by @plehegar.
-
Backport the relevant global object definition for the relevant performance entry buffer w3c/performance-timeline#129, by @yoavweiss.
-
-
3 pull requests merged.
-
Backport the relevant global object definition for the relevant performance entry buffer w3c/performance-timeline#129.
-
terminate auto-pub on gh-pages w3c/performance-timeline#126.
-
Buffered flag spec changes w3c/performance-timeline#123.
-
-
1 pull request closed.
-
supportedEntryTypes: cache the FrozenArray w3c/performance-timeline#118.
-
-
2 pull requests received 33 new comments.
-
Buffered flag spec changes w3c/performance-timeline#123 (25 comments by @ehanley324, @npm1, @yoavweiss)
-
supportedEntryTypes: cache the FrozenArray w3c/performance-timeline#118 (8 comments by @npm1, @rniwa, @yoavweiss)
-
w3c/hr-time
-
1 issue opened.
-
Add mitigation list to security & privacy section w3c/hr-time#67, by @yoavweiss.
-
-
4 issues closed.
-
can performance.now() timers be frozen for background tabs, etc? w3c/hr-time#65.
-
Add mitigation list to security & privacy section w3c/hr-time#67.
-
Privacy (PING) review w3c/hr-time#20.
-
Gate Timestamps behind existing permission prompts w3c/hr-time#64.
-
-
2 issues received 3 new comments.
-
Gate Timestamps behind existing permission prompts w3c/hr-time#64 (2 comments by @pes10k, @yoavweiss)
-
-
4 pull requests opened.
-
Fixed respec references w3c/hr-time#71, by @plehegar.
-
Refreshed ReSpec config w3c/hr-time#70, by @plehegar.
-
Add a note on now() in backgrounded tabs w3c/hr-time#69, by @yoavweiss.
-
Added a list of potential mitigations to timing attacks w3c/hr-time#68, by @yoavweiss.
-
-
3 pull requests merged.
-
Refreshed ReSpec config w3c/hr-time#70.
-
Add a note on now() in backgrounded tabs w3c/hr-time#69.
-
Added a list of potential mitigations to timing attacks w3c/hr-time#68.
-
-
4 pull requests received 21 new comments.
-
Added a list of potential mitigations to timing attacks w3c/hr-time#68 (6 comments by @igrigorik, @tomrittervg, @yoavweiss)
-
Add a note on now() in backgrounded tabs w3c/hr-time#69 (4 comments by @igrigorik, @npm1, @yoavweiss)
w3c/largest-contentful-paint
-
1 issue opened.
-
Any polyfill could be used currently? w3c/largest-contentful-paint#1, by @NE-SmallTown.
-
w3c/network-error-logging
-
3 issues received 17 new comments.
-
Signed Exchange Reporting w3c/network-error-logging#99 (9 comments by @horo-t, @igrigorik, @jyasskin, @shhnjk)
-
Are user initiated aborts a network failure? w3c/network-error-logging#108 (7 comments by @aaronpeters, @chlily1, @igrigorik, @MattMenke2)
-
Clear report body fields based on `phase` and report destination w3c/network-error-logging#105 (1 comment by @aaronpeters)
-
-
2 pull requests opened.
-
Comply with the <dfn> policy for "NEL policy" w3c/network-error-logging#114, by @jyasskin.
-
Export "NEL policy" w3c/network-error-logging#113, by @jyasskin.
-
-
3 pull requests merged.
-
Comply with the <dfn> policy for "NEL policy" w3c/network-error-logging#114.
-
Export "NEL policy" w3c/network-error-logging#109.
-
Use example IP addresses from RFC5737 and RFC3849. w3c/network-error-logging#110.
-
-
1 pull request closed.
-
Export "NEL policy" w3c/network-error-logging#113.
-
-
1 pull request received 1 new comment.
w3c/reporting
-
4 issues opened.
-
Feedback from Mozilla w3c/reporting#158, by @annevk.
-
reporting cache replace operation not defined w3c/reporting#157, by @annevk.
-
superdomain match for origin is bogus w3c/reporting#156, by @annevk.
-
Capability URL problem bigger than advertized w3c/reporting#155, by @annevk.
-
-
4 issues closed.
-
Friendly TAG Review: Crash ids w3c/reporting#55.
-
Custom reports w3c/reporting#73.
-
intervention reports do not contain id w3c/reporting#145.
-
How to support "deprecation" and "intervention" use cases w3c/reporting#27.
-
-
7 issues received 19 new comments.
-
Endpoint weighted selection algorithm fails if weights are 0 w3c/reporting#153 (6 comments by @chlily1, @dcreager, @gapple, @sburnett)
-
Relative URLs in endpoints configuration. w3c/reporting#147 (6 comments by @dcreager, @igrigorik, @koto)
-
-
1 pull request opened.
-
Make endpoint selection algorithm match DNS SRV's target selection algorithm w3c/reporting#154, by @sburnett.
-
-
1 pull request merged.
-
Make endpoint selection algorithm match DNS SRV's target selection algorithm w3c/reporting#154.
-
w3c/event-timing
-
17 issues opened.
-
Considered for event timing: drag & drop w3c/event-timing#52, by @annevk.
-
Provide more explanatory material in processing model w3c/event-timing#51, by @npm1.
-
Add a note to caution about meaningfulness of first event w3c/event-timing#50, by @npm1.
-
Semantics behind list w3c/event-timing#49, by @annevk.
-
Event Timing spec is up! w3c/event-timing#47, by @npm1.
-
Set up PR preview w3c/event-timing#42, by @domenic.
-
Formatting/style nits w3c/event-timing#35, by @domenic.
-
"Queuing other entries" section is confusing w3c/event-timing#34, by @domenic.
-
Unclear the maplike does what you're expecting w3c/event-timing#33, by @domenic.
-
"finalize event timing" append step seems wrong w3c/event-timing#32, by @domenic.
-
Various uses of public JavaScript APIs w3c/event-timing#31, by @domenic.
-
Use implements to check type w3c/event-timing#30, by @domenic.
-
Which events to capture? The current setup is a bit strange. w3c/event-timing#29, by @domenic.
-
"Dispatch pending entries" is too generic of a name w3c/event-timing#28, by @domenic.
-
Use unsigned long long instead of unsigned long? w3c/event-timing#27, by @domenic.
-
Non-normative section has a must w3c/event-timing#26, by @domenic.
-
-
16 issues closed.
-
Various uses of public JavaScript APIs w3c/event-timing#31.
-
Unclear the maplike does what you're expecting w3c/event-timing#33.
-
Formatting/style nits w3c/event-timing#35.
-
Set up PR preview w3c/event-timing#42.
-
"finalize event timing" append step seems wrong w3c/event-timing#32.
-
Use implements to check type w3c/event-timing#30.
-
Which events to capture? The current setup is a bit strange. w3c/event-timing#29.
-
"Dispatch pending entries" is too generic of a name w3c/event-timing#28.
-
Use unsigned long long instead of unsigned long? w3c/event-timing#27.
-
Non-normative section has a must w3c/event-timing#26.
-
Does / should FID duration reflect time to next render frame? w3c/event-timing#25.
-
Consider recording event timing outside of event dispatch w3c/event-timing#8.
-
Specify how to report EventTiming outside of event handlers w3c/event-timing#21.
-
FirstInput must always be reported w3c/event-timing#20.
-
Should we spec the buffer related APIs somewhere? w3c/event-timing#2.
-
12 issues received 41 new comments.
-
Which events to capture? The current setup is a bit strange. w3c/event-timing#29 (7 comments by @domenic, @npm1, @tdresser)
-
"Approximate the 75'th percentile of click event queueing times." as a use case does not make sense w3c/event-timing#48 (6 comments by @npm1, @smaug----)
-
Does / should FID duration reflect time to next render frame? w3c/event-timing#25 (6 comments by @igrigorik, @npm1, @tdresser)
-
-
10 pull requests opened.
-
Fixes in algorithms w3c/event-timing#46, by @npm1.
-
Change event linking w3c/event-timing#45, by @npm1.
-
Add PR Preview support w3c/event-timing#43, by @npm1.
-
Editorial fixes w3c/event-timing#41, by @npm1.
-
Use relevant global object to obtain the Window w3c/event-timing#40, by @npm1.
-
Consider event types instead of event classes w3c/event-timing#39, by @npm1.
-
Improve dispatch algorithm name w3c/event-timing#38, by @npm1.
-
Use unsigned long long w3c/event-timing#37, by @npm1.
-
Enforce language in non-normative sections w3c/event-timing#36, by @npm1.
-
-
10 pull requests merged.
-
Fixes in algorithms w3c/event-timing#46.
-
Change event linking w3c/event-timing#45.
-
Fix nits w3c/event-timing#44.
-
Add PR Preview support w3c/event-timing#43.
-
Editorial fixes w3c/event-timing#41.
-
Use relevant global object to obtain the Window w3c/event-timing#40.
-
Consider event types instead of event classes w3c/event-timing#39.
-
Improve dispatch algorithm name w3c/event-timing#38.
-
Use unsigned long long w3c/event-timing#37.
-
Enforce language in non-normative sections w3c/event-timing#36.
-
-
5 pull requests received 22 new comments.
w3c/user-timing
-
1 issue opened.
w3c/server-timing
-
1 issue received 1 new comment.
w3c/resource-timing
-
1 issue closed.
-
Encapsulate responseEnd in an algorithm w3c/resource-timing#208.
-
-
1 pull request opened.
-
Split response end to a separate algorithm w3c/resource-timing#209, by @yoavweiss.
-
-
1 pull request merged.
-
Split response end to a separate algorithm w3c/resource-timing#209.
-
-
1 pull request received 8 new comments.
-
Split response end to a separate algorithm w3c/resource-timing#209 (8 comments by @npm1, @yoavweiss)
-
w3c/navigation-timing
-
1 issue opened.
-
Navigation Timing behavior for HTTP Exchange (SxG) loading w3c/navigation-timing#107, by @igrigorik.
-
-
2 issues received 3 new comments.
-
Navigation Timing behavior for HTTP Exchange (SxG) loading w3c/navigation-timing#107 (2 comments by @sleevi, @yoavweiss)
-
Should navigationEntry's navigationType be updated according to the parent page ? w3c/navigation-timing#85 (1 comment by @VigneshSubramaniam)
-
TR publications
-
3 documents published.
-
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
-
Performance Timeline Level 2 published as a Working Draft. History of Performance Timeline Level 2
-
Participants
-
1 participant left.
-
Gilles Dubuc (Wikimedia Foundation) left.
-
-
2 organizations joined.
-
Salesforce joined.
-
Wikimedia Foundation joined.
-
GitHub
w3c/event-timing
-
1 issue opened.
-
Does / should FID duration reflect time to next render frame? w3c/event-timing#25, by @igrigorik.
-
-
2 issues received 8 new comments.
-
Does / should FID duration reflect time to next render frame? w3c/event-timing#25 (2 comments by @npm1, @tdresser)
-
1 pull request opened.
-
Use CG-DRAFT status w3c/event-timing#24, by @marcoscaceres.
-
-
1 pull request merged.
-
Use CG-DRAFT status w3c/event-timing#24.
-
w3c/performance-timeline
-
1 issue opened.
-
Republish L2 based on the latest "level2" branch w3c/performance-timeline#124, by @yoavweiss.
-
-
1 issue closed.
-
WebIDL spec does not allow required dictionary argument with no required members w3c/performance-timeline#119.
-
-
3 issues received 14 new comments.
-
Republish L2 based on the latest "level2" branch w3c/performance-timeline#124 (3 comments by @siusin, @yoavweiss)
-
Relevant global object for 'relevant performance entry buffer' w3c/performance-timeline#122 (2 comments by @yoavweiss)
-
4 pull requests opened.
-
Auto pub level2 w3c/performance-timeline#127, by @siusin.
-
terminate auto-pub on gh-pages w3c/performance-timeline#126, by @siusin.
-
Emily Hanley's buffered flag PR w3c/performance-timeline#125, by @yoavweiss.
-
Buffered flag spec changes w3c/performance-timeline#123, by @ehanley324.
-
-
1 pull request closed.
-
Emily Hanley's buffered flag PR w3c/performance-timeline#125.
-
-
1 pull request received 48 new comments.
-
Buffered flag spec changes w3c/performance-timeline#123 (48 comments by @ehanley324, @npm1, @yoavweiss)
-
w3c/resource-timing
-
2 issues opened.
-
Encapsulate responseEnd in an algorithm w3c/resource-timing#208, by @npm1.
-
Clarify that TAO needs to be set even on same origin resource after cross-origin redirects w3c/resource-timing#207, by @rniwa.
-
-
3 issues closed.
-
Specify TAO check for 304 responses w3c/resource-timing#201.
-
Resource Timing and range requests w3c/resource-timing#205.
-
`origin-or-null` definition and TAO processing w3c/resource-timing#152.
-
-
4 issues received 12 new comments.
-
Specify TAO check for 304 responses w3c/resource-timing#201 (7 comments by @annevk, @npm1, @yoavweiss)
-
Resource Timing and range requests w3c/resource-timing#205 (3 comments by @igrigorik, @nicjansma, @yoavweiss)
-
Clarify that TAO needs to be set even on same origin resource after cross-origin redirects w3c/resource-timing#207 (1 comment by @yoavweiss)
-
Clarify what transferSize, encodedBodySize should return in various conditions w3c/resource-timing#40 (1 comment by @taxi666)
-
-
1 pull request opened.
-
Clarify TAO processing when it comes to revalidation responses w3c/resource-timing#206, by @yoavweiss.
-
-
1 pull request merged.
-
Clarify TAO processing when it comes to revalidation responses w3c/resource-timing#206.
-
-
1 pull request received 7 new comments.
-
Clarify TAO processing when it comes to revalidation responses w3c/resource-timing#206 (7 comments by @npm1, @yoavweiss)
-
w3c/hr-time
-
1 issue opened.
-
can performance.now() timers be frozen for background tabs, etc? w3c/hr-time#65, by @wanderview.
-
-
2 issues closed.
-
Find better sources to quote than Wikipedia w3c/hr-time#62.
-
Security Review w3c/hr-time#60.
-
-
1 issue reopened.
-
Privacy (PING) review w3c/hr-time#20, by @yoavweiss.
-
-
6 issues received 42 new comments.
-
Gate Timestamps behind existing permission prompts w3c/hr-time#64 (19 comments by @igrigorik, @noncombatant, @pes10k, @rniwa, @tomrittervg, @yoavweiss)
-
can performance.now() timers be frozen for background tabs, etc? w3c/hr-time#65 (13 comments by @igrigorik, @npm1, @skyostil, @spanicker, @wanderview, @yoavweiss)
-
Reducing the precision of the DOMHighResTimeStamp resolution w3c/hr-time#56 (1 comment by @igrigorik)
-
-
1 pull request opened.
-
Refer to ECMA-262 time rather than unix time w3c/hr-time#66, by @yoavweiss.
-
-
1 pull request merged.
-
Refer to ECMA-262 time rather than unix time w3c/hr-time#66.
-
-
1 pull request received 4 new comments.
-
Refer to ECMA-262 time rather than unix time w3c/hr-time#66 (4 comments by @marcoscaceres, @toddreifsteck, @yoavweiss)
-
w3c/user-timing
-
3 issues opened.
-
detail field null? w3c/user-timing#56, by @npm1.
-
Use more appropriate error types w3c/user-timing#55, by @npm1.
-
startOrOptions cannot be nullable w3c/user-timing#54, by @npm1.
-
-
3 issues closed.
-
detail field null? w3c/user-timing#56.
-
Use more appropriate error types w3c/user-timing#55.
-
startOrOptions cannot be nullable w3c/user-timing#54.
-
-
2 issues received 9 new comments.
-
2 pull requests opened.
-
Replace RangeErrors with TypeErrors w3c/user-timing#58, by @npm1.
-
-
2 pull requests merged.
-
Replace RangeErrors with TypeErrors w3c/user-timing#58.
-
L3 fixes w3c/user-timing#57.
-
-
1 pull request received 13 new comments.
w3c/navigation-timing
-
1 issue received 2 new comments.
-
"timing allow check" is not well defined in the context of NavTiming w3c/navigation-timing#104 (2 comments by @annevk, @yoavweiss)
-
-
1 pull request opened.
-
Avoid redefining secureConnectionStart w3c/navigation-timing#106, by @yoavweiss.
-
w3c/perf-timing-primer
-
1 issue opened.
-
Typos etc in Section 6.2 w3c/perf-timing-primer#18, by @hawkinsw.
-
-
1 issue closed.
-
Typos etc in Section 6.2 w3c/perf-timing-primer#18.
-
-
1 pull request opened.
-
Fix #18: Correct a few typos change wording. w3c/perf-timing-primer#19, by @hawkinsw.
-
-
1 pull request merged.
-
Fix #18: Correct a few typos change wording. w3c/perf-timing-primer#19.
-
w3c/network-error-logging
-
2 issues opened.
-
NEL header injection attack allows stealing HttpOnly cookies w3c/network-error-logging#112, by @chlily1.
-
`request_headers` may send SameSite cookies cross-site w3c/network-error-logging#111, by @chlily1.
-
-
2 issues received 6 new comments.
-
Are user initiated aborts a network failure? w3c/network-error-logging#108 (5 comments by @chlily1, @igrigorik, @yoavweiss)
-
Clear report body fields based on `phase` and report destination w3c/network-error-logging#105 (1 comment by @chlily1)
-
w3c/longtasks
-
1 issue opened.
-
containerType is confusing w3c/longtasks#61, by @SilentImp.
-
-
2 issues received 5 new comments.
w3c/reporting
-
1 issue opened.
-
Endpoint weighted selection algorithm fails if weights are 0 w3c/reporting#153, by @chlily1.
-
-
2 issues received 2 new comments.
-
Allow features to de-duplicate reports rather than sending redundant information w3c/reporting#6 (1 comment by @aarongustafson)
TR publications
-
9 documents published.
-
Performance Timeline Level 2 published 3 times 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
-
User Timing Level 3 published as a Working Draft. History of User Timing Level 3
-
Resource Hints published as a Working Draft. History of Resource Hints
-
Resource Timing Level 2 published as a Working Draft. History of Resource Timing Level 2
-
Server Timing published as a Working Draft. History of Server Timing
-
User Timing Level 3 published as a First Public Working Draft. History of User Timing Level 3
-
GitHub
w3c/beacon
-
1 issue received 5 new comments.
-
Should sendBeacon support GET? w3c/beacon#22 (5 comments by @annevk, @emmettbutler, @igrigorik, @yoavweiss)
-
-
1 pull request received 1 new comment.
w3c/resource-timing
-
3 issues opened.
-
Resource Timing and range requests w3c/resource-timing#205, by @yoavweiss.
-
Add tests for not-same-site nested contexts w3c/resource-timing#204, by @yoavweiss.
-
Include Content Type w3c/resource-timing#203, by @Snugug.
-
-
4 issues received 4 new comments.
-
Be a bit more explicit about which subresources are to be ignored from stylesheets w3c/resource-timing#200 (1 comment by @yoavweiss)
w3c/performance-timeline
-
3 issues opened.
-
Relevant global object for 'relevant performance entry buffer' w3c/performance-timeline#122, by @npm1.
-
WebIDL spec does not allow required dictionary argument with no required members w3c/performance-timeline#119, by @hawkinsw.
-
supportedEntryTypes API has some issues w3c/performance-timeline#117, by @bzbarsky.
-
-
1 issue closed.
-
Broken link to non-existent anchor in WebIDL spec w3c/performance-timeline#110.
-
-
6 issues received 32 new comments.
-
supportedEntryTypes API has some issues w3c/performance-timeline#117 (14 comments by @annevk, @bzbarsky, @npm1)
-
Add entryTypes method to enumerate type of entries observable via PerformanceObserver w3c/performance-timeline#77 (7 comments by @bzbarsky, @npm1)
-
WebIDL spec does not allow required dictionary argument with no required members w3c/performance-timeline#119 (3 comments by @hawkinsw, @npm1, @rniwa)
-
Broken link to non-existent anchor in WebIDL spec w3c/performance-timeline#110 (2 comments by @npm1)
-
supported entry types needs to be context aware w3c/performance-timeline#113 (2 comments by @npm1, @toddreifsteck)
-
-
6 pull requests opened.
-
supported entry types needs to be context aware w3c/performance-timeline#121, by @cvazac.
-
Make observe() parameter an optional dictionary w3c/performance-timeline#120, by @npm1.
-
supportedEntryTypes: cache the FrozenArray w3c/performance-timeline#118, by @npm1.
-
Fix a link to filter algorithm again w3c/performance-timeline#116, by @marcoscaceres.
-
Fix a link to filter algorithm w3c/performance-timeline#115, by @npm1.
-
L2: Remove buffered flag w3c/performance-timeline#114, by @npm1.
-
-
4 pull requests merged.
-
Make observe() parameter an optional dictionary w3c/performance-timeline#120.
-
Fix a link to filter algorithm again w3c/performance-timeline#116.
-
Fix a link to filter algorithm w3c/performance-timeline#115.
-
L2: Remove buffered flag w3c/performance-timeline#114.
-
-
5 pull requests received 19 new comments.
-
Fix a link to filter algorithm w3c/performance-timeline#115 (7 comments by @marcoscaceres, @npm1, @yoavweiss)
-
supportedEntryTypes: cache the FrozenArray w3c/performance-timeline#118 (6 comments by @bzbarsky, @npm1, @rniwa)
-
Make observe() parameter an optional dictionary w3c/performance-timeline#120 (3 comments by @hawkinsw, @npm1)
-
Fix a link to filter algorithm again w3c/performance-timeline#116 (2 comments by @marcoscaceres, @yoavweiss)
-
w3c/navigation-timing
-
1 issue opened.
-
"timing allow check" is not well defined in the context of NavTiming w3c/navigation-timing#104, by @bzbarsky.
-
-
1 issue closed.
-
Unload event TAO check should be for all redirects w3c/navigation-timing#95.
-
-
3 issues received 4 new comments.
-
Should navigationEntry's navigationType be updated according to the parent page ? w3c/navigation-timing#85 (2 comments by @toddreifsteck, @yoavweiss)
-
should unloaded iframes be included in their parent document's unload duration? w3c/navigation-timing#83 (1 comment by @yoavweiss)
-
-
2 pull requests opened.
-
supported entry types needs to be context aware w3c/navigation-timing#105, by @cvazac.
-
Make sure all redirects pass TAO before exposing unload data w3c/navigation-timing#103, by @yoavweiss.
-
-
1 pull request merged.
-
Make sure all redirects pass TAO before exposing unload data w3c/navigation-timing#103.
-
-
1 pull request received 1 new comment.
-
Make sure all redirects pass TAO before exposing unload data w3c/navigation-timing#103 (1 comment by @toddreifsteck)
-
w3c/element-timing
-
2 issues opened.
-
Link Resource Timing entry w3c/element-timing#2, by @npm1.
-
Reference point for startTime? w3c/element-timing#1, by @gi11es.
-
-
1 issue closed.
-
Reference point for startTime? w3c/element-timing#1.
-
-
2 issues received 9 new comments.
w3c/user-timing
-
7 issues closed.
-
Declarative marks w3c/user-timing#17.
-
Enable association with input events. w3c/user-timing#15.
-
Handling repeat metrics and measures + custom startTime? w3c/user-timing#14.
-
mark() and measure() return PerformanceEntries w3c/user-timing#23.
-
Should performance.measure() work with resource timing entries? w3c/user-timing#27.
-
Measure API: make startOrOptions nullable w3c/user-timing#48.
-
Level 3 proposal w3c/user-timing#43.
-
-
9 issues received 17 new comments.
-
Enable association with input events. w3c/user-timing#15 (3 comments by @npm1, @tdresser, @yoavweiss)
-
Provide a way to associate warnings with measurements w3c/user-timing#25 (2 comments by @igrigorik, @npm1)
-
Update the introductory text to explain how this API differs from performance.now() w3c/user-timing#37 (1 comment by @igrigorik)
-
Should performance.measure() work with resource timing entries? w3c/user-timing#27 (1 comment by @npm1)
w3c/hr-time
-
1 issue opened.
-
Gate Timestamps behind existing permission prompts w3c/hr-time#64, by @pes10k.
-
-
2 issues received 7 new comments.
-
Gate Timestamps behind existing permission prompts w3c/hr-time#64 (5 comments by @noncombatant, @pes10k, @psnyde2, @tomrittervg, @yoavweiss)
-
w3c/network-error-logging
-
1 pull request opened.
-
Use example IP addresses from RFC5737 and RFC3849. w3c/network-error-logging#110, by @jyasskin.
-
TR publications
-
2 documents published.
-
User Timing published as a Recommendation. History of User Timing
-
User Timing Level 2 published as a Recommendation. History of User Timing Level 2
-
Participants
-
1 organization joined.
-
Shopify joined.
-
GitHub
w3c/network-error-logging
-
4 issues opened.
-
Are user initiated aborts a network failure? w3c/network-error-logging#108, by @igrigorik.
-
Disallow "hop-by-hop" headers in `request_headers` and `response_headers` w3c/network-error-logging#107, by @chlily1.
-
Clear report body fields based on `phase` and report destination w3c/network-error-logging#105, by @chlily1.
-
Update editors w3c/network-error-logging#104, by @jyasskin.
-
-
1 issue closed.
-
Update editors w3c/network-error-logging#104.
-
-
2 issues received 13 new comments.
-
Are user initiated aborts a network failure? w3c/network-error-logging#108 (12 comments by @chlily1, @igrigorik, @MattMenke2)
-
Spec exceeds the scope of network error logging. w3c/network-error-logging#101 (1 comment by @jyasskin)
-
-
2 pull requests opened.
-
Export "NEL policy" w3c/network-error-logging#109, by @horo-t.
-
Update dcreager's affiliation w3c/network-error-logging#106, by @dcreager.
-
-
2 pull requests merged.
-
Update dcreager's affiliation w3c/network-error-logging#106.
-
Introduce a new algorithm "Deliver a network report". w3c/network-error-logging#100.
-
-
1 pull request received 1 new comment.
w3c/reporting
-
3 issues opened.
-
Segfault when running bikeshed in Travis builds w3c/reporting#152, by @dcreager.
-
No definition found for "serialize json to bytes" w3c/reporting#148, by @paulmeyer90.
-
Relative URLs in endpoints configuration. w3c/reporting#147, by @koto.
-
-
1 issue closed.
-
Segfault when running bikeshed in Travis builds w3c/reporting#152.
-
-
1 issue received 1 new comment.
-
3 pull requests opened.
-
Update dcreager's affiliation w3c/reporting#151, by @dcreager.
-
Show URI Template directly for generate_test_report WebDriver command w3c/reporting#150, by @paulmeyer90.
-
skip-service-worker -> service-worker mode w3c/reporting#149, by @cvazac.
-
-
3 pull requests merged.
-
Update dcreager's affiliation w3c/reporting#151.
-
Show URI Template directly for generate_test_report WebDriver command w3c/reporting#150.
-
skip-service-worker -> service-worker mode w3c/reporting#149.
-
-
3 pull requests received 12 new comments.
-
Limit report delivery per page w3c/reporting#142 (9 comments by @dcreager, @igrigorik, @paulmeyer90)
-
Show URI Template directly for generate_test_report WebDriver command w3c/reporting#150 (1 comment by @jgraham)
-
w3c/user-timing
-
1 issue opened.
-
measure API should return null w3c/user-timing#51, by @maxlgu.
-
-
1 issue closed.
-
measure API should return null w3c/user-timing#51.
-
-
1 issue reopened.
-
Measure API: make startOrOptions nullable w3c/user-timing#48, by @npm1.
-
-
3 issues received 9 new comments.
-
Measure API: make startOrOptions nullable w3c/user-timing#48 (5 comments by @cvazac, @npm1, @philipwalton)
-
-
2 pull requests opened.
-
add npm as a co-editor w3c/user-timing#53, by @siusin.
-
Remove measureWithOptions w3c/user-timing#52, by @npm1.
-
-
3 pull requests merged.
-
add npm as a co-editor w3c/user-timing#53.
-
Remove measureWithOptions w3c/user-timing#52.
-
Sanity check for timestamps w3c/user-timing#50.
-
-
2 pull requests received 7 new comments.
w3c/event-timing
-
1 issue opened.
-
Scrolling Event w3c/event-timing#23, by @AbigailMonday.
-
-
1 issue received 1 new comment.
w3c/longtasks
-
1 issue opened.
-
Provide explanation for the 50ms threshold w3c/longtasks#59, by @marcelduran.
-
-
1 issue closed.
-
Provide explanation for the 50ms threshold w3c/longtasks#59.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Explain 50ms threshold for longtasks w3c/longtasks#60, by @npm1.
-
-
1 pull request merged.
-
Explain 50ms threshold for longtasks w3c/longtasks#60.
-
w3c/performance-timeline
-
1 issue closed.
-
PerformanceObserver's observe() should support entryType-specific parameters w3c/performance-timeline#103.
-
-
3 issues received 3 new comments.
-
PerformanceObserver's observe() should support entryType-specific parameters w3c/performance-timeline#103 (1 comment by @npm1)
-
Define buffering behaviors & hooks for queued (PerformanceObserver) entries w3c/performance-timeline#81 (1 comment by @npm1)
-
w3c/resource-timing
-
2 issues opened.
-
Timing-Allow-Origin check should be case-insensitive w3c/resource-timing#202, by @npm1.
-
Specify TAO check for 304 responses w3c/resource-timing#201, by @npm1.
-
-
2 issues closed.
-
Timing-Allow-Origin check should be case-insensitive w3c/resource-timing#202.
-
The spec uses the wrong Origin definition, and missing a note regarding TAO redirects w3c/resource-timing#195.
-
-
6 issues received 16 new comments.
-
Timing-Allow-Origin check should be case-insensitive w3c/resource-timing#202 (6 comments by @annevk, @npm1, @yoavweiss)
-
Proposal: API for exposing resource requests w3c/resource-timing#137 (5 comments by @igrigorik, @nicjansma, @npm1, @rniwa)
-
The spec uses the wrong Origin definition, and missing a note regarding TAO redirects w3c/resource-timing#195 (1 comment by @yoavweiss)
-
Expose JavaScript code caching information in PerformanceResourceTiming w3c/resource-timing#190 (1 comment by @arturjanc)
-
-
1 pull request merged.
-
Improve TAO definition w3c/resource-timing#197.
-
-
1 pull request received 4 new comments.
w3c/requestidlecallback
-
2 pull requests opened.
-
Clarify timeRemaining() algorithm. w3c/requestidlecallback#79, by @rmcilroy.
-
Better define deadline w3c/requestidlecallback#78, by @yoavweiss.
-
-
2 pull requests received 22 new comments.
-
Clarify timeRemaining() algorithm. w3c/requestidlecallback#79 (5 comments by @rmcilroy, @szager-chromium, @yoavweiss)
w3c/paint-timing
-
1 issue opened.
-
1 issue received 3 new comments.
-
surprising (if not understandable) results for first-paint when `document.visibilityState === 'hidden'` w3c/paint-timing#40 (3 comments by @mikesherov, @tdresser)
-
TR publications
-
3 documents published.
-
User Timing Level 2 published as a Proposed Recommendation. History of User Timing Level 2
-
Server Timing published as a Working Draft. History of Server Timing
-
Performance Timeline Level 2 published as a Working Draft. History of Performance Timeline Level 2
-
Participants
-
1 organization joined.
-
Apple Inc. joined.
-
GitHub
w3c/requestidlecallback
-
1 issue opened.
-
The timeRemaining language is confusing w3c/requestidlecallback#77, by @szager-chromium.
-
-
1 issue received 3 new comments.
-
"deadline" in the "start an idle period algorithm" should be defined in terms of event loop w3c/requestidlecallback#71 (3 comments by @rniwa, @yoavweiss)
-
w3c/resource-timing
-
5 issues opened.
-
Be a bit more explicit about which subresources are to be ignored from stylesheets w3c/resource-timing#200, by @npm1.
-
Handling of 0-RTT interactions w3c/resource-timing#199, by @yoavweiss.
-
Register TAO as Permanent Message Header Field Name w3c/resource-timing#198, by @plehegar.
-
The spec uses the wrong Origin definition, and missing a note regarding TAO redirects w3c/resource-timing#195, by @yoavweiss.
-
Expose JavaScript code caching information in PerformanceResourceTiming w3c/resource-timing#190, by @mathiasbynens.
-
-
2 issues closed.
-
Exposing CSS subresource URLs w3c/resource-timing#70.
-
Many of the tests are flaky w3c/resource-timing#182.
-
-
2 issues reopened.
-
Clarify cross-origin resources w3c/resource-timing#173, by @yoavweiss.
-
Exposing CSS subresource URLs w3c/resource-timing#70, by @yoavweiss.
-
-
9 issues received 38 new comments.
-
Proposal: API for exposing resource requests w3c/resource-timing#137 (11 comments by @igrigorik, @npm1, @philipwalton, @yoavweiss)
-
Exposing CSS subresource URLs w3c/resource-timing#70 (7 comments by @igrigorik, @toddreifsteck, @yoavweiss, @youennf)
-
Clarify cross-origin resources w3c/resource-timing#173 (6 comments by @annevk, @toddreifsteck, @yoavweiss)
-
Expose JavaScript code caching information in PerformanceResourceTiming w3c/resource-timing#190 (4 comments by @marcelduran, @nmckay, @rniwa, @toddreifsteck)
-
`origin-or-null` definition and TAO processing w3c/resource-timing#152 (4 comments by @marcoscaceres, @toddreifsteck, @yoavweiss)
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (1 comment by @nicjansma)
-
-
6 pull requests opened.
-
Improve TAO definition w3c/resource-timing#197, by @yoavweiss.
-
Force TAO check on all fetches, not just the last non-redirected one w3c/resource-timing#196, by @yoavweiss.
-
Prevent leaking values when TAO fails w3c/resource-timing#194, by @yoavweiss.
-
Add myself to the editors list w3c/resource-timing#193, by @yoavweiss.
-
Remove issue 27 and mark exclusion at risk w3c/resource-timing#192, by @yoavweiss.
-
HTTP over QUIC is now HTTP/3 w3c/resource-timing#191, by @LPardue.
-
-
5 pull requests merged.
-
Force TAO check on all fetches, not just the last non-redirected one w3c/resource-timing#196.
-
Prevent leaking values when TAO fails w3c/resource-timing#194.
-
HTTP over QUIC is now HTTP/3 w3c/resource-timing#191.
-
Add myself to the editors list w3c/resource-timing#193.
-
Remove issue 27 and mark exclusion at risk w3c/resource-timing#192.
-
-
2 pull requests closed.
-
Use HTML's origin serialization, add note regarding TAO and redirects w3c/resource-timing#172.
-
Remove the restriction for no-cors CSS subresources w3c/resource-timing#158.
-
-
6 pull requests received 34 new comments.
-
Force TAO check on all fetches, not just the last non-redirected one w3c/resource-timing#196 (8 comments by @npm1, @toddreifsteck, @yoavweiss)
-
Use HTML's origin serialization, add note regarding TAO and redirects w3c/resource-timing#172 (3 comments by @annevk, @yoavweiss)
-
Remove the restriction for no-cors CSS subresources w3c/resource-timing#158 (1 comment by @igrigorik)
w3c/user-timing
-
1 issue opened.
-
Measure API: make startOrOptions nullable w3c/user-timing#48, by @maxlgu.
-
-
1 issue received 9 new comments.
-
Measure API: make startOrOptions nullable w3c/user-timing#48 (9 comments by @cvazac, @maxlgu, @npm1, @tdresser)
-
-
3 pull requests opened.
-
Sanity check for timestamps w3c/user-timing#50, by @npm1.
-
Create measureWithOptions w3c/user-timing#49, by @npm1.
-
Allow PerformanceMark to be constructed w3c/user-timing#47, by @npm1.
-
-
3 pull requests merged.
-
Create measureWithOptions w3c/user-timing#49.
-
Allow PerformanceMark to be constructed w3c/user-timing#47.
-
User Timing L3 changes w3c/user-timing#46.
-
-
4 pull requests received 12 new comments.
w3c/server-timing
-
1 issue opened.
-
TAO is not fully aligned with ACAO w3c/server-timing#63, by @youennf.
-
-
1 issue closed.
-
TAO is not fully aligned with ACAO w3c/server-timing#63.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Correct encoded values in sample response body w3c/server-timing#62, by @fj.
-
-
1 pull request merged.
-
Correct encoded values in sample response body w3c/server-timing#62.
-
-
1 pull request received 6 new comments.
-
Correct encoded values in sample response body w3c/server-timing#62 (6 comments by @charmander, @cvazac, @dontcallmedom, @fj)
-
w3c/reporting
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Use Infra's definition of JSON serialization. w3c/reporting#146, by @jyasskin.
-
-
1 pull request merged.
-
Use Infra's definition of JSON serialization. w3c/reporting#146.
-
-
2 pull requests received 2 new comments.
w3c/network-error-logging
-
1 issue opened.
-
Spec exceeds the scope of network error logging. w3c/network-error-logging#101, by @MattMenke2.
-
-
1 issue received 7 new comments.
-
Signed Exchange Reporting w3c/network-error-logging#99 (7 comments by @dcreager, @horo-t, @igrigorik)
-
-
3 pull requests opened.
-
Turn on PR Preview. w3c/network-error-logging#103, by @jyasskin.
-
Export "Generate a network error report". w3c/network-error-logging#102, by @jyasskin.
-
Introduce a new algorithm "Deliver a network report". w3c/network-error-logging#100, by @horo-t.
-
-
2 pull requests merged.
-
Export "Generate a network error report". w3c/network-error-logging#102.
-
Turn on PR Preview. w3c/network-error-logging#103.
-
-
1 pull request received 13 new comments.
-
Introduce a new algorithm "Deliver a network report". w3c/network-error-logging#100 (13 comments by @dcreager, @horo-t, @igrigorik, @jyasskin)
-
w3c/paint-timing
-
2 issues opened.
-
Be more precise about first paint vs first contentful paint w3c/paint-timing#38, by @npm1.
-
supported entry types needs to be context aware w3c/paint-timing#37, by @cvazac.
-
-
1 pull request opened.
-
Wrap algorithms in div algorithms w3c/paint-timing#39, by @npm1.
-
-
1 pull request merged.
-
Wrap algorithms in div algorithms w3c/paint-timing#39.
-
w3c/longtasks
-
1 issue opened.
-
supported entry types needs to be context aware w3c/longtasks#57, by @cvazac.
-
-
1 pull request opened.
-
Wrap the long tasks algorithm in div w3c/longtasks#58, by @npm1.
-
-
1 pull request merged.
-
Wrap the long tasks algorithm in div w3c/longtasks#58.
-
w3c/navigation-timing
-
2 issues opened.
-
supported entry types needs to be context aware w3c/navigation-timing#102, by @cvazac.
-
Load event timings are not well-defined w3c/navigation-timing#101, by @yoavweiss.
-
w3c/performance-timeline
-
1 issue opened.
-
supported entry types needs to be context aware w3c/performance-timeline#113, by @cvazac.
-
-
1 pull request merged.
-
Add |type| to PerformanceObserverInit w3c/performance-timeline#112.
-
-
1 pull request received 12 new comments.
-
Add |type| to PerformanceObserverInit w3c/performance-timeline#112 (12 comments by @npm1, @yoavweiss)
-
w3c/event-timing
-
1 pull request merged.
-
Queue entries outside of the event dispatching logic w3c/event-timing#22.
-
-
1 pull request received 17 new comments.
-
Queue entries outside of the event dispatching logic w3c/event-timing#22 (17 comments by @npm1, @yoavweiss)
-