Web Performance Working Group - Activity in 2018
No matches.
Participants
-
1 participant joined.
-
Dominic Farolino (Google LLC) joined.
-
GitHub
w3c/requestidlecallback
-
1 issue received 2 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, @yoavweiss)
-
w3c/network-error-logging
-
1 issue opened.
-
Signed Exchange Reporting w3c/network-error-logging#99, by @horo-t.
-
-
2 issues received 7 new comments.
-
Signed Exchange Reporting w3c/network-error-logging#99 (4 comments by @dcreager, @horo-t, @igrigorik)
-
Should reports have 'phase' property? w3c/network-error-logging#94 (3 comments by @dcreager, @ScottHelme)
-
w3c/resource-timing
-
3 issues opened.
-
Test multiple DNS responses and connection failures w3c/resource-timing#188, by @yoavweiss.
-
Test domainLookup values in the connection coalescing case w3c/resource-timing#186, by @yoavweiss.
-
Many of the tests are flaky w3c/resource-timing#182, by @yoavweiss.
-
-
5 issues closed.
-
DNS lookups can occur even when reusing a connection w3c/resource-timing#160.
-
Navigation Preload can have negative times w3c/resource-timing#139.
-
TFO and secureConnectionStart w3c/resource-timing#120.
-
How do dns and connectStart handle multiple ip/name options? w3c/resource-timing#123.
-
Ensure that first byte measurement and 1XX responses are covered by tests w3c/resource-timing#87.
-
-
10 issues received 17 new comments.
-
Ensure that first byte measurement and 1XX responses are covered by tests w3c/resource-timing#87 (4 comments by @acomminos, @yoavweiss)
-
should redirected navigations have a workerStart value if a previous redirect URL was intercepted w3c/resource-timing#118 (2 comments by @yoavweiss)
-
spec what requestStart, responseStart, and responseEnd should represent when service worker is involved w3c/resource-timing#119 (2 comments by @igrigorik, @yoavweiss)
-
How do dns and connectStart handle multiple ip/name options? w3c/resource-timing#123 (2 comments by @yoavweiss)
-
Test multiple DNS responses and connection failures w3c/resource-timing#188 (1 comment by @yoavweiss)
-
Test domainLookup values in the connection coalescing case w3c/resource-timing#186 (1 comment by @yoavweiss)
-
-
5 pull requests opened.
-
Clarify that connectStart/connectEnd refer to the latest connection retry w3c/resource-timing#189, by @yoavweiss.
-
Address the request retry case, and add a note w3c/resource-timing#187, by @yoavweiss.
-
Connection reuse does not imply DNS was not required w3c/resource-timing#185, by @yoavweiss.
-
Fix "can add entry" algorithm typo which made it incorrect w3c/resource-timing#184, by @yoavweiss.
-
Add a note regarding negative timestamps for navigation preload requests w3c/resource-timing#183, by @yoavweiss.
-
-
5 pull requests merged.
-
Connection reuse does not imply DNS was not required w3c/resource-timing#185.
-
Add a note regarding negative timestamps for navigation preload requests w3c/resource-timing#183.
-
Address the request retry case, and add a note w3c/resource-timing#187.
-
Clarify that connectStart/connectEnd refer to the latest connection retry w3c/resource-timing#189.
-
Fix "can add entry" algorithm typo which made it incorrect w3c/resource-timing#184.
-
-
4 pull requests received 17 new comments.
-
Connection reuse does not imply DNS was not required w3c/resource-timing#185 (7 comments by @cvazac, @yoavweiss)
-
Add a note regarding negative timestamps for navigation preload requests w3c/resource-timing#183 (5 comments by @cvazac, @yoavweiss)
-
Clarify that connectStart/connectEnd refer to the latest connection retry w3c/resource-timing#189 (4 comments by @igrigorik, @toddreifsteck, @yoavweiss)
-
Address the request retry case, and add a note w3c/resource-timing#187 (1 comment by @toddreifsteck)
-
w3c/navigation-timing
-
2 issues opened.
-
workerStart should be clearly defined as applicable to the last SW w3c/navigation-timing#100, by @yoavweiss.
-
workerStart should be gated on same-origin check w3c/navigation-timing#99, by @yoavweiss.
-
w3c/reporting
-
2 issues opened.
-
intervention reports do not contain id w3c/reporting#145, by @freddieleeman.
-
Please add parsing tests for Report-To w3c/reporting#141, by @annevk.
-
-
1 issue closed.
-
destination set to "" and "report" w3c/reporting#140.
-
-
3 pull requests opened.
-
Fix destination field in report delivery w3c/reporting#144, by @dcreager.
-
Change report buffer limit to enforce per report type w3c/reporting#143, by @paulmeyer90.
-
Limit report delivery per page w3c/reporting#142, by @paulmeyer90.
-
-
3 pull requests merged.
-
Change report buffer limit to enforce per report type w3c/reporting#143.
-
Fix destination field in report delivery w3c/reporting#144.
-
Add the "unresponsive" reason for crash reports. w3c/reporting#139.
-
-
1 pull request received 4 new comments.
w3c/performance-timeline
-
1 issue closed.
-
Add entryTypes method to enumerate type of entries observable via PerformanceObserver w3c/performance-timeline#77.
-
-
1 issue received 2 new comments.
-
Add entryTypes method to enumerate type of entries observable via PerformanceObserver w3c/performance-timeline#77 (2 comments by @npm1, @yoavweiss)
-
-
1 pull request opened.
-
Add |type| to PerformanceObserverInit w3c/performance-timeline#112, by @npm1.
-
-
1 pull request received 31 new comments.
-
Add |type| to PerformanceObserverInit w3c/performance-timeline#112 (31 comments by @igrigorik, @marcoscaceres, @npm1, @yoavweiss)
-
w3c/user-timing
-
1 pull request opened.
-
User Timing L3 changes w3c/user-timing#46, by @npm1.
-
-
1 pull request received 25 new comments.
-
User Timing L3 changes w3c/user-timing#46 (25 comments by @igrigorik, @npm1, @philipwalton, @siusin)
-
w3c/event-timing
-
4 issues opened.
-
Specify how to report EventTiming outside of event handlers w3c/event-timing#21, by @npm1.
-
FirstInput must always be reported w3c/event-timing#20, by @npm1.
-
Specify async EventCounts updating w3c/event-timing#19, by @npm1.
-
Remove modifications to other specifications w3c/event-timing#15, by @npm1.
-
-
3 issues closed.
-
It is totally unclear what 'duration' tries to measure w3c/event-timing#6.
-
PerformanceEventTiming or PerformanceInputTiming w3c/event-timing#10.
-
Specific use cases section contains incorrect use case w3c/event-timing#11.
-
-
2 issues received 4 new comments.
-
It is totally unclear what 'duration' tries to measure w3c/event-timing#6 (3 comments by @npm1, @smaug----, @tdresser)
-
-
7 pull requests opened.
-
Queue entries outside of the event dispatching logic w3c/event-timing#22, by @npm1.
-
Update README to remove spec-like parts w3c/event-timing#18, by @npm1.
-
Use `[SameObject]` for `eventCounts` attribute w3c/event-timing#17, by @foolip.
-
Add `[Exposed=Window]` to (partial) interfaces w3c/event-timing#16, by @foolip.
-
Update gh-pages. w3c/event-timing#14, by @tdresser.
-
Event Timing HTML spec file w3c/event-timing#13, by @npm1.
-
Event Timing spec w3c/event-timing#12, by @npm1.
-
-
6 pull requests merged.
-
Update README to remove spec-like parts w3c/event-timing#18.
-
Use `[SameObject]` for `eventCounts` attribute w3c/event-timing#17.
-
Add `[Exposed=Window]` to (partial) interfaces w3c/event-timing#16.
-
Update gh-pages. w3c/event-timing#14.
-
Event Timing HTML spec file w3c/event-timing#13.
-
Event Timing spec w3c/event-timing#12.
-
-
4 pull requests received 16 new comments.
-
Queue entries outside of the event dispatching logic w3c/event-timing#22 (12 comments by @npm1, @tdresser)
-
w3c/longtasks
-
1 issue opened.
-
Typo w3c/longtasks#55, by @yoavweiss.
-
-
1 issue closed.
-
Typo w3c/longtasks#55.
-
-
1 pull request opened.
-
Do not register taskattribution w3c/longtasks#56, by @npm1.
-
-
1 pull request merged.
-
Do not register taskattribution w3c/longtasks#56.
-
w3c/hr-time
-
1 issue reopened.
-
Privacy (PING) review w3c/hr-time#20, by @plehegar.
-
-
2 issues received 3 new comments.
w3c/paint-timing
-
1 pull request opened.
-
Fix first-contentful-paint typo w3c/paint-timing#36, by @stephendonner.
-
-
1 pull request merged.
-
Fix first-contentful-paint typo w3c/paint-timing#36.
-
TR publications
-
5 documents published.
-
Navigation Timing Level 2 published twice as a Working Draft. History of Navigation Timing Level 2
-
Performance Timeline Level 2 published twice as a Working Draft. History of Performance Timeline Level 2
-
Resource Timing Level 2 published as a Working Draft. History of Resource Timing Level 2
-
Participants
-
1 organization joined.
-
Microsoft Corporation joined.
-
GitHub
w3c/resource-timing
-
3 issues opened.
-
Access to the Remote Address information w3c/resource-timing#180, by @gui-poa.
-
Meta: When should Fetch integration happen? w3c/resource-timing#179, by @yoavweiss.
-
Make TAO a subset of CORS w3c/resource-timing#178, by @yoavweiss.
-
-
9 issues closed.
-
Clarify the behavior of the SW timeline w3c/resource-timing#140.
-
Meta: When should Fetch integration happen? w3c/resource-timing#179.
-
Terminated fetch() vs Resource Timing w3c/resource-timing#161.
-
Determine whether to wait until after responseEnd to queue entry for ResourceTiming w3c/resource-timing#93.
-
Increase limit of 150 for PerformanceEntrys? w3c/resource-timing#89.
-
Clarify behavior of setResourceTimingBufferSize w3c/resource-timing#96.
-
When is resourcetimingbufferfull supposed to fire? w3c/resource-timing#141.
-
Register Timing-Allow-Origin as a header w3c/resource-timing#174.
-
-
14 issues received 39 new comments.
-
Exposing CSS subresource URLs w3c/resource-timing#70 (10 comments by @domenic, @yoavweiss, @youennf)
-
Access to the Remote Address information w3c/resource-timing#180 (4 comments by @gui-poa, @igrigorik)
-
Clarify the behavior of the SW timeline w3c/resource-timing#140 (4 comments by @igrigorik, @yoavweiss)
-
should redirected navigations have a workerStart value if a previous redirect URL was intercepted w3c/resource-timing#118 (2 comments by @igrigorik, @yoavweiss)
-
Determine whether to wait until after responseEnd to queue entry for ResourceTiming w3c/resource-timing#93 (2 comments by @igrigorik, @yoavweiss)
-
Allow semi-wildcard `Timing-Allow-Origin` values (for subdomains) w3c/resource-timing#175 (2 comments by @cvazac, @toddreifsteck)
-
Ensure that first byte measurement and 1XX responses are covered by tests w3c/resource-timing#87 (1 comment by @yoavweiss)
-
-
1 pull request opened.
-
Register entry type "resource" w3c/resource-timing#181, by @npm1.
-
-
4 pull requests merged.
-
Register entry type "resource" w3c/resource-timing#181.
-
Fire `resourcetimingbufferfull` asynchronously - alternative approach w3c/resource-timing#168.
-
Better define which entries are exposed for nested contexts w3c/resource-timing#177.
-
add iana consideration section w3c/resource-timing#176.
-
-
1 pull request closed.
-
Fire `resourcetimingbufferfull` asynchronously w3c/resource-timing#163.
-
-
5 pull requests received 82 new comments.
-
Better define which entries are exposed for nested contexts w3c/resource-timing#177 (37 comments by @annevk, @bzbarsky, @domenic, @yoavweiss)
-
Fire `resourcetimingbufferfull` asynchronously - alternative approach w3c/resource-timing#168 (36 comments by @mstange, @npm1, @yoavweiss)
-
w3c/navigation-timing
-
2 issues opened.
-
Define attribute behavior only once w3c/navigation-timing#97, by @yoavweiss.
-
Unload event TAO check should be for all redirects w3c/navigation-timing#95, by @yoavweiss.
-
-
4 issues closed.
-
Please fix at least your broken links, if you want anyone to ever make any sense of your specs w3c/navigation-timing#65.
-
Some normative references in non-normative sections w3c/navigation-timing#89.
-
Missing word in navigationStart note w3c/navigation-timing#90.
-
Some links to anchors in other specs need to be fixed w3c/navigation-timing#88.
-
-
5 issues received 5 new comments.
-
Unload event TAO check should be for all redirects w3c/navigation-timing#95 (1 comment by @toddreifsteck)
-
Please fix at least your broken links, if you want anyone to ever make any sense of your specs w3c/navigation-timing#65 (1 comment by @yoavweiss)
-
Some normative references in non-normative sections w3c/navigation-timing#89 (1 comment by @yoavweiss)
-
6 pull requests opened.
-
Register entry type "navigation" w3c/navigation-timing#98, by @npm1.
-
Another broken link w3c/navigation-timing#96, by @yoavweiss.
-
Fix a bunch of href links w3c/navigation-timing#94, by @yoavweiss.
-
chore: tidy up w3c/navigation-timing#93, by @marcoscaceres.
-
Fold the secureConnectionStart processing to ResourceTiming's processing w3c/navigation-timing#92, by @yoavweiss.
-
Fixed broken links, replaced no-longer-relevant concepts w3c/navigation-timing#91, by @yoavweiss.
-
-
5 pull requests merged.
-
Register entry type "navigation" w3c/navigation-timing#98.
-
Another broken link w3c/navigation-timing#96.
-
Fix a bunch of href links w3c/navigation-timing#94.
-
chore: tidy up w3c/navigation-timing#93.
-
Fixed broken links, replaced no-longer-relevant concepts w3c/navigation-timing#91.
-
-
3 pull requests received 37 new comments.
-
Fixed broken links, replaced no-longer-relevant concepts w3c/navigation-timing#91 (35 comments by @marcoscaceres, @yoavweiss)
-
w3c/user-timing
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Register entry types w3c/user-timing#45, by @npm1.
-
-
1 pull request merged.
-
Register entry types w3c/user-timing#45.
-
-
1 pull request received 1 new comment.
w3c/longtasks
-
2 issues opened.
-
Names are inconsistent w3c/longtasks#53, by @domenic.
-
The processing model only works for iframes, not object/embed/etc. w3c/longtasks#52, by @domenic.
-
-
3 issues closed.
-
Don't talk about "frames" w3c/longtasks#46.
-
Specify Possible "Task Types" w3c/longtasks#40.
-
Change name to be less confusing w3c/longtasks#47.
-
-
3 issues received 5 new comments.
-
The processing model only works for iframes, not object/embed/etc. w3c/longtasks#52 (3 comments by @domenic, @npm1)
-
-
5 pull requests opened.
-
Register entry types w3c/longtasks#54, by @npm1.
-
Many fixes, both substantive and editorial w3c/longtasks#51, by @domenic.
-
Remove "browser" and "rendering" task types w3c/longtasks#50, by @npm1.
-
Set TaskAttributionTiming's |name| to "unknown" w3c/longtasks#49, by @npm1.
-
Remove Modifications to other specifications w3c/longtasks#48, by @npm1.
-
-
5 pull requests merged.
-
Register entry types w3c/longtasks#54.
-
Many fixes, both substantive and editorial w3c/longtasks#51.
-
Remove "browser" and "rendering" task types w3c/longtasks#50.
-
Set TaskAttributionTiming's |name| to "unknown" w3c/longtasks#49.
-
Remove Modifications to other specifications w3c/longtasks#48.
-
-
2 pull requests received 11 new comments.
w3c/paint-timing
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Register entry types w3c/paint-timing#35, by @npm1.
-
-
1 pull request merged.
-
Register entry types w3c/paint-timing#35.
-
-
1 pull request received 2 new comments.
w3c/web-performance
-
1 issue opened.
-
Put in place a process to improve link validation w3c/web-performance#26, by @yoavweiss.
-
-
1 issue closed.
-
Broken website link on github repo w3c/web-performance#21.
-
-
2 issues received 3 new comments.
-
Put in place a process to improve link validation w3c/web-performance#26 (2 comments by @marcoscaceres)
-
w3c/reporting
-
7 issues opened.
-
destination set to "" and "report" w3c/reporting#140, by @annevk.
-
Automation: Need two more steps to handle closed browsing context and user prompts w3c/reporting#137, by @Honry.
-
Privacy concerns around Crash IDs. w3c/reporting#135, by @paulmeyer90.
-
endpoints should be stateless w3c/reporting#133, by @bakulf.
-
Format of dates w3c/reporting#132, by @Martin-Pitt.
-
Reporting API should be exposed to workers w3c/reporting#131, by @bakulf.
-
-
6 issues closed.
-
Crash reports should not say they are visible to ReportingObserver w3c/reporting#117.
-
Privacy concerns around Crash IDs. w3c/reporting#135.
-
Report format for OOMs w3c/reporting#77.
-
Define crash reports w3c/reporting#56.
-
OOM reporting in "crash" report w3c/reporting#44.
-
Using JSON for header values w3c/reporting#127.
-
-
7 issues received 16 new comments.
-
Crash reports should not say they are visible to ReportingObserver w3c/reporting#117 (1 comment by @paulmeyer90)
-
3 pull requests opened.
-
Add the "unresponsive" reason for crash reports. w3c/reporting#139, by @paulmeyer90.
-
Remove Crash IDs from crash reports. w3c/reporting#136, by @paulmeyer90.
-
Remove statement that crash reports are observable from JavaScript. w3c/reporting#134, by @paulmeyer90.
-
-
2 pull requests merged.
-
Remove statement that crash reports are observable from JavaScript. w3c/reporting#134.
-
Remove Crash IDs from crash reports. w3c/reporting#136.
-
-
1 pull request received 1 new comment.
w3c/performance-timeline
-
1 issue received 1 new comment.
-
PerformanceObserver's observe() should support entryType-specific parameters w3c/performance-timeline#103 (1 comment by @yoavweiss)
-
-
1 pull request opened.
-
Add ReSpec validator support w3c/performance-timeline#111, by @marcoscaceres.
-
-
2 pull requests merged.
-
Define supportedEntryTypes w3c/performance-timeline#108.
-
Add ReSpec validator support w3c/performance-timeline#111.
-
-
2 pull requests received 55 new comments.
-
Define supportedEntryTypes w3c/performance-timeline#108 (36 comments by @igrigorik, @npm1, @rniwa, @yoavweiss)
-
Add ReSpec validator support w3c/performance-timeline#111 (19 comments by @igrigorik, @marcoscaceres, @yoavweiss)
-
w3c/event-timing
-
1 issue opened.
-
Specific use cases section contains incorrect use case w3c/event-timing#11, by @zeptonaut.
-
-
1 issue received 1 new comment.
w3c/network-error-logging
-
1 issue closed.
-
Request: Ability to Add Headers to Log w3c/network-error-logging#93.
-
-
1 pull request opened.
-
Add an explainer w3c/network-error-logging#98, by @dcreager.
-
-
2 pull requests merged.
-
Add an explainer w3c/network-error-logging#98.
-
Include custom request/response headers in reports w3c/network-error-logging#96.
-
-
2 pull requests received 6 new comments.
-
Include custom request/response headers in reports w3c/network-error-logging#96 (5 comments by @dcreager, @igrigorik)
-
w3c/beacon
-
1 issue opened.
-
When can Beacon support the GET method? w3c/beacon#64, by @berwin.
-
-
1 issue closed.
-
When can Beacon support the GET method? w3c/beacon#64.
-
-
1 issue received 2 new comments.
w3c/requestidlecallback
-
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 @rmcilroy, @rniwa, @yoavweiss)
-
-
1 pull request opened.
-
chore: remove inline markdown w3c/requestidlecallback#76, by @marcoscaceres.
-
-
1 pull request merged.
-
chore: remove inline markdown w3c/requestidlecallback#76.
-
-
1 pull request received 2 new comments.
w3c/perf-security-privacy
-
1 pull request opened.
-
chore: remove inline markdown w3c/perf-security-privacy#5, by @marcoscaceres.
-
-
1 pull request merged.
-
chore: remove inline markdown w3c/perf-security-privacy#5.
-
-
1 pull request received 3 new comments.
-
chore: remove inline markdown w3c/perf-security-privacy#5 (3 comments by @marcoscaceres, @yoavweiss)
-
w3c/hr-time
-
2 issues received 3 new comments.
-
1 pull request opened.
-
editorial: tidy + remove inline markdown w3c/hr-time#63, by @marcoscaceres.
-
-
1 pull request merged.
-
editorial: tidy + remove inline markdown w3c/hr-time#63.
-
-
1 pull request received 1 new comment.
TR publications
-
6 documents published.
-
Performance Timeline Level 2 published as a Working Draft. History of Performance Timeline Level 2
-
Server Timing published twice as a Working Draft. History of Server Timing
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Resource Timing Level 2 published twice as a Working Draft. History of Resource Timing Level 2
-
Participants
-
1 participant left.
-
Yoav Weiss (Shopify) left.
-
-
6 organizations joined.
-
360 joined.
-
Orange joined.
-
Intel Corporation joined.
-
Alibaba Group joined.
-
Airbnb Inc joined.
-
Baidu, Inc. joined.
-
GitHub
w3c/resource-timing
-
4 issues opened.
-
Allow semi-wildcard `Timing-Allow-Origin` values (for subdomains) w3c/resource-timing#175, by @jakub-g.
-
Register Timing-Allow-Origin as a header w3c/resource-timing#174, by @yoavweiss.
-
Clarify cross-origin resources w3c/resource-timing#173, by @alanwaketan.
-
Broken links in https://w3c.github.io/resource-timing/#sec-performanceresourcetiming w3c/resource-timing#167, by @miketaylr.
-
-
1 issue closed.
-
Broken links in https://w3c.github.io/resource-timing/#sec-performanceresourcetiming w3c/resource-timing#167.
-
-
8 issues received 25 new comments.
-
`origin-or-null` definition and TAO processing w3c/resource-timing#152 (10 comments by @annevk, @marcoscaceres, @yoavweiss)
-
Navigation Preload can have negative times w3c/resource-timing#139 (5 comments by @mfalken, @wanderview, @yoavweiss)
-
elaborate on `stalled` or `blocked` stage in specs w3c/resource-timing#164 (2 comments by @jasonslyvia, @yoavweiss)
-
Clarify when entry is added to performance entry buffer w3c/resource-timing#82 (1 comment by @rniwa)
-
Broken links in https://w3c.github.io/resource-timing/#sec-performanceresourcetiming w3c/resource-timing#167 (1 comment by @yoavweiss)
-
DNS lookups can occur even when reusing a connection w3c/resource-timing#160 (1 comment by @yoavweiss)
-
Would like a precise way to map PerformanceTimings to FetchEvent w3c/resource-timing#259 (1 comment by @yoavweiss)
-
-
7 pull requests opened.
-
Better define which entries are exposed for nested contexts w3c/resource-timing#177, by @yoavweiss.
-
add iana consideration section w3c/resource-timing#176, by @siusin.
-
Use HTML's origin serialization, add note regarding TAO and redirects w3c/resource-timing#172, by @yoavweiss.
-
Removed ! from performance entry buffer links w3c/resource-timing#171, by @yoavweiss.
-
editorial: update links w3c/resource-timing#170, by @marcoscaceres.
-
Add a note about "stalled" or "blocked" time w3c/resource-timing#169, by @jasonslyvia.
-
Fire `resourcetimingbufferfull` asynchronously - alternative approach w3c/resource-timing#168, by @yoavweiss.
-
-
2 pull requests merged.
-
Removed ! from performance entry buffer links w3c/resource-timing#171.
-
editorial: update links w3c/resource-timing#170.
-
-
6 pull requests received 36 new comments.
-
Use HTML's origin serialization, add note regarding TAO and redirects w3c/resource-timing#172 (12 comments by @annevk, @cvazac, @igrigorik, @yoavweiss)
-
Fire `resourcetimingbufferfull` asynchronously - alternative approach w3c/resource-timing#168 (4 comments by @igrigorik, @rniwa, @yoavweiss)
-
Add a note about "stalled" or "blocked" time w3c/resource-timing#169 (3 comments by @igrigorik, @jasonslyvia, @yoavweiss)
-
Better define which entries are exposed for nested contexts w3c/resource-timing#177 (2 comments by @yoavweiss)
w3c/hr-time
-
2 issues opened.
-
Find better sources to quote than Wikipedia w3c/hr-time#62, by @yoavweiss.
-
Security Review w3c/hr-time#60, by @toddreifsteck.
-
-
2 issues received 4 new comments.
-
1 pull request opened.
-
Editorial: fix cross refs, tidy up w3c/hr-time#61, by @marcoscaceres.
-
-
1 pull request merged.
-
Editorial: fix cross refs, tidy up w3c/hr-time#61.
-
-
1 pull request received 21 new comments.
w3c/web-performance
-
1 issue opened.
-
Convert old Respec specs to Bikeshed w3c/web-performance#25, by @toddreifsteck.
-
-
1 issue closed.
-
Coordination around Trace Context work w3c/web-performance#22.
-
-
3 issues received 5 new comments.
-
Coordination around Trace Context work w3c/web-performance#22 (3 comments by @colinbendell, @toddreifsteck, @yoavweiss)
-
w3c/longtasks
-
1 issue opened.
-
Change name to be less confusing w3c/longtasks#47, by @npm1.
-
-
3 issues received 12 new comments.
-
Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? w3c/longtasks#41 (5 comments by @igrigorik, @npm1, @philipwalton)
-
w3c/server-timing
-
1 issue opened.
-
Privacy/Security Review w3c/server-timing#61, by @toddreifsteck.
-
-
3 issues closed.
-
Limiting sever timing to secure origins w3c/server-timing#54.
-
Relax (or remove) trailer processing requirement w3c/server-timing#58.
-
Server-Timing header and opaque responses w3c/server-timing#56.
-
-
4 issues received 6 new comments.
-
Evaluate current parsing error strategy w3c/server-timing#42 (3 comments by @cvazac, @ddragana, @toddreifsteck)
-
-
2 pull requests opened.
-
Trailer processing should be optional w3c/server-timing#60, by @cvazac.
-
Specify behavior for user-agents who only support secure contexts w3c/server-timing#59, by @cvazac.
-
-
2 pull requests merged.
-
Specify behavior for user-agents who only support secure contexts w3c/server-timing#59.
-
Trailer processing should be optional w3c/server-timing#60.
-
-
1 pull request received 2 new comments.
-
Specify behavior for user-agents who only support secure contexts w3c/server-timing#59 (2 comments by @yoavweiss)
-
w3c/requestidlecallback
-
3 issues closed.
-
Missing definition for "idle time" w3c/requestidlecallback#70.
-
Spec should allow setting timeRemaining to 0 early w3c/requestidlecallback#72.
-
Should pending idle callbacks in the queue be run when the page is unloaded/backgrounded? w3c/requestidlecallback#73.
-
-
4 issues received 14 new comments.
-
"deadline" in the "start an idle period algorithm" should be defined in terms of event loop w3c/requestidlecallback#71 (8 comments by @domenic, @farre, @rmcilroy, @rniwa, @yoavweiss)
-
Missing definition for "idle time" w3c/requestidlecallback#70 (4 comments by @domenic, @rmcilroy, @yoavweiss)
-
Spec should allow setting timeRemaining to 0 early w3c/requestidlecallback#72 (1 comment by @yoavweiss)
-
Should pending idle callbacks in the queue be run when the page is unloaded/backgrounded? w3c/requestidlecallback#73 (1 comment by @philipwalton)
-
-
2 pull requests opened.
-
Hook into HTML spec. w3c/requestidlecallback#75, by @rmcilroy.
-
Allow UAs to set timeRemaining to zero if a time critical task is pending w3c/requestidlecallback#74, by @rmcilroy.
-
-
2 pull requests merged.
-
Hook into HTML spec. w3c/requestidlecallback#75.
-
Allow UAs to set timeRemaining to zero if a time critical task is pending w3c/requestidlecallback#74.
-
-
2 pull requests received 2 new comments.
-
Allow UAs to set timeRemaining to zero if a time critical task is pending w3c/requestidlecallback#74 (1 comment by @rmcilroy)
w3c/navigation-timing
-
4 issues opened.
-
Missing word in navigationStart note w3c/navigation-timing#90, by @mstange.
-
Some normative references in non-normative sections w3c/navigation-timing#89, by @mstange.
-
Some links to anchors in other specs need to be fixed w3c/navigation-timing#88, by @mstange.
-
Inconsistent implementations of navigation type in "reload the page through navigation to the same URL" scenario w3c/navigation-timing#87, by @jakub-g.
-
-
1 issue closed.
-
2 issues received 2 new comments.
-
Some links to anchors in other specs need to be fixed w3c/navigation-timing#88 (1 comment by @mstange)
-
Inconsistent implementations of navigation type in "reload the page through navigation to the same URL" scenario w3c/navigation-timing#87 (1 comment by @tdresser)
-
w3c/performance-timeline
-
1 issue opened.
-
Broken link to non-existent anchor in WebIDL spec w3c/performance-timeline#110, by @mstange.
-
-
1 issue closed.
-
Is the "Dependencies" section relevant? w3c/performance-timeline#106.
-
-
4 issues received 19 new comments.
-
PerformanceEntries are affected by backgrounded status w3c/performance-timeline#105 (12 comments by @gi11es, @igrigorik, @npm1, @tdresser, @yoavweiss, @Zizzamia)
-
Define buffering behaviors & hooks for queued (PerformanceObserver) entries w3c/performance-timeline#81 (4 comments by @igrigorik, @rniwa, @toddreifsteck, @yoavweiss)
-
Add entryTypes method to enumerate type of entries observable via PerformanceObserver w3c/performance-timeline#77 (2 comments by @bakulf, @npm1)
-
-
2 pull requests opened.
-
Fix links after dependency removal w3c/performance-timeline#109, by @yoavweiss.
-
Define supportedEntryTypes w3c/performance-timeline#108, by @npm1.
-
-
2 pull requests merged.
-
Fix links after dependency removal w3c/performance-timeline#109.
-
Remove dependencies section w3c/performance-timeline#107.
-
-
1 pull request closed.
-
Add entryType-specific parameters for observe() w3c/performance-timeline#104.
-
-
4 pull requests received 28 new comments.
-
Define supportedEntryTypes w3c/performance-timeline#108 (22 comments by @igrigorik, @npm1, @rniwa, @yoavweiss)
-
w3c/event-timing
-
1 issue opened.
-
PerformanceEventTiming or PerformanceInputTiming w3c/event-timing#10, by @mfalken.
-
w3c/network-error-logging
-
2 issues opened.
-
Use camelCase for field names w3c/network-error-logging#97, by @rniwa.
-
Should reports have 'phase' property? w3c/network-error-logging#94, by @ScottHelme.
-
-
1 issue closed.
-
Should reports have 'phase' property? w3c/network-error-logging#94.
-
-
2 issues received 2 new comments.
-
2 pull requests opened.
-
Include custom request/response headers in reports w3c/network-error-logging#96, by @dcreager.
-
Add phase to example reports w3c/network-error-logging#95, by @dcreager.
-
-
1 pull request merged.
-
Add phase to example reports w3c/network-error-logging#95.
-
-
2 pull requests received 12 new comments.
-
Include custom request/response headers in reports w3c/network-error-logging#96 (9 comments by @dcreager, @igrigorik)
-
w3c/paint-timing
-
1 issue closed.
-
Eliminate "4.1. Modifications to other specifications" w3c/paint-timing#26.
-
-
5 issues received 10 new comments.
-
Eliminate "4.1. Modifications to other specifications" w3c/paint-timing#26 (4 comments by @npm1, @tdresser, @yoavweiss)
-
Define whether clipped contents should be included in first contextual paint w3c/paint-timing#20 (1 comment by @tdresser)
-
-
2 pull requests opened.
-
Update broken link in README w3c/paint-timing#34, by @everdimension.
-
Remove "Modifications to other specifications" w3c/paint-timing#33, by @npm1.
-
-
2 pull requests merged.
-
Update broken link in README w3c/paint-timing#34.
-
Remove "Modifications to other specifications" w3c/paint-timing#33.
-
w3c/device-memory
-
1 issue opened.
-
Upper and lower bound should be UA opiniated decision, in entire text. w3c/device-memory#23, by @GrosSacASac.
-
-
1 issue closed.
-
JavaScript API support w3c/device-memory#10.
-
-
4 issues received 5 new comments.
-
Expose CPU clock speed and GPU info in the same manner as device memory w3c/device-memory#15 (2 comments by @n8schloss, @yoavweiss)
-
Upper and lower bound should be UA opiniated decision, in entire text. w3c/device-memory#23 (1 comment by @GrosSacASac)
-
Should device memory be limited to what the UA can access? w3c/device-memory#13 (1 comment by @yoavweiss)
-
w3c/reporting
-
1 issue opened.
-
Error in CSP header examples w3c/reporting#129, by @AfroThundr3007730.
-
-
2 issues closed.
-
Error in CSP header examples w3c/reporting#129.
-
Clarify that the predefined report types all use the `default` group w3c/reporting#125.
-
-
2 issues received 2 new comments.
-
2 pull requests opened.
-
Fix typos in CSP headers w3c/reporting#130, by @dcreager.
-
Clarify endpoint group used for predefined types w3c/reporting#128, by @dcreager.
-
-
3 pull requests merged.
-
Fix typos in CSP headers w3c/reporting#130.
-
Clarify endpoint group used for predefined types w3c/reporting#128.
-
Use default value for group in Automation section. w3c/reporting#124.
-
-
1 pull request received 1 new comment.
w3c/user-timing
-
2 issues received 2 new comments.
Lifecycle
-
1 charter started.
-
Chartered until 30 June 2020. Participants had to rejoin under this charter.
-
TR publications
-
5 documents published.
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Server Timing published as a Working Draft. History of Server Timing
-
Network Error Logging published as a Working Draft. History of Network Error Logging
-
Reporting API published as a Working Draft. History of Reporting API
-
Device Memory published as a First Public Working Draft. History of Device Memory
-
Participants
-
4 participants joined.
-
Gilles Dubuc (Wikimedia Foundation) joined.
-
Yoav Weiss (Shopify) joined.
-
Xiaoqian Wu (W3C) joined.
-
Yoav Weiss (Shopify) joined.
-
-
4 participants left.
-
Nick Doty (W3C Invited Experts) left.
-
Yoav Weiss (Shopify) left.
-
Xiaoqian Wu (W3C) left.
-
Philippe Le Hegaret (W3C) left.
-
-
4 organizations joined.
-
Google LLC joined.
-
Meta joined.
-
Akamai Technologies joined.
-
Mozilla Foundation joined.
-
-
21 organizations left.
-
360 left.
-
Airbnb Inc left.
-
IAB Technology Laboratory, Inc. left.
-
Orange left.
-
Baidu, Inc. left.
-
Alibaba Group left.
-
Stripe left.
-
HTML5 Converged Technology Forum left.
-
Meta left.
-
Tencent left.
-
Viacom inc. left.
-
Dynatrace LLC left.
-
Akamai Technologies left.
-
Mozilla Foundation left.
-
Apple Inc. left.
-
Intel Corporation left.
-
SOASTA left.
-
Mitsubishi Electric Corporation left.
-
Microsoft Corporation left.
-
Google LLC left.
-
OpenJS Foundation left.
-
GitHub
w3c/performance-timeline
-
2 issues received 22 new comments.
-
PerformanceObserver's observe() should support entryType-specific parameters w3c/performance-timeline#103 (21 comments by @igrigorik, @nicjansma, @npm1, @rniwa)
-
-
1 pull request opened.
-
Remove dependencies section w3c/performance-timeline#107, by @yoavweiss.
-
-
2 pull requests received 4 new comments.
-
Add entryType-specific parameters for observe() w3c/performance-timeline#104 (3 comments by @npm1, @rniwa)
-
w3c/device-memory
-
1 issue opened.
-
IANA considerations section needed w3c/device-memory#21, by @dret.
-
-
2 issues closed.
-
Square brackets inside <code> tags are URL encoded for some reason w3c/device-memory#17.
-
Spec's "this version" link is broken w3c/device-memory#8.
-
-
3 issues received 6 new comments.
-
Square brackets inside <code> tags are URL encoded for some reason w3c/device-memory#17 (1 comment by @plehegar)
-
1 pull request opened.
-
Fix typo "dividng" w3c/device-memory#22, by @Krinkle.
-
-
1 pull request merged.
-
Fix typo "dividng" w3c/device-memory#22.
-
-
1 pull request received 2 new comments.
w3c/resource-timing
-
3 issues opened.
-
Need to define an actual processing model for what things are added to resource timing and for what global w3c/resource-timing#166, by @bzbarsky.
-
Should 404 codes be considered aborts? w3c/resource-timing#165, by @npm1.
-
elaborate on `stalled` or `blocked` stage in specs w3c/resource-timing#164, by @jasonslyvia.
-
-
4 issues received 13 new comments.
-
elaborate on `stalled` or `blocked` stage in specs w3c/resource-timing#164 (6 comments by @igrigorik, @jasonslyvia, @nicjansma, @yoavweiss)
-
consider adding attributes to track Cache API performance in a service worker FetchEvent handler w3c/resource-timing#162 (4 comments by @wanderview, @yoavweiss)
-
DNS lookups can occur even when reusing a connection w3c/resource-timing#160 (2 comments by @jasonslyvia, @rniwa)
-
-
1 pull request received 31 new comments.
-
Fire `resourcetimingbufferfull` asynchronously w3c/resource-timing#163 (31 comments by @npm1, @rniwa, @yoavweiss)
-
w3c/user-timing
-
1 issue closed.
-
Using navigationStart as a measure's startTime w3c/user-timing#44.
-
-
2 issues received 3 new comments.
-
Using navigationStart as a measure's startTime w3c/user-timing#44 (2 comments by @maxlgu, @yoavweiss)
-
Should performance.measure() work with resource timing entries? w3c/user-timing#27 (1 comment by @brusinow)
-
w3c/web-performance
-
1 issue closed.
-
Update https://w3c.github.io/web-performance/specs/PageVisibility/Overview.html w3c/web-performance#23.
-
-
1 issue received 4 new comments.
-
Update https://w3c.github.io/web-performance/specs/PageVisibility/Overview.html w3c/web-performance#23 (4 comments by @plehegar, @siusin, @yoavweiss)
-
-
1 pull request opened.
-
update the status of the abandoned specs w3c/web-performance#24, by @siusin.
-
-
1 pull request merged.
-
update the status of the abandoned specs w3c/web-performance#24.
-
-
1 pull request received 7 new comments.
w3c/reporting
-
5 issues opened.
-
Using JSON for header values w3c/reporting#127, by @annevk.
-
ReportingObserver::observe() should be Promise-based w3c/reporting#126, by @bakulf.
-
Clarify that the predefined report types all use the `default` group w3c/reporting#125, by @dcreager.
-
Allow servers to specify a maximum report age? w3c/reporting#123, by @dcreager.
-
Example Report-To header has incorrect syntax w3c/reporting#121, by @ScottHelme.
-
-
1 issue closed.
-
Example Report-To header has incorrect syntax w3c/reporting#121.
-
-
4 issues received 8 new comments.
-
2 pull requests opened.
-
Use default value for group in Automation section. w3c/reporting#124, by @paulmeyer90.
-
Fix example report-to header syntax. w3c/reporting#122, by @ScottHelme.
-
-
2 pull requests merged.
-
Fix typo in crash reports w3c/reporting#116.
-
Fix example report-to header syntax. w3c/reporting#122.
-
-
1 pull request received 1 new comment.
w3c/server-timing
-
1 issue received 1 new comment.
w3c/beacon
-
1 issue opened.
-
navegator.sendBeacon cookie visibility question. w3c/beacon#63, by @easher.
-
-
1 issue closed.
-
navegator.sendBeacon cookie visibility question. w3c/beacon#63.
-
-
1 issue received 4 new comments.
w3c/charter-webperf
-
1 pull request merged.
-
incorporate AC review feedback w3c/charter-webperf#43.
-
-
1 pull request received 1 new comment.
w3c/network-error-logging
-
1 issue opened.
-
Request: Ability to Add Headers to Log w3c/network-error-logging#93, by @prabhakm.
-
-
1 issue received 3 new comments.
-
Request: Ability to Add Headers to Log w3c/network-error-logging#93 (3 comments by @dcreager, @JohnRiv)
-
TR publications
-
1 document published.
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
GitHub
w3c/resource-timing
-
1 issue opened.
-
consider adding attributes to track Cache API performance in a service worker FetchEvent handler w3c/resource-timing#162, by @wanderview.
-
-
3 issues received 13 new comments.
-
Clarify when entry is added to performance entry buffer w3c/resource-timing#82 (2 comments by @npm1, @yoavweiss)
-
consider adding attributes to track Cache API performance in a service worker FetchEvent handler w3c/resource-timing#162 (2 comments by @asutherland, @wanderview)
-
1 pull request opened.
-
Fire `resourcetimingbufferfull` asynchronously w3c/resource-timing#163, by @yoavweiss.
-
-
2 pull requests received 12 new comments.
-
Fire `resourcetimingbufferfull` asynchronously w3c/resource-timing#163 (8 comments by @npm1, @yoavweiss)
-
Remove the restriction for no-cors CSS subresources w3c/resource-timing#158 (4 comments by @rniwa, @yoavweiss)
-
w3c/device-memory
-
1 pull request closed.
-
Fix typos and minor grammar issues w3c/device-memory#16.
-
w3c/charter-webperf
-
1 pull request opened.
-
incorporate AC review feedback w3c/charter-webperf#43, by @igrigorik.
-
-
1 pull request received 8 new comments.
-
incorporate AC review feedback w3c/charter-webperf#43 (8 comments by @igrigorik, @siusin, @wseltzer, @yoavweiss)
-
w3c/longtasks
-
1 issue opened.
-
Don't talk about "frames" w3c/longtasks#46, by @domenic.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Support microtasks, rendering, and browser tasks w3c/longtasks#45, by @npm1.
-
-
1 pull request merged.
-
Support microtasks, rendering, and browser tasks w3c/longtasks#45.
-
-
1 pull request received 10 new comments.
w3c/performance-timeline
-
1 issue opened.
-
Is the "Dependencies" section relevant? w3c/performance-timeline#106, by @yoavweiss.
-
-
2 issues received 3 new comments.
-
Is the "Dependencies" section relevant? w3c/performance-timeline#106 (2 comments by @igrigorik, @marcoscaceres)
-
PerformanceEntries are affected by backgrounded status w3c/performance-timeline#105 (1 comment by @igrigorik)
-
-
1 pull request received 37 new comments.
-
Add entryType-specific parameters for observe() w3c/performance-timeline#104 (37 comments by @igrigorik, @npm1, @yoavweiss)
-
w3c/paint-timing
-
1 issue opened.
-
What is the scope of timings? w3c/paint-timing#31, by @domenic.
-
-
1 pull request opened.
-
Fixed a wrong commented code. w3c/paint-timing#32, by @berwin.
-
-
1 pull request merged.
-
Fix nits in PerformancePaintTiming and headers w3c/paint-timing#27.
-
-
1 pull request closed.
-
Fixed a wrong commented code. w3c/paint-timing#32.
-
-
2 pull requests received 2 new comments.
w3c/user-timing
-
1 issue opened.
-
Using navigationStart as a measure's startTime w3c/user-timing#44, by @paulirish.
-
-
1 issue received 8 new comments.
-
Using navigationStart as a measure's startTime w3c/user-timing#44 (8 comments by @maxlgu, @npm1, @tdresser, @yoavweiss)
-
w3c/reporting
-
2 issues opened.
-
Add "javascript error" report type? w3c/reporting#119, by @paulmeyer90.
-
Add "performance warning" report type? w3c/reporting#118, by @RByers.
-
-
3 issues closed.
-
Should ReportingObserver.observe accept a filter? w3c/reporting#46.
-
Buffer reports for handling "boot-time" with ReportingObserver? w3c/reporting#59.
-
Observe reports from JavaScript w3c/reporting#29.
-
-
7 issues received 20 new comments.
-
Add "javascript error" report type? w3c/reporting#119 (8 comments by @dcreager, @ebidel, @igrigorik, @mikewest, @RByers)
-
Add "performance warning" report type? w3c/reporting#118 (5 comments by @ebidel, @igrigorik, @spanicker, @yoavweiss)
-
Observing reports (via ReportingObserver) cross-frame w3c/reporting#74 (3 comments by @igrigorik, @paulmeyer90)
-
Use low priority task queue and add takeRecords to ReportingObserver? w3c/reporting#58 (1 comment by @RByers)
-
Buffer reports for handling "boot-time" with ReportingObserver? w3c/reporting#59 (1 comment by @RByers)
-
-
1 pull request opened.
-
Clarify note on header value interpretation w3c/reporting#120, by @mathiasbynens.
-
-
1 pull request merged.
-
Clarify note on header value interpretation w3c/reporting#120.
-
w3c/navigation-timing
-
1 pull request opened.
-
fix broken local references w3c/navigation-timing#86, by @jasonslyvia.
-
-
1 pull request merged.
-
fix broken local references w3c/navigation-timing#86.
-
-
1 pull request received 2 new comments.
w3c/network-error-logging
-
1 issue closed.
-
Need some tests w3c/network-error-logging#70.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Add extra constraints to report generation algorithm w3c/network-error-logging#91.
-
w3c/event-timing
-
1 issue opened.
-
Original Event as attribute w3c/event-timing#9, by @nicjansma.
-
w3c/web-performance
-
1 issue opened.
-
Update https://w3c.github.io/web-performance/specs/PageVisibility/Overview.html w3c/web-performance#23, by @annevk.
-
w3c/requestidlecallback
-
1 issue received 3 new comments.
-
Should pending idle callbacks in the queue be run when the page is unloaded/backgrounded? w3c/requestidlecallback#73 (3 comments by @philipwalton, @rmcilroy, @spanicker)
-
TR publications
-
3 documents published.
-
User Timing Level 2 published as a Candidate Recommendation Snapshot. History of User Timing Level 2
-
Server Timing published as a Working Draft. History of Server Timing
-
User Timing Level 2 published as a Working Draft. History of User Timing Level 2
-
GitHub
w3c/longtasks
-
1 issue closed.
-
Editorial issues with the processing model w3c/longtasks#15.
-
-
2 issues received 2 new comments.
-
2 pull requests opened.
-
Fix more editorial issues in processing model w3c/longtasks#44, by @npm1.
-
Fix some nits: linking, variables, periods w3c/longtasks#43, by @npm1.
-
-
2 pull requests merged.
-
Fix more editorial issues in processing model w3c/longtasks#44.
-
Fix some nits: linking, variables, periods w3c/longtasks#43.
-
-
2 pull requests received 11 new comments.
w3c/performance-timeline
-
2 issues opened.
-
PerformanceEntries are affected by backgrounded status w3c/performance-timeline#105, by @npm1.
-
PerformanceObserver's observe() should support entryType-specific parameters w3c/performance-timeline#103, by @npm1.
-
-
2 issues received 3 new comments.
-
Add entryTypes method to enumerate type of entries observable via PerformanceObserver w3c/performance-timeline#77 (2 comments by @igrigorik, @npm1)
-
PerformanceEntries are affected by backgrounded status w3c/performance-timeline#105 (1 comment by @tdresser)
-
-
1 pull request opened.
-
Add entryType-specific parameters for observe() w3c/performance-timeline#104, by @npm1.
-
-
1 pull request received 8 new comments.
-
Add entryType-specific parameters for observe() w3c/performance-timeline#104 (8 comments by @npm1, @tdresser)
-
w3c/hr-time
-
1 pull request opened.
-
Remove issue number from note w3c/hr-time#59, by @npm1.
-
-
1 pull request closed.
-
Remove issue number from note w3c/hr-time#59.
-
-
1 pull request received 7 new comments.
w3c/network-error-logging
-
1 issue opened.
-
Template style and status should match W3C's w3c/network-error-logging#86, by @yoavweiss.
-
-
11 issues closed.
-
Interaction with proxies w3c/network-error-logging#49.
-
Clarify when reports are sent w3c/network-error-logging#66.
-
Specify a maximum 'max-age' w3c/network-error-logging#65.
-
More scenarios w3c/network-error-logging#16.
-
Require that HTTP errors be considered failures? w3c/network-error-logging#72.
-
Other 4xx server responses when submitting errors w3c/network-error-logging#60.
-
clarify the case with overlapping origins and subdomains w3c/network-error-logging#59.
-
DNS errors? w3c/network-error-logging#48.
-
Interaction with ServiceWorker w3c/network-error-logging#54.
-
Verify "ownership" when generating include-subdomain reports w3c/network-error-logging#74.
-
Template style and status should match W3C's w3c/network-error-logging#86.
-
-
12 issues received 16 new comments.
-
Verify "ownership" when generating include-subdomain reports w3c/network-error-logging#74 (4 comments by @dcreager, @flano-yuki, @jyasskin)
-
Handle type mismatches in NEL header more gracefully w3c/network-error-logging#85 (2 comments by @dcreager, @yoavweiss)
-
Require that HTTP errors be considered failures? w3c/network-error-logging#72 (1 comment by @dcreager)
-
Other 4xx server responses when submitting errors w3c/network-error-logging#60 (1 comment by @dcreager)
-
clarify the case with overlapping origins and subdomains w3c/network-error-logging#59 (1 comment by @dcreager)
-
-
6 pull requests opened.
-
Fixed example IP addresses to conform to RFC 5737 w3c/network-error-logging#92, by @adamroach.
-
Add extra constraints to report generation algorithm w3c/network-error-logging#91, by @dcreager.
-
Remove redundant URL w3c/network-error-logging#90, by @dcreager.
-
Clean up network error reports section w3c/network-error-logging#89, by @dcreager.
-
Fix typo w3c/network-error-logging#88, by @dsanders11.
-
Update WICG references to W3C w3c/network-error-logging#87, by @dcreager.
-
-
9 pull requests merged.
-
Fixed example IP addresses to conform to RFC 5737 w3c/network-error-logging#92.
-
Remove redundant URL w3c/network-error-logging#90.
-
Require 4xx and 5xx results to be `http.error` w3c/network-error-logging#79.
-
Clean up network error reports section w3c/network-error-logging#89.
-
NEL reports are not observable w3c/network-error-logging#77.
-
Handle errors in different phases differently w3c/network-error-logging#83.
-
Fix typo w3c/network-error-logging#88.
-
Update WICG references to W3C w3c/network-error-logging#87.
-
Factor out a Concepts section w3c/network-error-logging#82.
-
-
5 pull requests received 39 new comments.
-
Handle errors in different phases differently w3c/network-error-logging#83 (35 comments by @dcreager, @jyasskin, @yoavweiss)
-
Fixed example IP addresses to conform to RFC 5737 w3c/network-error-logging#92 (1 comment by @dcreager)
-
Require 4xx and 5xx results to be `http.error` w3c/network-error-logging#79 (1 comment by @dcreager)
-
w3c/reporting
-
4 issues opened.
-
Crash reports should not say they are visible to ReportingObserver w3c/reporting#117, by @jpchase.
-
JFV reference w3c/reporting#107, by @reschke.
-
Unsigned values for IDL? w3c/reporting#105, by @dtapuska.
-
Old spec URL does not forward to new one. w3c/reporting#102, by @paulmeyer90.
-
-
9 issues closed.
-
Unsigned values for IDL? w3c/reporting#105.
-
Specify some report types to be "unobservable"? w3c/reporting#57.
-
Why is report.origin a separate field? w3c/reporting#25.
-
Endpoint groups and load balancing / failover w3c/reporting#93.
-
Migrate to WebPerf working group w3c/reporting#100.
-
JFV reference w3c/reporting#107.
-
Are report uploads supposed to send CORS preflights? w3c/reporting#41.
-
Friendly TAG Review: Thoughts on the HTTP header w3c/reporting#53.
-
Old spec URL does not forward to new one. w3c/reporting#102.
-
-
1 issue reopened.
-
Are report uploads supposed to send CORS preflights? w3c/reporting#41, by @dcreager.
-
-
9 issues received 24 new comments.
-
Are report uploads supposed to send CORS preflights? w3c/reporting#41 (7 comments by @dcreager, @estark37, @roryhewitt, @yoavweiss)
-
Crash reports should not say they are visible to ReportingObserver w3c/reporting#117 (1 comment by @jpchase)
-
-
12 pull requests opened.
-
Fix typo in crash reports w3c/reporting#116, by @jpchase.
-
Add paulmeyer as editor. w3c/reporting#115, by @paulmeyer90.
-
Add examples to report types w3c/reporting#114, by @paulmeyer90.
-
Define crash reports w3c/reporting#113, by @paulmeyer90.
-
Make |lineNumber| and |columnNumber| unsigned. w3c/reporting#112, by @paulmeyer90.
-
Make ALL formatting consistent. w3c/reporting#111, by @paulmeyer90.
-
Allow report types to customize the report URL w3c/reporting#110, by @dcreager.
-
Update formatting of field in IDLs w3c/reporting#109, by @paulmeyer90.
-
Update citation to HTTP-JFV w3c/reporting#108, by @dcreager.
-
Fix typos w3c/reporting#106, by @dsanders11.
-
Rename "report list" -> "report queue" w3c/reporting#104, by @paulmeyer90.
-
Update "WICG" -> "W3C" w3c/reporting#103, by @paulmeyer90.
-
-
13 pull requests merged.
-
Define crash reports w3c/reporting#113.
-
Add examples to report types w3c/reporting#114.
-
Add paulmeyer as editor. w3c/reporting#115.
-
Make |lineNumber| and |columnNumber| unsigned. w3c/reporting#112.
-
Make ALL formatting consistent. w3c/reporting#111.
-
Allow report types to customize the report URL w3c/reporting#110.
-
Update citation to HTTP-JFV w3c/reporting#108.
-
Clarify CORS behavior for report uploads w3c/reporting#97.
-
Rename "report list" -> "report queue" w3c/reporting#104.
-
Clarify name of "observability" property w3c/reporting#101.
-
Add notes about load balancing mechanism w3c/reporting#94.
-
Fix typos w3c/reporting#106.
-
Update "WICG" -> "W3C" w3c/reporting#103.
-
-
2 pull requests closed.
-
Update formatting of field in IDLs w3c/reporting#109.
-
Update report body IDL to use underscores w3c/reporting#95.
-
-
9 pull requests received 29 new comments.
w3c/requestidlecallback
-
1 issue opened.
-
Should pending idle callbacks in the queue be run when the page is unloaded/backgrounded? w3c/requestidlecallback#73, by @philipwalton.
-
-
1 issue received 1 new comment.
-
Should pending idle callbacks in the queue be run when the page is unloaded/backgrounded? w3c/requestidlecallback#73 (1 comment by @tdresser)
-
w3c/resource-timing
-
2 issues opened.
-
Terminated fetch() vs Resource Timing w3c/resource-timing#161, by @npm1.
-
DNS lookups can occur even when reusing a connection w3c/resource-timing#160, by @npm1.
-
-
1 issue received 1 new comment.
-
Would like a precise way to map PerformanceTimings to FetchEvent w3c/resource-timing#259 (1 comment by @clayw)
-
w3c/device-memory
-
1 issue closed.
-
Implementing this RFC is harmful w3c/device-memory#20.
-
-
1 issue received 1 new comment.
w3c/server-timing
-
1 issue closed.
-
clarify extraneous characters after names w3c/server-timing#51.
-
-
1 issue received 2 new comments.
-
Relax (or remove) trailer processing requirement w3c/server-timing#58 (2 comments by @cvazac, @igrigorik)
-
-
1 pull request merged.
-
Update web-platform-tests URL w3c/server-timing#57.
-
-
1 pull request received 2 new comments.
w3c/user-timing
-
1 issue opened.
-
Level 3 proposal w3c/user-timing#43, by @philipwalton.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
editorial tweak w3c/user-timing#42, by @dret.
-
-
1 pull request merged.
-
editorial tweak w3c/user-timing#42.
-
-
1 pull request received 2 new comments.
w3c/charter-webperf
-
1 pull request merged.
-
Editorial and minor substantive changes w3c/charter-webperf#42.
-
-
1 pull request received 1 new comment.
w3c/navigation-timing
-
1 issue opened.
-
Should navigationEntry's navigationType be updated according to the parent page ? w3c/navigation-timing#85, by @shacharz.
-
-
1 issue received 7 new comments.
-
Should navigationEntry's navigationType be updated according to the parent page ? w3c/navigation-timing#85 (7 comments by @igrigorik, @shacharz, @yoavweiss)
-
Participants
-
1 organization joined.
-
360 joined.
-
GitHub
w3c/server-timing
-
1 issue opened.
-
Relax (or remove) trailer processing requirement w3c/server-timing#58, by @igrigorik.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Update web-platform-tests URL w3c/server-timing#57, by @foolip.
-
w3c/network-error-logging
-
4 issues opened.
-
Handle type mismatches in NEL header more gracefully w3c/network-error-logging#85, by @dcreager.
-
Make `report_to` field optional w3c/network-error-logging#84, by @dcreager.
-
Network Error Report body fields discrepancy w3c/network-error-logging#78, by @JohnRiv.
-
Verify "ownership" when generating include-subdomain reports w3c/network-error-logging#74, by @dcreager.
-
-
3 issues closed.
-
Error reports should include HTTP verb w3c/network-error-logging#73.
-
Flag for 5xx reporting w3c/network-error-logging#58.
-
Network Error Report body fields discrepancy w3c/network-error-logging#78.
-
-
5 issues received 45 new comments.
-
Verify "ownership" when generating include-subdomain reports w3c/network-error-logging#74 (39 comments by @alvestrand, @annevk, @dcreager, @domenic, @flano-yuki, @sleevi)
-
Network Error Report body fields discrepancy w3c/network-error-logging#78 (3 comments by @dcreager, @JohnRiv)
-
Require that HTTP errors be considered failures? w3c/network-error-logging#72 (1 comment by @dcreager)
-
-
8 pull requests opened.
-
Handle errors in different phases differently w3c/network-error-logging#83, by @dcreager.
-
Factor out a Concepts section w3c/network-error-logging#82, by @dcreager.
-
Update examples to latest JSON schema w3c/network-error-logging#81, by @dcreager.
-
Add request method to report body w3c/network-error-logging#80, by @dcreager.
-
Require 4xx and 5xx results to be `http.error` w3c/network-error-logging#79, by @dcreager.
-
NEL reports are not observable w3c/network-error-logging#77, by @dcreager.
-
Refactor report definition w3c/network-error-logging#76, by @dcreager.
-
Update JSON field names to use underscores instead of dashes w3c/network-error-logging#75, by @dcreager.
-
-
4 pull requests merged.
-
Add request method to report body w3c/network-error-logging#80.
-
Update examples to latest JSON schema w3c/network-error-logging#81.
-
Refactor report definition w3c/network-error-logging#76.
-
Update JSON field names to use underscores instead of dashes w3c/network-error-logging#75.
-
-
5 pull requests received 33 new comments.
-
Factor out a Concepts section w3c/network-error-logging#82 (17 comments by @dcreager, @igrigorik, @siusin, @yoavweiss)
-
Update examples to latest JSON schema w3c/network-error-logging#81 (7 comments by @dcreager, @JohnRiv)
-
w3c/reporting
-
2 issues opened.
-
Migrate to WebPerf working group w3c/reporting#100, by @dcreager.
-
Endpoint groups and load balancing / failover w3c/reporting#93, by @mnot.
-
-
6 issues closed.
-
Friendly TAG Review: UA string consistency w3c/reporting#52.
-
Friendly TAG Review: content type? w3c/reporting#51.
-
Enable reporting via meta tag (or otherwise via JS)? w3c/reporting#28.
-
Should any Report-To header clear unspecified endpoints? w3c/reporting#48.
-
"Core" report delivery and predefined report types w3c/reporting#80.
-
Consider following TAG recommendations for naming JSON fields w3c/reporting#72.
-
-
8 issues received 33 new comments.
-
Endpoint groups and load balancing / failover w3c/reporting#93 (14 comments by @annevk, @dcreager, @martinthomson, @mikewest, @mnot)
-
Friendly TAG Review: Thoughts on the HTTP header w3c/reporting#53 (9 comments by @dcreager, @hadleybeeman, @mnot, @slightlyoff, @travisleithead, @ylafon)
-
Are report uploads supposed to send CORS preflights? w3c/reporting#41 (3 comments by @dcreager, @domenic)
-
Consider following TAG recommendations for naming JSON fields w3c/reporting#72 (3 comments by @dcreager, @paulmeyer90, @RByers)
-
-
12 pull requests opened.
-
Clarify name of "observability" property w3c/reporting#101, by @dcreager.
-
Update links to JSON RFC w3c/reporting#99, by @dcreager.
-
Use real User-Agent string in examples w3c/reporting#98, by @dcreager.
-
Clarify CORS behavior for report uploads w3c/reporting#97, by @dcreager.
-
Collect current User-Agent when queueing a report w3c/reporting#96, by @dcreager.
-
Update report body IDL to use underscores w3c/reporting#95, by @dcreager.
-
Add notes about load balancing mechanism w3c/reporting#94, by @dcreager.
-
Define the "intervention" report type. w3c/reporting#92, by @paulmeyer90.
-
Add some more bikeshed links in for deprecation reports. w3c/reporting#91, by @paulmeyer90.
-
Update include-subdomains to use underscore w3c/reporting#90, by @dcreager.
-
Specify WebDriver command for testing w3c/reporting#89, by @paulmeyer90.
-
Aggregation logic w3c/reporting#88, by @paulmeyer90.
-
-
10 pull requests merged.
-
Use real User-Agent string in examples w3c/reporting#98.
-
Update links to JSON RFC w3c/reporting#99.
-
Collect current User-Agent when queueing a report w3c/reporting#96.
-
Define the MIME type in more detail. w3c/reporting#63.
-
Define the "intervention" report type. w3c/reporting#92.
-
Update include-subdomains to use underscore w3c/reporting#90.
-
Add some more bikeshed links in for deprecation reports. w3c/reporting#91.
-
Specify WebDriver command for testing w3c/reporting#89.
-
Aggregation logic w3c/reporting#88.
-
Add Deprecation IDL w3c/reporting#87.
-
-
1 pull request closed.
-
Add IDL defs for Report and ReportBodys w3c/reporting#60.
-
-
11 pull requests received 39 new comments.
-
Collect current User-Agent when queueing a report w3c/reporting#96 (11 comments by @dcreager, @igrigorik, @RByers)
-
Specify WebDriver command for testing w3c/reporting#89 (11 comments by @dcreager, @kereliuk, @paulmeyer90)
-
Add note about custom metadata and spam prevention w3c/reporting#85 (4 comments by @dcreager, @yoavweiss)
-
Update include-subdomains to use underscore w3c/reporting#90 (2 comments by @dcreager, @paulmeyer90)
-
Add some more bikeshed links in for deprecation reports. w3c/reporting#91 (1 comment by @paulmeyer90)
-
w3c/charter-webperf
-
6 pull requests opened.
-
Editorial and minor substantive changes w3c/charter-webperf#42, by @wseltzer.
-
There is no Interaction Domain w3c/charter-webperf#41, by @wseltzer.
-
Plh/admin cleanup w3c/charter-webperf#39, by @plehegar.
-
Nominating Yoav Weiss as co-chair of the group w3c/charter-webperf#38, by @igrigorik.
-
Recharter proposal: 2018-2020 w3c/charter-webperf#37, by @igrigorik.
-
-
5 pull requests merged.
-
There is no Interaction Domain w3c/charter-webperf#41.
-
Fixed FTE w3c/charter-webperf#40.
-
Plh/admin cleanup w3c/charter-webperf#39.
-
Nominating Yoav Weiss as co-chair of the group w3c/charter-webperf#38.
-
Recharter proposal: 2018-2020 w3c/charter-webperf#37.
-
-
3 pull requests received 23 new comments.
-
Recharter proposal: 2018-2020 w3c/charter-webperf#37 (13 comments by @igrigorik, @marcoscaceres, @past, @plehegar, @rniwa, @toddreifsteck)
-
Editorial and minor substantive changes w3c/charter-webperf#42 (7 comments by @igrigorik, @siusin, @wseltzer)
-
Nominating Yoav Weiss as co-chair of the group w3c/charter-webperf#38 (3 comments by @igrigorik, @plehegar, @yoavweiss)
-
w3c/resource-timing
-
1 issue closed.
-
NextHopProtocol Values w3c/resource-timing#122.
-
-
7 issues received 35 new comments.
-
NextHopProtocol Values w3c/resource-timing#122 (14 comments by @igrigorik, @LPardue, @MikeBishop, @RyanTheOptimist, @yoavweiss)
-
Clarify behavior of setResourceTimingBufferSize w3c/resource-timing#96 (9 comments by @npm1, @toddreifsteck, @wanderview, @yoavweiss)
-
Clarify when entry is added to performance entry buffer w3c/resource-timing#82 (4 comments by @npm1, @yoavweiss)
-
Clarify what constitutes a "downloadable resource" w3c/resource-timing#100 (3 comments by @igrigorik, @yoavweiss)
-
When is resourcetimingbufferfull supposed to fire? w3c/resource-timing#141 (3 comments by @npm1, @smaug----, @yoavweiss)
-
spec what requestStart, responseStart, and responseEnd should represent when service worker is involved w3c/resource-timing#119 (1 comment by @mfalken)
-
-
1 pull request merged.
-
Add nextHopProtocol HTTP/0.9 and 1.0. Link to QUIC w3c/resource-timing#159.
-
-
2 pull requests received 12 new comments.
-
Add nextHopProtocol HTTP/0.9 and 1.0. Link to QUIC w3c/resource-timing#159 (11 comments by @igrigorik, @LPardue, @MikeBishop, @yoavweiss)
-
Remove the restriction for no-cors CSS subresources w3c/resource-timing#158 (1 comment by @yoavweiss)
-
w3c/navigation-timing
-
1 issue opened.
-
secureConnectionStart definition is inconsistent with ResourceTiming w3c/navigation-timing#84, by @npm1.
-
-
3 issues received 6 new comments.
-
Please fix at least your broken links, if you want anyone to ever make any sense of your specs w3c/navigation-timing#65 (3 comments by @bzbarsky, @igrigorik, @yoavweiss)
-
Should processing model cut the steps defined by PerformanceResourceTiming? w3c/navigation-timing#78 (2 comments by @igrigorik, @yoavweiss)
-
secureConnectionStart definition is inconsistent with ResourceTiming w3c/navigation-timing#84 (1 comment by @toddreifsteck)
-
w3c/longtasks
-
2 issues opened.
-
Expose sampled call stacks w3c/longtasks#42, by @kshyju.
-
Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? w3c/longtasks#41, by @npm1.
-
-
1 issue received 1 new comment.
-
Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? w3c/longtasks#41 (1 comment by @tdresser)
-
w3c/hr-time
-
1 issue closed.
-
Reducing the precision of the DOMHighResTimeStamp resolution w3c/hr-time#56.
-
-
1 issue received 1 new comment.
-
Reducing the precision of the DOMHighResTimeStamp resolution w3c/hr-time#56 (1 comment by @yoavweiss)
-
w3c/paint-timing
-
1 issue opened.
-
Stop Monkey Patching the Event Loop processing Model w3c/paint-timing#30, by @tdresser.
-
-
1 issue closed.
-
Stop Monkey Patching the Event Loop processing Model w3c/paint-timing#30.
-
-
2 issues received 3 new comments.
-
Stop Monkey Patching the Event Loop processing Model w3c/paint-timing#30 (2 comments by @annevk, @tdresser)
-
w3c/performance-timeline
-
1 pull request opened.
-
Update web-platform-tests URL w3c/performance-timeline#102, by @foolip.
-
-
1 pull request merged.
-
Update web-platform-tests URL w3c/performance-timeline#102.
-
-
1 pull request received 1 new comment.
w3c/perf-timing-primer
-
1 pull request opened.
-
fix a typo w3c/perf-timing-primer#17, by @huangxiaolu.
-
-
1 pull request merged.
-
fix a typo w3c/perf-timing-primer#17.
-
w3c/event-timing
-
3 issues opened.
-
Consider recording event timing outside of event dispatch w3c/event-timing#8, by @tdresser.
-
Monkey patch of DOM w3c/event-timing#7, by @annevk.
-
It is totally unclear what 'duration' tries to measure w3c/event-timing#6, by @smaug----.
-
-
1 issue closed.
-
Monkey patch of DOM w3c/event-timing#7.
-
-
2 issues received 7 new comments.
-
It is totally unclear what 'duration' tries to measure w3c/event-timing#6 (5 comments by @annevk, @smaug----, @tdresser)
-
-
1 pull request opened.
-
Enable threshold customization w3c/event-timing#5, by @tdresser.
-
TR publications
-
3 documents published.
-
Resource Timing Level 2 published 3 times as a Working Draft. History of Resource Timing Level 2
-
Participants
-
1 organization joined.
-
Airbnb Inc joined.
-
-
1 organization left.
-
X left.
-
GitHub
w3c/resource-timing
-
5 issues closed.
-
Link PerformanceEntry in IDL w3c/resource-timing#107.
-
Section 5.1 Processing Model supporting text change from 'underlined' to 'in parenthesis' w3c/resource-timing#154.
-
Backport gh-pages fixes to V2 w3c/resource-timing#131.
-
InitiatorType of service worker navigation preload w3c/resource-timing#110.
-
Events don't have default actions w3c/resource-timing#148.
-
-
9 issues received 36 new comments.
-
Exposing CSS subresource URLs w3c/resource-timing#70 (19 comments by @annevk, @igrigorik, @past, @rniwa, @toddreifsteck, @wanderview, @yoavweiss)
-
Link PerformanceEntry in IDL w3c/resource-timing#107 (6 comments by @marcoscaceres, @tabatkins, @yoavweiss)
-
Section 5.1 Processing Model supporting text change from 'underlined' to 'in parenthesis' w3c/resource-timing#154 (1 comment by @nicjansma)
-
InitiatorType of service worker navigation preload w3c/resource-timing#110 (1 comment by @yoavweiss)
-
-
4 pull requests opened.
-
Add nextHopProtocol HTTP/0.9 and 1.0. Link to QUIC w3c/resource-timing#159, by @yoavweiss.
-
Remove the restriction for no-cors CSS subresources w3c/resource-timing#158, by @yoavweiss.
-
fix xref to PerformanceEntry w3c/resource-timing#157, by @marcoscaceres.
-
Fix 'underlined' -> 'in parenthesis' w3c/resource-timing#156, by @nicjansma.
-
-
4 pull requests merged.
-
Update recommended min UA Resource Timing buffer size to 250 w3c/resource-timing#155.
-
fix xref to PerformanceEntry w3c/resource-timing#157.
-
Fix 'underlined' -> 'in parenthesis' w3c/resource-timing#156.
-
Remove mention of default actions. w3c/resource-timing#150.
-
-
1 pull request closed.
-
V2 w3c/resource-timing#128.
-
-
7 pull requests received 25 new comments.
-
Update recommended min UA Resource Timing buffer size to 250 w3c/resource-timing#155 (14 comments by @igrigorik, @nicjansma, @past, @rviscomi, @toddreifsteck, @yoavweiss)
-
Add nextHopProtocol HTTP/0.9 and 1.0. Link to QUIC w3c/resource-timing#159 (4 comments by @igrigorik, @yoavweiss)
-
fix xref to PerformanceEntry w3c/resource-timing#157 (3 comments by @igrigorik, @marcoscaceres, @yoavweiss)
-
w3c/reporting
-
3 issues opened.
-
Revert "3P anonymization" w3c/reporting#81, by @igrigorik.
-
"Core" report delivery and predefined report types w3c/reporting#80, by @dcreager.
-
Report format for OOMs w3c/reporting#77, by @paulmeyer90.
-
-
5 issues closed.
-
Scope of includeSubdomains w3c/reporting#66.
-
Revert "3P anonymization" w3c/reporting#81.
-
What happens if *.foo.com and bar.foo.com configure differing endpoints? w3c/reporting#24.
-
Add priority field to endpoint tuple and client w3c/reporting#39.
-
Group clients by origin, not endpoint w3c/reporting#64.
-
-
11 issues received 35 new comments.
-
Friendly TAG Review: Thoughts on the HTTP header w3c/reporting#53 (12 comments by @dcreager, @mikewest, @mnot, @reschke, @slightlyoff, @torgo)
-
Should any Report-To header clear unspecified endpoints? w3c/reporting#48 (5 comments by @dcreager, @igrigorik)
-
Consider following TAG recommendations for naming JSON fields w3c/reporting#72 (4 comments by @mikewest, @RByers)
-
"Core" report delivery and predefined report types w3c/reporting#80 (3 comments by @dcreager, @paulmeyer90)
-
What happens if *.foo.com and bar.foo.com configure differing endpoints? w3c/reporting#24 (1 comment by @dcreager)
-
-
9 pull requests opened.
-
Add Deprecation IDL w3c/reporting#87, by @paulmeyer90.
-
Fixed up bikeshed link errors and some formatting. w3c/reporting#86, by @paulmeyer90.
-
Add note about custom metadata and spam prevention w3c/reporting#85, by @dcreager.
-
Removed aggregation logic. w3c/reporting#84, by @paulmeyer90.
-
Change |buffered| default to false. w3c/reporting#83, by @paulmeyer90.
-
Improve specification of report type filtering (ReportingObserver) w3c/reporting#82, by @paulmeyer90.
-
Updated deprecation report field names to be underscore-separated. w3c/reporting#79, by @paulmeyer90.
-
Updated deprecation report field names to be dash-separated. w3c/reporting#78, by @paulmeyer90.
-
Define the "deprecation" report type. w3c/reporting#76, by @paulmeyer90.
-
-
8 pull requests merged.
-
Fixed up bikeshed link errors and some formatting. w3c/reporting#86.
-
Improve specification of report type filtering (ReportingObserver) w3c/reporting#82.
-
Updated deprecation report field names to be underscore-separated. w3c/reporting#79.
-
Removed aggregation logic. w3c/reporting#84.
-
Change |buffered| default to false. w3c/reporting#83.
-
Add `weight` and `priority` to each endpoint w3c/reporting#70.
-
Define the "deprecation" report type. w3c/reporting#76.
-
Aggregate reports w3c/reporting#75.
-
-
2 pull requests closed.
-
Updated deprecation report field names to be dash-separated. w3c/reporting#78.
-
12 pull requests received 47 new comments.
-
Aggregate reports w3c/reporting#75 (17 comments by @clelland, @dcreager, @igrigorik, @juliatuttle, @patrickkettner, @paulmeyer90)
-
Add note about custom metadata and spam prevention w3c/reporting#85 (8 comments by @dcreager, @igrigorik, @yoavweiss)
-
Improve specification of report type filtering (ReportingObserver) w3c/reporting#82 (5 comments by @igrigorik, @paulmeyer90)
-
Define the "deprecation" report type. w3c/reporting#76 (3 comments by @igrigorik, @paulmeyer90, @RByers)
-
update explainer with an example of how to add metadata to the HTTP based reporting w3c/reporting#61 (2 comments by @dcreager, @igrigorik)
-
Updated deprecation report field names to be underscore-separated. w3c/reporting#79 (2 comments by @paulmeyer90, @RByers)
-
Updated deprecation report field names to be dash-separated. w3c/reporting#78 (1 comment by @paulmeyer90)
-
w3c/server-timing
-
1 issue opened.
-
Server-Timing header and opaque responses w3c/server-timing#56, by @youennf.
-
-
1 issue received 5 new comments.
-
Server-Timing header and opaque responses w3c/server-timing#56 (5 comments by @igrigorik, @yoavweiss, @youennf)
-
w3c/event-timing
-
1 issue closed.
-
Excluding events without listeners or default actions being executed w3c/event-timing#1.
-
-
1 issue received 1 new comment.
-
Excluding events without listeners or default actions being executed w3c/event-timing#1 (1 comment by @tdresser)
-
-
1 pull request opened.
-
Use paint time for event duration. w3c/event-timing#4, by @tdresser.
-
-
1 pull request merged.
-
Use paint time for event duration. w3c/event-timing#4.
-
-
1 pull request closed.
-
Coalesced event scenario and buffering until onload description w3c/event-timing#3.
-
-
1 pull request received 5 new comments.
-
Coalesced event scenario and buffering until onload description w3c/event-timing#3 (5 comments by @tdresser)
-
w3c/user-timing
-
2 issues opened.
-
Publish L2 CR and snapshot in v2 branch w3c/user-timing#41, by @igrigorik.
-
Define best practices for monitoring of single page apps via UT / custom Entries w3c/user-timing#40, by @igrigorik.
-
-
3 issues closed.
-
Publish L2 CR and snapshot in v2 branch w3c/user-timing#41.
-
Transition Level 2 to CR w3c/user-timing#19.
-
Existing Test gap: Verify that toJSON output is created properly w3c/user-timing#29.
-
-
3 issues received 7 new comments.
-
Existing Test gap: Verify that toJSON output is created properly w3c/user-timing#29 (4 comments by @igrigorik, @npm1, @philipwalton, @toddreifsteck)
-
w3c/charter-webperf
-
1 issue opened.
-
Streaming Resources aren't exposed effectively to the performance timeline w3c/charter-webperf#36, by @tdresser.
-
-
5 issues closed.
-
Expose Memory Pressure API? w3c/charter-webperf#33.
-
Enable developers to create and queue custom PerformanceEntry objects w3c/charter-webperf#28.
-
Improve RUM observability and monitoring of single page apps w3c/charter-webperf#27.
-
Surface blocked scroll events in Performance Timeline? w3c/charter-webperf#31.
-
Expose First Paint, First Contentful Paint, ... to developers w3c/charter-webperf#32.
-
-
8 issues received 12 new comments.
-
Could we expose browser crashes to developers? w3c/charter-webperf#29 (3 comments by @igrigorik, @tdresser, @yoavweiss)
-
Improve RUM observability and monitoring of single page apps w3c/charter-webperf#27 (1 comment by @igrigorik)
-
Surface blocked scroll events in Performance Timeline? w3c/charter-webperf#31 (1 comment by @igrigorik)
-
Enable developers to create and queue custom PerformanceEntry objects w3c/charter-webperf#28 (1 comment by @igrigorik)
-
Expose First Paint, First Contentful Paint, ... to developers w3c/charter-webperf#32 (1 comment by @igrigorik)
-
w3c/paint-timing
-
1 issue opened.
-
Clarify invisible text w3c/paint-timing#29, by @npm1.
-
-
1 issue received 5 new comments.
w3c/network-error-logging
-
1 issue received 1 new comment.
w3c/beacon
-
2 issues closed.
-
beacon-navigate is broken w3c/beacon#59.
-
Resource Timing + beacon test w3c/beacon#58.
-
-
1 issue received 1 new comment.
w3c/hr-time
-
1 issue received 2 new comments.
-
Reducing the precision of the DOMHighResTimeStamp resolution w3c/hr-time#56 (2 comments by @toddreifsteck)
-
-
1 pull request merged.
-
WindowOrWorkerGlobalScope is a mixin w3c/hr-time#58.
-
-
1 pull request received 1 new comment.
w3c/longtasks
-
1 issue received 2 new comments.
w3c/performance-timeline
-
2 issues received 3 new comments.
-
Define buffering behaviors & hooks for queued (PerformanceObserver) entries w3c/performance-timeline#81 (2 comments by @igrigorik, @toddreifsteck)
-
Add entryTypes method to enumerate type of entries observable via PerformanceObserver w3c/performance-timeline#77 (1 comment by @igrigorik)
-
-
1 pull request closed.
-
[WIP] Explain and improve PerformanceObserver ergonomics w3c/performance-timeline#95.
-
-
1 pull request received 4 new comments.
-
[WIP] Explain and improve PerformanceObserver ergonomics w3c/performance-timeline#95 (4 comments by @igrigorik, @tdresser, @toddreifsteck)
-
TR publications
-
3 documents published.
-
Resource Timing Level 2 published twice as a Working Draft. History of Resource Timing Level 2
-
User Timing Level 2 published as a Working Draft. History of User Timing Level 2
-
GitHub
w3c/reporting
-
3 issues opened.
-
Observing reports (via ReportingObserver) cross-frame w3c/reporting#74, by @paulmeyer90.
-
Custom reports w3c/reporting#73, by @paulmeyer90.
-
Consider following TAG recommendations for naming JSON fields w3c/reporting#72, by @domenic.
-
-
6 issues received 7 new comments.
-
Use low priority task queue and add takeRecords to ReportingObserver? w3c/reporting#58 (2 comments by @igrigorik, @paulmeyer90)
-
Observing reports (via ReportingObserver) cross-frame w3c/reporting#74 (1 comment by @patrickkettner)
-
Consider following TAG recommendations for naming JSON fields w3c/reporting#72 (1 comment by @domenic)
-
-
1 pull request opened.
-
Aggregate reports w3c/reporting#75, by @paulmeyer90.
-
-
1 pull request merged.
-
Add ReportingObserver w3c/reporting#47.
-
-
2 pull requests received 12 new comments.
w3c/hr-time
-
1 pull request opened.
-
WindowOrWorkerGlobalScope is a mixin w3c/hr-time#58, by @saschanaz.
-
-
1 pull request received 1 new comment.
w3c/server-timing
-
1 issue received 1 new comment.
w3c/paint-timing
-
1 issue received 3 new comments.
-
The exact timing of navigation should be defined w3c/paint-timing#19 (3 comments by @RiteshMaheshwari, @Zizzamia)
-
w3c/resource-timing
-
2 issues opened.
-
Section 5.1 Processing Model supporting text change from 'underlined' to 'in parenthesis' w3c/resource-timing#154, by @zaphodtx.
-
`origin-or-null` definition and TAO processing w3c/resource-timing#152, by @yoavweiss.
-
-
4 issues received 7 new comments.
-
Increase limit of 150 for PerformanceEntrys? w3c/resource-timing#89 (3 comments by @igrigorik, @nicjansma)
-
`origin-or-null` definition and TAO processing w3c/resource-timing#152 (2 comments by @igrigorik, @yoavweiss)
-
-
2 pull requests opened.
-
Update recommended min UA Resource Timing buffer size to 250 w3c/resource-timing#155, by @nicjansma.
-
Changes spec back to Level 2 w3c/resource-timing#153, by @nicjansma.
-
-
1 pull request merged.
-
Changes spec back to Level 2 w3c/resource-timing#153.
-
-
4 pull requests received 12 new comments.
-
Remove mention of default actions. w3c/resource-timing#150 (4 comments by @nicjansma, @siusin, @tdresser)
-
Update recommended min UA Resource Timing buffer size to 250 w3c/resource-timing#155 (3 comments by @tdresser, @yoavweiss)
-
Changes spec back to Level 2 w3c/resource-timing#153 (3 comments by @igrigorik, @nicjansma, @siusin)
-
w3c/beacon
-
1 issue opened.
-
Typo in Example 1 code w3c/beacon#61, by @zurmuehl.
-
-
1 issue closed.
-
Typo in Example 1 code w3c/beacon#61.
-
-
1 issue reopened.
-
Typo in Example 1 code w3c/beacon#61, by @marcoscaceres.
-
-
1 issue received 5 new comments.
-
1 pull request opened.
-
Fixed typos: visiblityState -> visibilityState w3c/beacon#62, by @zurmuehl.
-
-
1 pull request merged.
-
Fixed typos: visiblityState -> visibilityState w3c/beacon#62.
-
-
1 pull request received 1 new comment.
w3c/event-timing
-
2 issues opened.
-
Should we spec the buffer related APIs somewhere? w3c/event-timing#2, by @maxlgu.
-
Excluding events without listeners or default actions being executed w3c/event-timing#1, by @maxlgu.
-
-
1 pull request opened.
-
Coalesced event scenario and buffering until onload description w3c/event-timing#3, by @maxlgu.
-
w3c/performance-timeline
-
1 pull request received 2 new comments.
-
[WIP] Explain and improve PerformanceObserver ergonomics w3c/performance-timeline#95 (2 comments by @igrigorik, @tdresser)
-
w3c/user-timing
-
2 pull requests opened.
-
chore: enable pull request previews w3c/user-timing#39, by @marcoscaceres.
-
chore: user formerEditors in config w3c/user-timing#38, by @marcoscaceres.
-
-
2 pull requests merged.
-
chore: user formerEditors in config w3c/user-timing#38.
-
chore: enable pull request previews w3c/user-timing#39.
-
-
1 pull request received 2 new comments.
TR publications
-
1 document published.
-
High Resolution Time Level 2 published as a Candidate Recommendation Snapshot. History of High Resolution Time Level 2
-
GitHub
w3c/server-timing
-
2 issues opened.
-
Fetch integration is missing w3c/server-timing#55, by @annevk.
-
Limiting sever timing to secure origins w3c/server-timing#54, by @valenting.
-
-
2 issues received 16 new comments.
-
Limiting sever timing to secure origins w3c/server-timing#54 (12 comments by @annevk, @cvazac, @igrigorik, @valenting, @yoavweiss)
-
Future considerations w3c/server-timing#39 (4 comments by @bripkens, @igrigorik, @itsderek23, @MrEcho)
-
w3c/performance-timeline
-
1 pull request received 1 new comment.
-
[WIP] Explain and improve PerformanceObserver ergonomics w3c/performance-timeline#95 (1 comment by @tdresser)
-
w3c/resource-timing
-
3 issues opened.
-
Measuring things other than time w3c/resource-timing#151, by @tenderlove.
-
Critical path length? w3c/resource-timing#149, by @lencioni.
-
Events don't have default actions w3c/resource-timing#148, by @annevk.
-
-
4 issues closed.
-
Measuring things other than time w3c/resource-timing#151.
-
Clarify resourcetimingbufferfull conditions w3c/resource-timing#95.
-
initiatorType test cases w3c/resource-timing#138.
-
-
7 issues received 16 new comments.
-
When is resourcetimingbufferfull supposed to fire? w3c/resource-timing#141 (9 comments by @annevk, @igrigorik, @npm1, @rniwa)
-
setResourceTimingBufferSize should not clear "resource timing buffer full flag" when the buffer has shrunk w3c/resource-timing#145 (1 comment by @igrigorik)
-
spec what requestStart, responseStart, and responseEnd should represent when service worker is involved w3c/resource-timing#119 (1 comment by @bashi)
-
-
1 pull request opened.
-
Remove mention of default actions. w3c/resource-timing#150, by @tdresser.
-
-
1 pull request merged.
-
Clarify addition of PerformanceResourceTiming w3c/resource-timing#146.
-
-
1 pull request closed.
-
Add a note regarding navigation preload in initiatorType w3c/resource-timing#147.
-
-
3 pull requests received 26 new comments.
-
Clarify addition of PerformanceResourceTiming w3c/resource-timing#146 (14 comments by @igrigorik, @npm1, @rniwa, @Soltik, @yoavweiss)
-
Add a note regarding navigation preload in initiatorType w3c/resource-timing#147 (8 comments by @igrigorik, @yoavweiss)
-
Remove mention of default actions. w3c/resource-timing#150 (4 comments by @igrigorik, @siusin, @tdresser)
-
w3c/requestidlecallback
-
1 issue received 4 new comments.
-
Missing definition for "idle time" w3c/requestidlecallback#70 (4 comments by @domenic, @igrigorik, @rmcilroy)
-
w3c/navigation-timing
-
2 issues received 3 new comments.
-
should unloaded iframes be included in their parent document's unload duration? w3c/navigation-timing#83 (1 comment by @igrigorik)
w3c/reporting
-
1 issue opened.
-
Testing ReportingObserver in web platform tests. w3c/reporting#71, by @paulmeyer90.
-
-
1 issue received 5 new comments.
-
Testing ReportingObserver in web platform tests. w3c/reporting#71 (5 comments by @foolip, @kereliuk, @patrickkettner, @paulmeyer90, @RByers)
-
-
1 pull request received 7 new comments.
w3c/network-error-logging
-
1 issue opened.
-
Error reports should include HTTP verb w3c/network-error-logging#73, by @dcreager.
-
w3c/user-timing
-
1 issue closed.
-
1 issue received 10 new comments.
-
Update WP tests to not throw when NT1 names are used as the first arg in measure calls w3c/user-timing#36 (10 comments by @bakulf, @bzbarsky, @igrigorik, @jgraham, @marcoscaceres, @nolanlawson, @philipwalton)
-
w3c/beacon
-
2 issues opened.
-
Firefox, Chrome and Edge all fail http referrer test w3c/beacon#60, by @toddreifsteck.
-
beacon-navigate is broken w3c/beacon#59, by @toddreifsteck.
-
-
1 issue closed.
-
Firefox, Chrome and Edge all fail http referrer test w3c/beacon#60.
-
-
2 issues received 7 new comments.
w3c/hr-time
-
1 issue received 1 new comment.
-
Reducing the precision of the DOMHighResTimeStamp resolution w3c/hr-time#56 (1 comment by @plehegar)
-
-
1 pull request received 1 new comment.
TR publications
-
1 document published.
-
User Timing Level 2 published as a Working Draft. History of User Timing Level 2
-
GitHub
w3c/hr-time
-
1 issue closed.
-
Add prompt to unload test w3c/hr-time#32.
-
-
2 issues received 7 new comments.
-
Reducing the precision of the DOMHighResTimeStamp resolution w3c/hr-time#56 (6 comments by @blurbusters, @tdresser, @toddreifsteck)
-
-
1 pull request opened.
-
Add a note regarding HRT precision w3c/hr-time#57, by @plehegar.
-
-
1 pull request merged.
-
Add a note regarding HRT precision w3c/hr-time#57.
-
-
2 pull requests received 7 new comments.
-
Add a note regarding HRT precision w3c/hr-time#57 (6 comments by @igrigorik, @plehegar, @tobint, @toddreifsteck)
-
w3c/resource-timing
-
1 issue closed.
-
Clarify whether UA can clear the buffer under memory pressure w3c/resource-timing#94.
-
-
9 issues received 23 new comments.
-
When is resourcetimingbufferfull supposed to fire? w3c/resource-timing#141 (8 comments by @annevk, @igrigorik, @npm1, @smaug----)
-
`InitiatorType` should not single out XHR w3c/resource-timing#142 (6 comments by @annevk, @yoavweiss)
-
Clarify whether UA can clear the buffer under memory pressure w3c/resource-timing#94 (2 comments by @toddreifsteck, @yoavweiss)
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (2 comments by @igrigorik, @mvadu)
-
InitiatorType of service worker navigation preload w3c/resource-timing#110 (1 comment by @yoavweiss)
-
-
1 pull request opened.
-
Add a note regarding navigation preload in initiatorType w3c/resource-timing#147, by @yoavweiss.
-
-
2 pull requests received 19 new comments.
-
Clarify addition of PerformanceResourceTiming w3c/resource-timing#146 (18 comments by @igrigorik, @marcoscaceres, @npm1, @toddreifsteck, @yoavweiss)
-
w3c/reporting
-
1 issue closed.
-
General Questions with this project w3c/reporting#69.
-
-
4 issues received 11 new comments.
-
1 pull request opened.
-
Add `weight` and `priority` to each endpoint w3c/reporting#70, by @dcreager.
-
-
1 pull request merged.
-
Group endpoints by origin w3c/reporting#67.
-
-
5 pull requests received 27 new comments.
-
Add IDL defs for Report and ReportBodys w3c/reporting#60 (3 comments by @igrigorik, @patrickkettner, @RByers)
w3c/web-performance
-
1 issue opened.
-
Coordination around Trace Context work w3c/web-performance#22, by @AloisReitbauer.
-
w3c/beacon
-
1 issue opened.
-
Resource Timing + beacon test w3c/beacon#58, by @toddreifsteck.
-
w3c/user-timing
-
1 issue opened.
-
Update the introductory text to explain how this API differs from performance.now() w3c/user-timing#37, by @philipwalton.
-
-
4 issues closed.
-
Clarify what Navigation Timing entries are allowed and how to use their values w3c/user-timing#31.
-
measure() may throw InvalidAccessError w3c/user-timing#26.
-
measure() may throw SyntaxError w3c/user-timing#21.
-
-
6 issues received 13 new comments.
-
Update the introductory text to explain how this API differs from performance.now() w3c/user-timing#37 (4 comments by @philipwalton, @tobie, @toddreifsteck)
-
Existing Test gap: Verify that toJSON output is created properly w3c/user-timing#29 (3 comments by @igrigorik, @tobie)
-
Update WP tests to not throw when NT1 names are used as the first arg in measure calls w3c/user-timing#36 (3 comments by @igrigorik, @philipwalton)
-
Clarify what Navigation Timing entries are allowed and how to use their values w3c/user-timing#31 (1 comment by @igrigorik)
-
What does "navigationStart" mean as a second argument to performance.measure() in a web worker? w3c/user-timing#22 (1 comment by @igrigorik)
-
-
1 pull request merged.
-
Address outstanding L2 issues w3c/user-timing#35.
-
-
1 pull request received 27 new comments.
-
Address outstanding L2 issues w3c/user-timing#35 (27 comments by @igrigorik, @marcoscaceres, @philipwalton, @toddreifsteck)
-
w3c/performance-timeline
-
2 issues opened.
-
When a UA is under memory pressure, what the proper way to shrink buffers in timeline? w3c/performance-timeline#101, by @toddreifsteck.
-
Ensure tests are clean w3c/performance-timeline#100, by @toddreifsteck.
-
-
1 issue closed.
-
Objects with the same start time have unspecified ordering w3c/performance-timeline#99.
-
-
3 issues received 6 new comments.
-
Define buffering behaviors & hooks for queued (PerformanceObserver) entries w3c/performance-timeline#81 (4 comments by @igrigorik, @rniwa)
-
When a UA is under memory pressure, what the proper way to shrink buffers in timeline? w3c/performance-timeline#101 (1 comment by @toddreifsteck)
-
Objects with the same start time have unspecified ordering w3c/performance-timeline#99 (1 comment by @toddreifsteck)
-
w3c/navigation-timing
-
1 issue opened.
-
should unloaded iframes be included in their parent document's unload duration? w3c/navigation-timing#83, by @toddreifsteck.
-
-
1 issue closed.
-
navigationStart marked as Obsolte w3c/navigation-timing#82.
-
-
1 issue received 1 new comment.
-
Report URL in "name" attribute (instead of "document") w3c/navigation-timing#59 (1 comment by @plehegar)
-
w3c/perf-timing-primer
-
1 pull request received 2 new comments.
-
Removing unnecessary spans from example #7 w3c/perf-timing-primer#15 (2 comments by @ericduran, @marcoscaceres)
-
w3c/server-timing
-
1 issue received 2 new comments.
-
expand description field to allow json instead of just quoted-string and token w3c/server-timing#45 (2 comments by @igrigorik, @mnot)
-
-
1 pull request opened.
-
Add example with both dur and desc w3c/server-timing#53, by @paulirish.
-
-
3 pull requests merged.
-
clarify extraneous characters after names w3c/server-timing#52.
-
remove empty anchor w3c/server-timing#50.
-
Add example with both dur and desc w3c/server-timing#53.
-
-
1 pull request received 1 new comment.
w3c/longtasks
-
1 issue opened.
-
Specify Possible "Task Types" w3c/longtasks#40, by @tdresser.
-
-
1 issue received 1 new comment.
TR publications
-
1 document published.
-
Resource Hints published as a Working Draft. History of Resource Hints
-
GitHub
w3c/resource-timing
-
9 issues opened.
-
setResourceTimingBufferSize should not clear "resource timing buffer full flag" when the buffer has shrunk w3c/resource-timing#145, by @rniwa.
-
Specify which entries are removed by setResourceTimingBufferSize w3c/resource-timing#144, by @rniwa.
-
`resourcetimingbufferfull` should fire at the `Performance` EventTarget w3c/resource-timing#143, by @mnoorenberghe.
-
`InitiatorType` should not single out XHR w3c/resource-timing#142, by @yoavweiss.
-
When is resourcetimingbufferfull supposed to fire? w3c/resource-timing#141, by @smaug----.
-
Clarify the behavior of the SW timeline w3c/resource-timing#140, by @yoavweiss.
-
Navigation Preload can have negative times w3c/resource-timing#139, by @yoavweiss.
-
initiatorType test cases w3c/resource-timing#138, by @nicjansma.
-
Proposal: API for exposing resource requests w3c/resource-timing#137, by @npm1.
-
-
5 issues closed.
-
Specify which entries are removed by setResourceTimingBufferSize w3c/resource-timing#144.
-
`resourcetimingbufferfull` should fire at the `Performance` EventTarget w3c/resource-timing#143.
-
Resource Timing entries within the context of a service worker for handled requests? w3c/resource-timing#88.
-
resource timing buffer full flag should be set to true before firing resourcetimingbufferfull event w3c/resource-timing#134.
-
VIDEO tag w3c/resource-timing#130.
-
-
13 issues received 24 new comments.
-
When is resourcetimingbufferfull supposed to fire? w3c/resource-timing#141 (4 comments by @igrigorik, @npm1, @smaug----)
-
setResourceTimingBufferSize should not clear "resource timing buffer full flag" when the buffer has shrunk w3c/resource-timing#145 (2 comments by @npm1)
-
Proposal: API for exposing resource requests w3c/resource-timing#137 (2 comments by @nicjansma, @npm1)
-
Clarify resourcetimingbufferfull conditions w3c/resource-timing#95 (2 comments by @igrigorik, @smaug----)
-
Specify which entries are removed by setResourceTimingBufferSize w3c/resource-timing#144 (1 comment by @rniwa)
-
`resourcetimingbufferfull` should fire at the `Performance` EventTarget w3c/resource-timing#143 (1 comment by @mnoorenberghe)
-
Resource Timing entries within the context of a service worker for handled requests? w3c/resource-timing#88 (1 comment by @yoavweiss)
-
-
3 pull requests opened.
-
Clarify addition of PerformanceResourceTiming w3c/resource-timing#146, by @npm1.
-
Fix substeps ordering when buffer is full w3c/resource-timing#136, by @npm1.
-
Fix respec issues w3c/resource-timing#135, by @siusin.
-
-
2 pull requests merged.
-
Fix respec issues w3c/resource-timing#135.
-
Fix substeps ordering when buffer is full w3c/resource-timing#136.
-
-
3 pull requests received 16 new comments.
-
Clarify addition of PerformanceResourceTiming w3c/resource-timing#146 (2 comments by @igrigorik, @npm1)
w3c/performance-timeline
-
1 issue opened.
-
Objects with the same start time have unspecified ordering w3c/performance-timeline#99, by @tdresser.
-
-
1 issue closed.
-
Add support for flushing observer via `takeRecords()` w3c/performance-timeline#74.
-
-
2 issues received 3 new comments.
-
Add firstPaint PerformanceEntry w3c/performance-timeline#4 (2 comments by @igrigorik, @NE-SmallTown)
-
Objects with the same start time have unspecified ordering w3c/performance-timeline#99 (1 comment by @igrigorik)
-
-
1 pull request merged.
-
define PerformanceObserver#takeRecords() w3c/performance-timeline#98.
-
-
1 pull request received 6 new comments.
-
define PerformanceObserver#takeRecords() w3c/performance-timeline#98 (6 comments by @igrigorik, @npm1, @rniwa, @toddreifsteck)
-
w3c/network-error-logging
-
3 issues opened.
-
Require that HTTP errors be considered failures? w3c/network-error-logging#72, by @dcreager.
-
Move sampling rate into Reporting? w3c/network-error-logging#71, by @dcreager.
-
Need some tests w3c/network-error-logging#70, by @dcreager.
-
-
1 issue received 1 new comment.
-
Require that HTTP errors be considered failures? w3c/network-error-logging#72 (1 comment by @dcreager)
-
w3c/reporting
-
3 issues opened.
-
General Questions with this project w3c/reporting#69, by @ghost.
-
Spam avoidance mechanism w3c/reporting#68, by @dcreager.
-
Scope of includeSubdomains w3c/reporting#66, by @dcreager.
-
-
3 issues received 16 new comments.
-
Spam avoidance mechanism w3c/reporting#68 (5 comments by @bluesmoon, @dcreager, @juliatuttle, @yoavweiss)
-
1 pull request opened.
-
Group endpoints by origin w3c/reporting#67, by @dcreager.
-
-
2 pull requests received 3 new comments.
w3c/paint-timing
-
1 issue opened.
-
[Question]Some questions about the spec w3c/paint-timing#28, by @NE-SmallTown.
-
-
1 issue closed.
-
[Question]Some questions about the spec w3c/paint-timing#28.
-
-
1 issue received 13 new comments.
-
[Question]Some questions about the spec w3c/paint-timing#28 (13 comments by @igrigorik, @NE-SmallTown, @tdresser)
-
w3c/user-timing
-
1 issue opened.
-
Update WP tests to not throw when NT1 names are used as the first arg in measure calls w3c/user-timing#36, by @philipwalton.
-
-
2 issues received 2 new comments.
-
Update WP tests to not throw when NT1 names are used as the first arg in measure calls w3c/user-timing#36 (1 comment by @igrigorik)
-
-
1 pull request received 18 new comments.
-
Address outstanding L2 issues w3c/user-timing#35 (18 comments by @igrigorik, @marcoscaceres, @nolanlawson, @philipwalton)
-
w3c/server-timing
-
1 issue opened.
-
clarify extraneous characters after names w3c/server-timing#51, by @cvazac.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
clarify extraneous characters after names w3c/server-timing#52, by @cvazac.
-
remove empty anchor w3c/server-timing#50, by @cvazac.
-
-
1 pull request received 5 new comments.
w3c/navigation-timing
-
1 issue opened.
-
navigationStart marked as Obsolte w3c/navigation-timing#82, by @nicjansma.
-
-
3 issues received 7 new comments.
-
Please fix at least your broken links, if you want anyone to ever make any sense of your specs w3c/navigation-timing#65 (5 comments by @bzbarsky, @igrigorik, @plehegar)
-
w3c/hr-time
-
1 issue opened.
-
Reducing the precision of the DOMHighResTimeStamp resolution w3c/hr-time#56, by @plehegar.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Decreased DOMHighResTimeStamp resolution w3c/hr-time#55, by @plehegar.
-
-
1 pull request merged.
-
1 pull request closed.
-
Decreased DOMHighResTimeStamp resolution w3c/hr-time#55.
-
-
2 pull requests received 6 new comments.
-
Harmonized links and references, adding links to tests and issues w3c/hr-time#53 (1 comment by @siusin)
w3c/perf-timing-primer
-
1 issue opened.
-
Maybe hand this to MDN? w3c/perf-timing-primer#16, by @marcoscaceres.
-
-
1 pull request opened.
-
Removing unnecessary spans from example #7 w3c/perf-timing-primer#15, by @ericduran.
-
-
1 pull request received 1 new comment.
w3c/beacon
-
1 issue closed.
-
Tests for CORS and sendBeacon() w3c/beacon#41.
-
-
1 issue received 1 new comment.
w3c/longtasks
-
1 pull request closed.
-
No timing clamp for long tasks: index.html w3c/longtasks#33.
-
-
1 pull request received 1 new comment.