Web Performance Working Group - Activity in 2017
No matches.
TR publications
-
5 documents published.
-
Server Timing published twice as a Working Draft. History of Server Timing
-
User Timing Level 2 published twice as a Working Draft. History of User Timing Level 2
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Participants
-
1 organization joined.
-
IAB Technology Laboratory, Inc. joined.
-
GitHub
w3c/server-timing
-
5 issues opened.
-
clarify invalid params w3c/server-timing#48, by @cvazac.
-
clarify incomplete params w3c/server-timing#46, by @cvazac.
-
expand description field to allow json instead of just quoted-string and token w3c/server-timing#45, by @colinbendell.
-
add total to distinguish between calendar time and effort time w3c/server-timing#44, by @colinbendell.
-
add start time to distinguish between cached and active entries w3c/server-timing#43, by @colinbendell.
-
-
3 issues closed.
-
clarify invalid params w3c/server-timing#48.
-
clarify incomplete params w3c/server-timing#46.
-
Consider shorter names for the attributes w3c/server-timing#40.
-
-
4 issues received 14 new comments.
-
expand description field to allow json instead of just quoted-string and token w3c/server-timing#45 (4 comments by @colinbendell, @cvazac)
-
2 pull requests opened.
-
clarify processing after incomplete or invalid param w3c/server-timing#49, by @cvazac.
-
clarify duplicate param names w3c/server-timing#47, by @cvazac.
-
-
2 pull requests merged.
-
clarify processing after incomplete or invalid param w3c/server-timing#49.
-
clarify duplicate param names w3c/server-timing#47.
-
-
1 pull request received 4 new comments.
w3c/resource-timing
-
4 issues opened.
-
resource timing buffer full flag should be set to true before firing resourcetimingbufferfull event w3c/resource-timing#134, by @rniwa.
-
Resource processing time w3c/resource-timing#133, by @yoavweiss.
-
Collect initiatorType use-cases w3c/resource-timing#132, by @nicjansma.
-
Backport gh-pages fixes to V2 w3c/resource-timing#131, by @nicjansma.
-
-
1 issue closed.
-
Clarify relationship between `onload`, adding entries and their completeness w3c/resource-timing#127.
-
-
9 issues received 15 new comments.
-
Clarify relationship between `onload`, adding entries and their completeness w3c/resource-timing#127 (1 comment by @yoavweiss)
-
Resource Timing entries within the context of a service worker for handled requests? w3c/resource-timing#88 (1 comment by @yoavweiss)
w3c/user-timing
-
1 issue closed.
-
Fix respec warnings and processing w3c/user-timing#32.
-
-
4 issues received 8 new comments.
-
What does "navigationStart" mean as a second argument to performance.measure() in a web worker? w3c/user-timing#22 (3 comments by @philipwalton, @tdresser)
-
Fix respec warnings and processing w3c/user-timing#32 (3 comments by @marcoscaceres, @philipwalton, @tdresser)
-
Existing Test gap: Verify that toJSON output is created properly w3c/user-timing#29 (1 comment by @npm1)
-
-
3 pull requests opened.
-
Address outstanding L2 issues w3c/user-timing#35, by @philipwalton.
-
Editorial: clean up example a bit w3c/user-timing#34, by @marcoscaceres.
-
Fix ReSpec warnings w3c/user-timing#33, by @tdresser.
-
-
2 pull requests merged.
-
Editorial: clean up example a bit w3c/user-timing#34.
-
Fix ReSpec warnings w3c/user-timing#33.
-
-
1 pull request closed.
-
Clarify that measure() may throw a SyntaxError w3c/user-timing#30.
-
-
3 pull requests received 8 new comments.
-
Editorial: clean up example a bit w3c/user-timing#34 (5 comments by @marcoscaceres, @philipwalton, @siusin)
-
w3c/navigation-timing
-
1 issue opened.
-
Navigation Timing should be exposed in the Worker context w3c/navigation-timing#81, by @yoavweiss.
-
-
3 issues closed.
-
IDL should xref PerformanceResourceTiming w3c/navigation-timing#64.
-
Navigation Timing should be exposed in the Worker context w3c/navigation-timing#81.
-
Timings for beforeUnload event w3c/navigation-timing#79.
-
-
5 issues received 10 new comments.
-
Timings for beforeUnload event w3c/navigation-timing#79 (4 comments by @andydavies, @igrigorik, @toddreifsteck)
-
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 @igrigorik, @marcoscaceres)
-
Should processing model cut the steps defined by PerformanceResourceTiming? w3c/navigation-timing#78 (1 comment by @igrigorik)
-
Navigation Timing should be exposed in the Worker context w3c/navigation-timing#81 (1 comment by @igrigorik)
-
-
1 pull request received 1 new comment.
w3c/hr-time
-
1 pull request merged.
-
Update spec to fix ambiguity around Time Origin definition. w3c/hr-time#54.
-
-
2 pull requests received 14 new comments.
-
Harmonized links and references, adding links to tests and issues w3c/hr-time#53 (12 comments by @marcoscaceres, @plehegar)
-
Update spec to fix ambiguity around Time Origin definition. w3c/hr-time#54 (2 comments by @divmain, @igrigorik)
-
w3c/longtasks
-
1 issue closed.
-
remove index.html in the master branch w3c/longtasks#35.
-
-
1 issue received 3 new comments.
-
2 pull requests opened.
-
remove index.html in master branch w3c/longtasks#39, by @siusin.
-
Update bikeshed w3c/longtasks#38, by @tdresser.
-
-
1 pull request merged.
-
remove index.html in master branch w3c/longtasks#39.
-
-
1 pull request closed.
-
Update bikeshed w3c/longtasks#38.
-
-
1 pull request received 4 new comments.
w3c/device-memory
-
1 issue opened.
-
Implementing this RFC is harmful w3c/device-memory#20, by @KOLANICH.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Add remark about lower/upper bounds changeability w3c/device-memory#19.
-
-
1 pull request received 2 new comments.
w3c/performance-timeline
-
1 pull request opened.
-
define PerformanceObserver#takeRecords() w3c/performance-timeline#98, by @igrigorik.
-
-
1 pull request closed.
-
Add takeRecords() to PerformanceObserver w3c/performance-timeline#97.
-
-
2 pull requests received 16 new comments.
-
define PerformanceObserver#takeRecords() w3c/performance-timeline#98 (13 comments by @igrigorik, @npm1, @tdresser)
-
Add takeRecords() to PerformanceObserver w3c/performance-timeline#97 (3 comments by @igrigorik, @npm1)
-
w3c/reporting
-
2 issues received 9 new comments.
-
Friendly TAG Review: service worker integration w3c/reporting#50 (7 comments by @andypaicu, @igrigorik, @juliatuttle, @mikewest, @nicjansma)
-
Specify some report types to be "unobservable"? w3c/reporting#57 (2 comments by @igrigorik, @mikewest)
-
-
1 pull request opened.
-
Add ReportingObserver w3c/reporting#65, by @paulmeyer90.
-
-
1 pull request closed.
-
Add ReportingObserver w3c/reporting#65.
-
w3c/network-error-logging
-
4 issues closed.
-
missing reference and broken links in 2.4 w3c/network-error-logging#56.
-
broken link on is-origin-trustworthy in 2.2.1.1 w3c/network-error-logging#57.
-
Define NEL on top of Reporting API w3c/network-error-logging#67.
-
Update spec to use respec reference best practices w3c/network-error-logging#68.
-
-
4 issues received 4 new comments.
-
broken link on is-origin-trustworthy in 2.2.1.1 w3c/network-error-logging#57 (1 comment by @igrigorik)
-
Update spec to use respec reference best practices w3c/network-error-logging#68 (1 comment by @igrigorik)
-
1 pull request merged.
-
Add successes and sampling rates w3c/network-error-logging#63.
-
-
1 pull request received 2 new comments.
w3c/paint-timing
-
1 issue opened.
-
Eliminate "4.1. Modifications to other specifications" w3c/paint-timing#26, by @tdresser.
-
-
1 issue received 5 new comments.
-
1 pull request opened.
-
Fix nits in PerformancePaintTiming and headers w3c/paint-timing#27, by @npm1.
-
-
1 pull request received 1 new comment.
TR publications
-
2 documents published.
-
Server Timing published twice as a Working Draft. History of Server Timing
-
GitHub
w3c/paint-timing
-
4 issues opened.
-
Add a note in spec about cross-origin check w3c/paint-timing#23, by @spanicker.
-
Clarify handling of child iframes w3c/paint-timing#22, by @npm1.
-
Define whether clipped contents should be included in first contextual paint w3c/paint-timing#20, by @rniwa.
-
The exact timing of navigation should be defined w3c/paint-timing#19, by @rniwa.
-
-
3 issues closed.
-
Add a note in spec about cross-origin check w3c/paint-timing#23.
-
DOMHighResTimeStamp should link w3c/paint-timing#8.
-
Clarify handling of child iframes w3c/paint-timing#22.
-
-
2 issues received 5 new comments.
-
Add a note in spec about cross-origin check w3c/paint-timing#23 (3 comments by @npm1, @spanicker, @tdresser)
-
-
3 pull requests opened.
-
Fix unlinked DOMHighResTimeStamp w3c/paint-timing#25, by @npm1.
-
Clarify iframes in PaintTiming w3c/paint-timing#24, by @npm1.
-
Use sentence case in headers w3c/paint-timing#21, by @npm1.
-
-
3 pull requests merged.
-
Fix unlinked DOMHighResTimeStamp w3c/paint-timing#25.
-
Clarify iframes in PaintTiming w3c/paint-timing#24.
-
Use sentence case in headers w3c/paint-timing#21.
-
-
3 pull requests received 6 new comments.
w3c/longtasks
w3c/reporting
-
5 issues opened.
-
Group clients by origin, not endpoint w3c/reporting#64, by @juliatuttle.
-
Reports compression w3c/reporting#62, by @yoavweiss.
-
Buffer reports for handling "boot-time" with ReportingObserver? w3c/reporting#59, by @RByers.
-
Use low priority task queue and add takeRecords to ReportingObserver? w3c/reporting#58, by @RByers.
-
Specify some report types to be "unobservable"? w3c/reporting#57, by @RByers.
-
-
1 issue closed.
-
Default value for max-age? w3c/reporting#32.
-
-
16 issues received 36 new comments.
-
Friendly TAG Review: content type? w3c/reporting#51 (6 comments by @mikewest, @mnot, @patrickkettner, @travisleithead)
-
Buffer reports for handling "boot-time" with ReportingObserver? w3c/reporting#59 (5 comments by @patrickkettner, @RByers)
-
Add priority field to endpoint tuple and client w3c/reporting#39 (2 comments by @juliatuttle, @patrickkettner)
-
Should ReportingObserver.observe accept a filter? w3c/reporting#46 (2 comments by @patrickkettner, @RByers)
-
Friendly TAG Review: service worker integration w3c/reporting#50 (2 comments by @patrickkettner, @RByers)
-
Should any Report-To header clear unspecified endpoints? w3c/reporting#48 (1 comment by @juliatuttle)
-
What happens if *.foo.com and bar.foo.com configure differing endpoints? w3c/reporting#24 (1 comment by @patrickkettner)
-
GCing an active but failing endpoint is counterproductive w3c/reporting#23 (1 comment by @patrickkettner)
-
Use low priority task queue and add takeRecords to ReportingObserver? w3c/reporting#58 (1 comment by @patrickkettner)
-
reporting of metadata such as browser engine+version or other metadata chosen by page? w3c/reporting#49 (1 comment by @patrickkettner)
-
-
3 pull requests opened.
-
Define the MIME type in more detail. w3c/reporting#63, by @mikewest.
-
Add IDL defs for Report and ReportBodys w3c/reporting#60, by @patrickkettner.
-
-
2 pull requests received 7 new comments.
w3c/navigation-timing
-
3 issues opened.
-
Timings for beforeUnload event w3c/navigation-timing#79, by @andydavies.
-
Should processing model cut the steps defined by PerformanceResourceTiming? w3c/navigation-timing#78, by @toddreifsteck.
-
Fix ReSpec warnings on GitHub spec w3c/navigation-timing#77, by @igrigorik.
-
-
1 issue closed.
-
Fix ReSpec warnings on GitHub spec w3c/navigation-timing#77.
-
-
4 issues received 12 new comments.
-
Timings for beforeUnload event w3c/navigation-timing#79 (5 comments by @andydavies, @cvazac, @nicjansma, @yoavweiss)
-
Fix ReSpec warnings on GitHub spec w3c/navigation-timing#77 (5 comments by @igrigorik, @marcoscaceres, @siusin)
-
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 @toddreifsteck)
-
-
1 pull request opened.
-
Fix ReSpec issues w3c/navigation-timing#80, by @marcoscaceres.
-
-
1 pull request merged.
-
Fix ReSpec issues w3c/navigation-timing#80.
-
-
1 pull request received 10 new comments.
w3c/requestidlecallback
-
3 issues opened.
-
Spec should allow setting timeRemaining to 0 early w3c/requestidlecallback#72, by @esprehn.
-
"deadline" in the "start an idle period algorithm" should be defined in terms of event loop w3c/requestidlecallback#71, by @rniwa.
-
Missing definition for "idle time" w3c/requestidlecallback#70, by @siusin.
-
-
3 issues received 9 new comments.
-
Missing definition for "idle time" w3c/requestidlecallback#70 (5 comments by @domenic, @igrigorik, @rmcilroy, @toddreifsteck)
-
"deadline" in the "start an idle period algorithm" should be defined in terms of event loop w3c/requestidlecallback#71 (2 comments by @rmcilroy, @rniwa)
-
Allow requesting a minimum time budget w3c/requestidlecallback#49 (2 comments by @cramforce, @farre)
-
w3c/performance-timeline
-
4 issues closed.
-
Step 1 of observe() gets an entryTypes sequence from ... where? w3c/performance-timeline#90.
-
Does PerformanceObserverInit's entryTypes contain types or names? w3c/performance-timeline#91.
-
observe() step 3 is confused about what objects it's manipulating w3c/performance-timeline#93.
-
Steps 3 and 4 of observe() aren't clear about what list is being considered w3c/performance-timeline#94.
-
-
1 pull request opened.
-
Add takeRecords() to PerformanceObserver w3c/performance-timeline#97, by @npm1.
-
-
1 pull request merged.
-
Improve observe() logic and references w3c/performance-timeline#96.
-
-
1 pull request closed.
-
Fix auto-publish w3c/performance-timeline#84.
-
-
3 pull requests received 12 new comments.
-
Add takeRecords() to PerformanceObserver w3c/performance-timeline#97 (6 comments by @npm1, @spanicker, @tdresser)
-
Improve observe() logic and references w3c/performance-timeline#96 (5 comments by @bzbarsky, @igrigorik)
-
w3c/hr-time
-
2 pull requests opened.
-
Update spec to fix ambiguity around Time Origin definition. w3c/hr-time#54, by @divmain.
-
Harmonized links and references, adding links to tests and issues w3c/hr-time#53, by @plehegar.
-
-
1 pull request reopened.
-
Update spec to fix ambiguity around Time Origin definition. w3c/hr-time#54, by @divmain.
-
-
1 pull request received 3 new comments.
-
Harmonized links and references, adding links to tests and issues w3c/hr-time#53 (3 comments by @marcoscaceres, @plehegar)
-
w3c/resource-timing
-
4 issues opened.
-
VIDEO tag w3c/resource-timing#130, by @nicjansma.
-
Unusual RT timings in IE & Edge w3c/resource-timing#129, by @fshort.
-
Clarify relationship between `onload`, adding entries and their completeness w3c/resource-timing#127, by @yoavweiss.
-
Review that Resource Timing 2 language works for QUIC w3c/resource-timing#126, by @toddreifsteck.
-
-
1 issue closed.
-
Unusual RT timings in IE & Edge w3c/resource-timing#129.
-
-
11 issues received 22 new comments.
-
spec what requestStart, responseStart, and responseEnd should represent when service worker is involved w3c/resource-timing#119 (4 comments by @mfalken, @wanderview)
-
NextHopProtocol Values w3c/resource-timing#122 (4 comments by @plehegar, @RyanTheOptimist, @sleevi, @toddreifsteck)
-
Unusual RT timings in IE & Edge w3c/resource-timing#129 (3 comments by @fshort, @plehegar, @toddreifsteck)
-
Clarify what constitutes a "downloadable resource" w3c/resource-timing#100 (2 comments by @JosephPecoraro, @toddreifsteck)
-
Determine whether to wait until after responseEnd to queue entry for ResourceTiming w3c/resource-timing#93 (1 comment by @yoavweiss)
-
How do dns and connectStart handle multiple ip/name options? w3c/resource-timing#123 (1 comment by @toddreifsteck)
-
InitiatorType of service worker navigation preload w3c/resource-timing#110 (1 comment by @toddreifsteck)
-
Ensure that first byte measurement and 1XX responses are covered by tests w3c/resource-timing#87 (1 comment by @toddreifsteck)
-
-
1 pull request opened.
-
V2 w3c/resource-timing#128, by @DharshanJS.
-
w3c/device-memory
-
1 issue opened.
-
Square brackets inside <code> tags are URL encoded for some reason w3c/device-memory#17, by @jdanford.
-
-
2 pull requests opened.
-
Add remark about lower/upper bounds changeability w3c/device-memory#19, by @tomayac.
-
Remove duplicated word w3c/device-memory#18, by @inexorabletash.
-
-
1 pull request merged.
-
Remove duplicated word w3c/device-memory#18.
-
-
2 pull requests received 3 new comments.
w3c/server-timing
-
3 issues opened.
-
Evaluate current parsing error strategy w3c/server-timing#42, by @cvazac.
-
Consider shorter names for the attributes w3c/server-timing#40, by @yoavweiss.
-
Future considerations w3c/server-timing#39, by @cvazac.
-
-
4 issues closed.
-
Incorporating feedback from TAG review w3c/server-timing#32.
-
Link to a defined extension hook in Resource Timing & Nav Timing w3c/server-timing#19.
-
readdress TAO w3c/server-timing#35.
-
ABNF for metric-value w3c/server-timing#12.
-
-
8 issues received 15 new comments.
-
Consider shorter names for the attributes w3c/server-timing#40 (5 comments by @achristensen07, @cvazac, @mnot, @yoavweiss)
-
Link to a defined extension hook in Resource Timing & Nav Timing w3c/server-timing#19 (1 comment by @igrigorik)
-
-
1 pull request opened.
-
Header format change: duration -> dur, description -> desc w3c/server-timing#41, by @cvazac.
-
-
2 pull requests merged.
-
Header format change: duration -> dur, description -> desc w3c/server-timing#41.
-
update ABNF and header examples w3c/server-timing#37.
-
-
1 pull request received 1 new comment.
w3c/network-error-logging
-
2 issues opened.
-
Update spec to use respec reference best practices w3c/network-error-logging#68, by @igrigorik.
-
Define NEL on top of Reporting API w3c/network-error-logging#67, by @igrigorik.
-
-
1 pull request opened.
-
Eliminate all custom reference links w3c/network-error-logging#69, by @dcreager.
-
-
3 pull requests merged.
-
Eliminate all custom reference links w3c/network-error-logging#69.
-
Rename includeSubdomains to include-subdomains w3c/network-error-logging#62.
-
Fix links to is-origin-trustworthy w3c/network-error-logging#64.
-
-
1 pull request closed.
-
Define NEL in terms of Fetch w3c/network-error-logging#55.
-
-
3 pull requests received 8 new comments.
-
Eliminate all custom reference links w3c/network-error-logging#69 (3 comments by @dcreager, @igrigorik)
w3c/web-performance
-
1 issue closed.
-
Intersection Observer review w3c/web-performance#19.
-
-
1 issue received 1 new comment.
w3c/user-timing
-
2 issues opened.
-
Fix respec warnings and processing w3c/user-timing#32, by @igrigorik.
-
Clarify what Navigation Timing entries are allowed and how to use their values w3c/user-timing#31, by @philipwalton.
-
-
2 issues received 5 new comments.
-
What does "navigationStart" mean as a second argument to performance.measure() in a web worker? w3c/user-timing#22 (3 comments by @philipwalton, @toddreifsteck)
-
-
1 pull request opened.
-
Clarify that measure() may throw a SyntaxError w3c/user-timing#30, by @philipwalton.
-
-
1 pull request received 1 new comment.
TR publications
-
4 documents published.
-
Page Visibility Level 2 published as a Proposed Recommendation. History of Page Visibility Level 2
-
Cooperative Scheduling of Background Tasks published as a Proposed Recommendation. History of Cooperative Scheduling of Background Tasks
-
Preload published as a Candidate Recommendation Snapshot. History of Preload
-
Server Timing published as a Working Draft. History of Server Timing
-
GitHub
w3c/network-error-logging
-
2 issues opened.
-
Clarify when reports are sent w3c/network-error-logging#66, by @sleevi.
-
Specify a maximum 'max-age' w3c/network-error-logging#65, by @sleevi.
-
-
3 issues received 4 new comments.
-
broken link on is-origin-trustworthy in 2.2.1.1 w3c/network-error-logging#57 (2 comments by @dcreager)
-
clarify the case with overlapping origins and subdomains w3c/network-error-logging#59 (1 comment by @sleevi)
-
-
3 pull requests opened.
-
Fix links to is-origin-trustworthy w3c/network-error-logging#64, by @dcreager.
-
Add successes and sampling rates w3c/network-error-logging#63, by @dcreager.
-
Rename includeSubdomains to include-subdomains w3c/network-error-logging#62, by @dcreager.
-
w3c/server-timing
-
2 issues opened.
-
RT and NT processing is not well defined w3c/server-timing#38, by @igrigorik.
-
readdress TAO w3c/server-timing#35, by @cvazac.
-
-
1 issue received 2 new comments.
-
2 pull requests opened.
-
update ABNF and header examples w3c/server-timing#37, by @cvazac.
-
Exclude PerformanceServerTiming objects for resources that fail the "timing allow check" algorithm w3c/server-timing#36, by @cvazac.
-
-
1 pull request merged.
-
2 pull requests received 22 new comments.
-
update ABNF and header examples w3c/server-timing#37 (14 comments by @cvazac, @igrigorik, @yoavweiss)
-
Exclude PerformanceServerTiming objects for resources that fail the "timing allow check" algorithm w3c/server-timing#36 (8 comments by @cvazac, @igrigorik, @yoavweiss)
-
w3c/resource-timing
-
6 issues opened.
-
how should connection limits impact times? w3c/resource-timing#124, by @toddreifsteck.
-
How do dns and connectStart handle multiple ip/name options? w3c/resource-timing#123, by @toddreifsteck.
-
NextHopProtocol Values w3c/resource-timing#122, by @googUser.
-
TFO and secureConnectionStart w3c/resource-timing#120, by @toddreifsteck.
-
spec what requestStart, responseStart, and responseEnd should represent when service worker is involved w3c/resource-timing#119, by @wanderview.
-
should redirected navigations have a workerStart value if a previous redirect URL was intercepted w3c/resource-timing#118, by @wanderview.
-
-
3 issues closed.
-
how should connection limits impact times? w3c/resource-timing#124.
-
Resource entry limit in Internet Explorer 10 w3c/resource-timing#104.
-
Existing Test gap: Verify that toJSON is created properly w3c/resource-timing#115.
-
-
9 issues received 29 new comments.
-
spec what requestStart, responseStart, and responseEnd should represent when service worker is involved w3c/resource-timing#119 (13 comments by @igrigorik, @mfalken, @wanderview)
-
NextHopProtocol Values w3c/resource-timing#122 (3 comments by @igrigorik, @plehegar, @toddreifsteck)
-
Existing Test gap: Verify that toJSON is created properly w3c/resource-timing#115 (3 comments by @igrigorik, @plehegar)
-
should redirected navigations have a workerStart value if a previous redirect URL was intercepted w3c/resource-timing#118 (2 comments by @igrigorik, @wanderview)
-
Clarify when entry is added to performance entry buffer w3c/resource-timing#82 (2 comments by @ghost, @igrigorik)
-
How do dns and connectStart handle multiple ip/name options? w3c/resource-timing#123 (2 comments by @igrigorik, @toddreifsteck)
-
Resource entry limit in Internet Explorer 10 w3c/resource-timing#104 (2 comments by @ghost, @toddreifsteck)
-
-
2 pull requests opened.
-
Added a link to the ALPN Protocol IDs registry w3c/resource-timing#125, by @plehegar.
-
Fix `connectEnd` definition w3c/resource-timing#121, by @yoavweiss.
-
-
2 pull requests merged.
-
Added a link to the ALPN Protocol IDs registry w3c/resource-timing#125.
-
Fix `connectEnd` definition w3c/resource-timing#121.
-
-
1 pull request received 1 new comment.
-
fetchStart is a required field, not a parenthesized zeroed field w3c/resource-timing#117 (1 comment by @igrigorik)
-
w3c/requestidlecallback
-
2 issues opened.
-
Priority Queue Option w3c/requestidlecallback#68, by @sebmarkbage.
-
(Editorial) Example 1 does not render properly w3c/requestidlecallback#67, by @iherman.
-
-
1 issue closed.
-
(Editorial) Example 1 does not render properly w3c/requestidlecallback#67.
-
-
2 issues reopened.
-
(Editorial) Example 1 does not render properly w3c/requestidlecallback#67, by @rmcilroy.
-
Priority Queue Option w3c/requestidlecallback#68, by @sebmarkbage.
-
-
3 issues received 26 new comments.
-
(Editorial) Example 1 does not render properly w3c/requestidlecallback#67 (14 comments by @igrigorik, @marcoscaceres, @rmcilroy)
-
Priority Queue Option w3c/requestidlecallback#68 (10 comments by @farre, @mbrevda, @motiz88, @rmcilroy, @RReverser, @sebmarkbage, @skyostil)
-
Allow requesting a minimum time budget w3c/requestidlecallback#49 (2 comments by @cramforce, @farre)
-
-
1 pull request opened.
-
fix: asterisk in example w3c/requestidlecallback#69, by @marcoscaceres.
-
-
1 pull request merged.
-
fix: asterisk in example w3c/requestidlecallback#69.
-
-
1 pull request received 1 new comment.
w3c/performance-timeline
-
6 issues opened.
-
Steps 3 and 4 of observe() aren't clear about what list is being considered w3c/performance-timeline#94, by @bzbarsky.
-
observe() step 3 is confused about what objects it's manipulating w3c/performance-timeline#93, by @bzbarsky.
-
Need to define what it means for an element of entryTypes to be "unsupported" w3c/performance-timeline#92, by @bzbarsky.
-
Does PerformanceObserverInit's entryTypes contain types or names? w3c/performance-timeline#91, by @bzbarsky.
-
Step 1 of observe() gets an entryTypes sequence from ... where? w3c/performance-timeline#90, by @bzbarsky.
-
Step 1 of "observe" is not clear w3c/performance-timeline#89, by @bzbarsky.
-
-
4 issues closed.
-
Need to define what it means for an element of entryTypes to be "unsupported" w3c/performance-timeline#92.
-
Step 1 of "observe" is not clear w3c/performance-timeline#89.
-
Should PerformanceObserver throw when entryTypes is empty? w3c/performance-timeline#87.
-
Existing Test gap: Verify that toJSON output is created properly w3c/performance-timeline#83.
-
-
4 issues received 7 new comments.
-
Existing Test gap: Verify that toJSON output is created properly w3c/performance-timeline#83 (4 comments by @igrigorik, @plehegar, @toddreifsteck)
-
Need to define what it means for an element of entryTypes to be "unsupported" w3c/performance-timeline#92 (1 comment by @igrigorik)
-
Should PerformanceObserver throw when entryTypes is empty? w3c/performance-timeline#87 (1 comment by @igrigorik)
-
-
2 pull requests opened.
-
Improve observe() logic and references w3c/performance-timeline#96, by @igrigorik.
-
[WIP] Explain and improve PerformanceObserver ergonomics w3c/performance-timeline#95, by @igrigorik.
-
-
1 pull request merged.
-
observing an empty sequence of entryTypes is a no-op w3c/performance-timeline#88.
-
-
4 pull requests received 40 new comments.
-
Improve observe() logic and references w3c/performance-timeline#96 (16 comments by @bzbarsky, @igrigorik, @spanicker)
-
observing an empty sequence of entryTypes is a no-op w3c/performance-timeline#88 (12 comments by @igrigorik, @plehegar, @yoavweiss)
-
[WIP] Explain and improve PerformanceObserver ergonomics w3c/performance-timeline#95 (10 comments by @igrigorik, @spanicker, @tdresser)
-
w3c/device-memory
-
1 issue opened.
-
Expose CPU clock speed and GPU info in the same manner as device memory w3c/device-memory#15, by @n8schloss.
-
-
1 pull request opened.
-
Fix typos and minor grammar issues w3c/device-memory#16, by @jdanford.
-
w3c/user-timing
-
1 issue received 2 new comments.
-
mark() and measure() return PerformanceEntries w3c/user-timing#23 (2 comments by @nolanlawson, @philipwalton)
-
w3c/reporting
-
1 issue opened.
-
Define crash reports w3c/reporting#56, by @RByers.
-
-
9 issues received 17 new comments.
-
Friendly TAG Review: Thoughts on the HTTP header w3c/reporting#53 (3 comments by @igrigorik, @mikewest, @RByers)
-
Friendly TAG Review: relation to lifecycle events w3c/reporting#54 (2 comments by @RByers, @spanicker)
-
Friendly TAG Review: service worker integration w3c/reporting#50 (2 comments by @igrigorik, @RByers)
-
reporting of metadata such as browser engine+version or other metadata chosen by page? w3c/reporting#49 (2 comments by @dbaron, @RByers)
-
w3c/hr-time
-
1 pull request opened.
-
Example currently broken in latest/published versions w3c/hr-time#52, by @ericduran.
-
-
1 pull request merged.
-
Example currently broken in latest/published versions w3c/hr-time#52.
-
-
1 pull request received 5 new comments.
-
Example currently broken in latest/published versions w3c/hr-time#52 (5 comments by @ericduran, @igrigorik, @plehegar)
-
w3c/perf-timing-primer
-
3 pull requests opened.
-
Adding def for time origin to fix broken time origin links w3c/perf-timing-primer#14, by @ericduran.
-
A couple more fixes w3c/perf-timing-primer#13, by @ericduran.
-
Replacing image with imagine w3c/perf-timing-primer#12, by @ericduran.
-
-
3 pull requests merged.
-
Adding def for time origin to fix broken time origin links w3c/perf-timing-primer#14.
-
A couple more fixes w3c/perf-timing-primer#13.
-
Replacing image with imagine w3c/perf-timing-primer#12.
-
-
2 pull requests received 4 new comments.
w3c/navigation-timing
-
1 issue closed.
-
Existing Test gap: Verify that toJSON is created properly w3c/navigation-timing#74.
-
-
1 issue received 3 new comments.
-
Existing Test gap: Verify that toJSON is created properly w3c/navigation-timing#74 (3 comments by @igrigorik, @plehegar)
-
w3c/beacon
-
3 issues closed.
-
Typo in Introduction note w3c/beacon#55.
-
Typo in Privacy and Security w3c/beacon#57.
-
Typo in Processing Model - fetch step w3c/beacon#56.
-
-
3 issues received 3 new comments.
w3c/paint-timing
-
1 issue opened.
-
Naming of entries is inconsistent with the Navigation Timing API w3c/paint-timing#18, by @thomas-darling.
-
-
1 issue closed.
-
Naming of entries is inconsistent with the Navigation Timing API w3c/paint-timing#18.
-
-
2 issues received 8 new comments.
-
Naming of entries is inconsistent with the Navigation Timing API w3c/paint-timing#18 (5 comments by @domenic, @igrigorik, @thomas-darling)
-
Headings should be sentence case, not titlecase w3c/paint-timing#14 (3 comments by @domenic, @thomas-darling)
-
TR publications
-
5 documents published.
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Server Timing published twice as a Working Draft. History of Server Timing
-
Long Tasks API 1 published as a First Public Working Draft. History of Long Tasks API 1
-
Paint Timing 1 published as a First Public Working Draft. History of Paint Timing 1
-
Participants
-
1 participant left.
-
Michael[tm] Smith (sideshowbarker) (W3C) left.
-
GitHub
w3c/resource-timing
-
2 issues closed.
-
Graphic should indicate fetchStart is a required field, not a parenthesized zeroed field w3c/resource-timing#98.
-
Prose link to PerformanceEntry is broken w3c/resource-timing#108.
-
-
3 issues received 5 new comments.
-
Existing Test gap: Verify that toJSON is created properly w3c/resource-timing#115 (3 comments by @plehegar, @tobie)
-
Graphic should indicate fetchStart is a required field, not a parenthesized zeroed field w3c/resource-timing#98 (1 comment by @plehegar)
-
Ensure that first byte measurement and 1XX responses are covered by tests w3c/resource-timing#87 (1 comment by @plehegar)
-
-
1 pull request opened.
-
fetchStart is a required field, not a parenthesized zeroed field w3c/resource-timing#117, by @plehegar.
-
-
1 pull request merged.
-
fetchStart is a required field, not a parenthesized zeroed field w3c/resource-timing#117.
-
w3c/reporting
-
8 issues opened.
-
Friendly TAG Review: Crash ids w3c/reporting#55, by @travisleithead.
-
Friendly TAG Review: relation to lifecycle events w3c/reporting#54, by @travisleithead.
-
Friendly TAG Review: Thoughts on the HTTP header w3c/reporting#53, by @travisleithead.
-
Friendly TAG Review: UA string consistency w3c/reporting#52, by @travisleithead.
-
Friendly TAG Review: content type? w3c/reporting#51, by @travisleithead.
-
Friendly TAG Review: service worker integration w3c/reporting#50, by @travisleithead.
-
Should any Report-To header clear unspecified endpoints? w3c/reporting#48, by @juliatuttle.
-
-
3 issues closed.
-
Don't name variables in the spec _new_ w3c/reporting#13.
-
"Process reporting endpoints..." adds 0-ttl client to new endpoint w3c/reporting#15.
-
Superdomain match logic is backwards w3c/reporting#16.
-
-
2 issues received 6 new comments.
-
Should ReportingObserver.observe accept a filter? w3c/reporting#46 (4 comments by @igrigorik, @RByers)
-
Should any Report-To header clear unspecified endpoints? w3c/reporting#48 (2 comments by @igrigorik, @juliatuttle)
-
-
1 pull request opened.
-
Add ReportingObserver w3c/reporting#47, by @RByers.
-
-
2 pull requests merged.
-
Fix spurious 0-ttl client, rename new in 'Process reporting endpoints'. w3c/reporting#22.
-
Fix superdomain match logic. w3c/reporting#21.
-
-
2 pull requests received 7 new comments.
-
Fix spurious 0-ttl client, rename new in 'Process reporting endpoints'. w3c/reporting#22 (1 comment by @juliatuttle)
w3c/server-timing
-
1 issue opened.
-
Incorporating feedback from TAG review w3c/server-timing#32, by @yoavweiss.
-
-
1 issue received 5 new comments.
-
Incorporating feedback from TAG review w3c/server-timing#32 (5 comments by @cvazac, @igrigorik, @reschke, @triblondon)
-
-
3 pull requests opened.
-
fix typo in usage section w3c/server-timing#34, by @cvazac.
-
address w3ctag review feedback w3c/server-timing#31, by @cvazac.
-
-
2 pull requests merged.
-
fix typo in usage section w3c/server-timing#34.
-
address w3ctag review feedback w3c/server-timing#31.
-
-
1 pull request closed.
-
fix typos w3c/server-timing#33.
-
w3c/beacon
-
3 issues opened.
-
Typo in Privacy and Security w3c/beacon#57, by @JosephPecoraro.
-
Typo in Processing Model - fetch step w3c/beacon#56, by @JosephPecoraro.
-
Typo in Introduction note w3c/beacon#55, by @JosephPecoraro.
-
-
1 issue closed.
-
1 pull request merged.
-
cleanup processing section w3c/beacon#54.
-
-
1 pull request received 9 new comments.
w3c/web-performance
-
2 issues opened.
-
Broken website link on github repo w3c/web-performance#21, by @ericduran.
-
Intersection Observer review w3c/web-performance#19, by @LJWatson.
-
-
1 pull request opened.
-
Teams are only visible to members of the org, so using public link w3c/web-performance#20, by @ericduran.
-
-
1 pull request merged.
-
Teams are only visible to members of the org, so using public link w3c/web-performance#20.
-
w3c/requestidlecallback
-
1 issue opened.
-
Add [Exposed] to all interfaces w3c/requestidlecallback#64, by @annevk.
-
-
1 issue closed.
-
Add [Exposed] to all interfaces w3c/requestidlecallback#64.
-
-
2 pull requests opened.
-
Fix typo in index.html w3c/requestidlecallback#66, by @piperchester.
-
Add Exposed to interfaces. w3c/requestidlecallback#65, by @rmcilroy.
-
-
2 pull requests merged.
-
Fix typo in index.html w3c/requestidlecallback#66.
-
Add Exposed to interfaces. w3c/requestidlecallback#65.
-
-
1 pull request reopened.
-
Add Exposed to interfaces. w3c/requestidlecallback#65, by @rmcilroy.
-
-
2 pull requests received 13 new comments.
-
Add Exposed to interfaces. w3c/requestidlecallback#65 (11 comments by @annevk, @igrigorik, @rmcilroy)
-
w3c/user-timing
-
1 issue closed.
-
Worker tests for User Timing w3c/user-timing#20.
-
-
6 issues received 20 new comments.
-
mark() and measure() return PerformanceEntries w3c/user-timing#23 (5 comments by @igrigorik, @nolanlawson, @philipwalton)
-
Existing Test gap: Verify that toJSON output is created properly w3c/user-timing#29 (5 comments by @plehegar, @tobie)
-
measure() may throw SyntaxError w3c/user-timing#21 (3 comments by @igrigorik, @philipwalton, @plehegar)
-
What does "navigationStart" mean as a second argument to performance.measure() in a web worker? w3c/user-timing#22 (3 comments by @igrigorik, @JosephPecoraro, @philipwalton)
-
w3c/performance-timeline
-
1 issue opened.
-
Should PerformanceObserver throw when entryTypes is empty? w3c/performance-timeline#87, by @igrigorik.
-
-
4 issues received 14 new comments.
-
"bubbles" flag for monitoring of all IFRAMEs w3c/performance-timeline#86 (6 comments by @igrigorik, @nicjansma, @tdresser)
-
Should PerformanceObserver throw when entryTypes is empty? w3c/performance-timeline#87 (5 comments by @cvazac, @igrigorik, @JosephPecoraro, @wisniewskit)
-
Add entryTypes method to enumerate type of entries observable via PerformanceObserver w3c/performance-timeline#77 (2 comments by @hiikezoe, @JosephPecoraro)
-
Existing Test gap: Verify that toJSON output is created properly w3c/performance-timeline#83 (1 comment by @plehegar)
-
-
1 pull request opened.
-
observing an empty sequence of entryTypes is a no-op w3c/performance-timeline#88, by @plehegar.
-
-
1 pull request received 3 new comments.
-
observing an empty sequence of entryTypes is a no-op w3c/performance-timeline#88 (3 comments by @igrigorik, @plehegar)
-
w3c/navigation-timing
-
1 issue opened.
-
Add [Exposed] to all interfaces w3c/navigation-timing#75, by @annevk.
-
-
3 issues closed.
-
Obsolete partial interface to the Performance has incorrect exposure setting w3c/navigation-timing#70.
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/navigation-timing#72.
-
Add [Exposed] to all interfaces w3c/navigation-timing#75.
-
-
4 issues received 4 new comments.
-
Existing Test gap: Verify that toJSON is created properly w3c/navigation-timing#74 (1 comment by @plehegar)
-
Obsolete partial interface to the Performance has incorrect exposure setting w3c/navigation-timing#70 (1 comment by @igrigorik)
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/navigation-timing#72 (1 comment by @igrigorik)
-
-
1 pull request opened.
-
Add [Exposed=Window] and use toJSON w3c/navigation-timing#76, by @plehegar.
-
-
1 pull request merged.
-
Add [Exposed=Window] and use toJSON w3c/navigation-timing#76.
-
w3c/longtasks
-
1 issue opened.
-
Long tasks v2 scriptUrl -> scriptURL w3c/longtasks#36, by @domenic.
-
w3c/perf-timing-primer
-
1 issue closed.
-
https://www.w3.org/TR/perf-timing-primer/ leads to 404 w3c/perf-timing-primer#7.
-
-
1 issue received 2 new comments.
-
https://www.w3.org/TR/perf-timing-primer/ leads to 404 w3c/perf-timing-primer#7 (2 comments by @alundiak, @siusin)
-
-
1 pull request opened.
-
Uncaught ReferenceError: i is not defined w3c/perf-timing-primer#11, by @alundiak.
-
-
1 pull request merged.
-
Uncaught ReferenceError: i is not defined w3c/perf-timing-primer#11.
-
-
1 pull request received 1 new comment.
w3c/device-memory
-
1 issue closed.
-
Issue tracking link is wrong w3c/device-memory#12.
-
-
3 issues received 9 new comments.
-
Should device memory be limited to what the UA can access? w3c/device-memory#13 (5 comments by @domenic, @fmeawad, @spanicker)
-
Setup auto-publish workflow for index.html; deprecate README.md w3c/device-memory#11 (3 comments by @siusin, @spanicker)
-
-
1 pull request opened.
-
auto-pub the editor's draft w3c/device-memory#14, by @siusin.
-
-
1 pull request merged.
-
auto-pub the editor's draft w3c/device-memory#14.
-
w3c/network-error-logging
-
1 pull request merged.
-
Move from CSP-style format to JSON Field Values w3c/network-error-logging#61.
-
-
1 pull request received 1 new comment.
-
Move from CSP-style format to JSON Field Values w3c/network-error-logging#61 (1 comment by @juliatuttle)
-
TR publications
-
8 documents published.
-
High Resolution Time Level 2 published as a Candidate Recommendation Snapshot. History of High Resolution Time Level 2
-
Preload published twice as a Working Draft. History of Preload
-
Server Timing published 4 times as a Working Draft. History of Server Timing
-
High Resolution Time Level 3 published as a Note. History of High Resolution Time Level 3
-
Participants
-
1 organization left.
-
360 left.
-
GitHub
w3c/resource-timing
-
2 issues opened.
-
domainLookupStart and domainLookupEnd during HTTP/2 Connection Reuse w3c/resource-timing#116, by @sajal.
-
Would like a precise way to map PerformanceTimings to FetchEvent w3c/resource-timing#259, by @jakearchibald.
-
-
1 issue closed.
-
domainLookupStart and domainLookupEnd during HTTP/2 Connection Reuse w3c/resource-timing#116.
-
-
2 issues received 11 new comments.
-
Would like a precise way to map PerformanceTimings to FetchEvent w3c/resource-timing#259 (8 comments by @annevk, @clayw, @igrigorik, @jakearchibald, @yoavweiss)
-
domainLookupStart and domainLookupEnd during HTTP/2 Connection Reuse w3c/resource-timing#116 (3 comments by @igrigorik, @sajal)
-
w3c/performance-timeline
-
1 issue opened.
-
"bubbles" flag for monitoring of all IFRAMEs w3c/performance-timeline#86, by @nicjansma.
-
-
3 issues received 4 new comments.
-
Clarify disconnecting a PerformanceObserver that has observed entries w3c/performance-timeline#66 (2 comments by @birtles, @yoavweiss)
-
Clarity on buffered-until-onload (and buffers, buffers, everywhere) w3c/performance-timeline#78 (1 comment by @nicjansma)
-
w3c/paint-timing
-
2 issues closed.
-
PerformanceTimeline or NavigationTiming support w3c/paint-timing#6.
-
First Paint definition contains copy-paste error w3c/paint-timing#9.
-
-
2 issues received 3 new comments.
-
PerformanceTimeline or NavigationTiming support w3c/paint-timing#6 (2 comments by @igrigorik, @nicjansma)
-
-
1 pull request opened.
-
Remove repeated sentence w3c/paint-timing#17, by @ferjm.
-
-
2 pull requests merged.
-
Fix grammatical typo in README w3c/paint-timing#3.
-
Remove repeated sentence w3c/paint-timing#17.
-
w3c/network-error-logging
-
1 pull request opened.
-
Move from CSP-style format to JSON Field Values w3c/network-error-logging#61, by @juliatuttle.
-
-
1 pull request received 10 new comments.
-
Move from CSP-style format to JSON Field Values w3c/network-error-logging#61 (10 comments by @igrigorik, @juliatuttle)
-
w3c/device-memory
-
3 issues opened.
-
Should device memory be limited to what the UA can access? w3c/device-memory#13, by @bzbarsky.
-
Issue tracking link is wrong w3c/device-memory#12, by @bzbarsky.
-
Setup auto-publish workflow for index.html; deprecate README.md w3c/device-memory#11, by @igrigorik.
-
-
1 issue closed.
-
Bikeshed: RAM vs. memory w3c/device-memory#6.
-
-
2 issues received 3 new comments.
-
Setup auto-publish workflow for index.html; deprecate README.md w3c/device-memory#11 (2 comments by @spanicker)
-
w3c/server-timing
-
4 pull requests opened.
-
DOMHighResTimestamp -> DOMHighResTimeStamp w3c/server-timing#30, by @cvazac.
-
update ABNF w3c/server-timing#29, by @cvazac.
-
add explainer w3c/server-timing#28, by @cvazac.
-
prefer 'for ... of' over 'forEach' w3c/server-timing#27, by @cvazac.
-
-
4 pull requests merged.
-
DOMHighResTimestamp -> DOMHighResTimeStamp w3c/server-timing#30.
-
update ABNF w3c/server-timing#29.
-
add explainer w3c/server-timing#28.
-
prefer 'for ... of' over 'forEach' w3c/server-timing#27.
-
-
3 pull requests received 9 new comments.
w3c/longtasks
-
1 issue opened.
-
remove index.html in the master branch w3c/longtasks#35, by @siusin.
-
-
1 issue closed.
-
PerformanceLongTaskTiming millisecond round vs floor w3c/longtasks#29.
-
-
2 issues received 5 new comments.
-
remove index.html in the master branch w3c/longtasks#35 (4 comments by @domenic, @igrigorik, @siusin, @spanicker)
-
w3c/beacon
-
6 issues opened.
-
corsMode calculation in the "Processing Model" section is broken w3c/beacon#53, by @tyoshino.
-
Remove referrer source definition + HTML5.2 dep w3c/beacon#51, by @igrigorik.
-
How important is it for sendBeacon() to follow redirects? w3c/beacon#49, by @cdumez.
-
Should sendBeacon set the FetchRequest's cacheMode to "no-cache"? w3c/beacon#48, by @cdumez.
-
Editorial cleanup w3c/beacon#47, by @igrigorik.
-
Complete PR for testing beacon w3c/beacon#46, by @toddreifsteck.
-
-
7 issues closed.
-
Remove referrer source definition + HTML5.2 dep w3c/beacon#51.
-
How important is it for sendBeacon() to follow redirects? w3c/beacon#49.
-
Editorial cleanup w3c/beacon#47.
-
Complete PR for testing beacon w3c/beacon#46.
-
-
9 issues received 48 new comments.
-
ArrayBuffer uses "application/octet-stream" as default Content-Type in impl w3c/beacon#40 (19 comments by @annevk, @cdumez, @igrigorik)
-
How important is it for sendBeacon() to follow redirects? w3c/beacon#49 (12 comments by @beidson, @geoffreygaren, @igrigorik, @leosei)
-
Should sendBeacon set the FetchRequest's cacheMode to "no-cache"? w3c/beacon#48 (4 comments by @cdumez, @igrigorik)
-
Should cross-origin beacons with an ArrayBuffer payload do a CORS preflight? w3c/beacon#45 (3 comments by @cdumez, @igrigorik)
-
corsMode calculation in the "Processing Model" section is broken w3c/beacon#53 (1 comment by @igrigorik)
-
-
3 pull requests opened.
-
cleanup processing section w3c/beacon#54, by @igrigorik.
-
remove referrer resource w3c/beacon#52, by @siusin.
-
Clean up the Dependencies section - fix #47 w3c/beacon#50, by @siusin.
-
-
2 pull requests merged.
-
remove referrer resource w3c/beacon#52.
-
Clean up the Dependencies section - fix #47 w3c/beacon#50.
-
-
2 pull requests received 25 new comments.
-
Clean up the Dependencies section - fix #47 w3c/beacon#50 (23 comments by @igrigorik, @marcoscaceres, @siusin)
-
w3c/reporting
-
2 issues opened.
-
Should ReportingObserver.observe accept a filter? w3c/reporting#46, by @RByers.
-
Rate limiting w3c/reporting#45, by @danmx.
-
-
3 issues received 4 new comments.
w3c/charter-webperf
-
1 issue opened.
-
Spec to record "next paint time" w3c/charter-webperf#35, by @bmaurer.
-
-
2 issues received 5 new comments.
-
Spec to record "next paint time" w3c/charter-webperf#35 (4 comments by @bmaurer, @igrigorik, @spanicker)
-
Enable developers to create and queue custom PerformanceEntry objects w3c/charter-webperf#28 (1 comment by @tdresser)
-
w3c/requestidlecallback
-
1 issue opened.
-
Define IdleDeadline internal layout part 2 w3c/requestidlecallback#61, by @annevk.
-
-
2 issues closed.
-
Define IdleDeadline internal layout part 2 w3c/requestidlecallback#61.
-
Don't monkey patch the event loop algorithm w3c/requestidlecallback#57.
-
-
2 issues received 7 new comments.
-
Define IdleDeadline internal layout part 2 w3c/requestidlecallback#61 (6 comments by @annevk, @igrigorik, @rmcilroy)
-
-
2 pull requests opened.
-
Add dependencies section to maintain citation references. w3c/requestidlecallback#63, by @rmcilroy.
-
Fix didTimeout definition w3c/requestidlecallback#62, by @rmcilroy.
-
-
3 pull requests merged.
-
Add dependencies section to maintain citation references. w3c/requestidlecallback#63.
-
Fix didTimeout definition w3c/requestidlecallback#62.
-
Change start idle period algorithm to avoid monkey patching event loop. w3c/requestidlecallback#60.
-
-
3 pull requests received 50 new comments.
-
Add dependencies section to maintain citation references. w3c/requestidlecallback#63 (27 comments by @igrigorik, @marcoscaceres, @rmcilroy)
-
Change start idle period algorithm to avoid monkey patching event loop. w3c/requestidlecallback#60 (15 comments by @annevk, @igrigorik, @rmcilroy)
-
w3c/hr-time
-
1 pull request closed.
-
Improve latest version headers w3c/hr-time#39.
-
-
1 pull request received 1 new comment.
TR publications
-
6 documents published.
-
Server Timing published 3 times as a Working Draft. History of Server Timing
-
Preload published 3 times as a Working Draft. History of Preload
-
GitHub
w3c/beacon
-
1 issue opened.
w3c/requestidlecallback
-
3 issues closed.
-
Defined IdleDeadline internal layout w3c/requestidlecallback#56.
-
timeRemaining() is badly defined, deadline argument w3c/requestidlecallback#55.
-
timeRemaining() is badly defined w3c/requestidlecallback#54.
-
-
4 issues received 6 new comments.
-
Don't monkey patch the event loop algorithm w3c/requestidlecallback#57 (3 comments by @annevk, @rmcilroy)
-
timeRemaining() is badly defined, deadline argument w3c/requestidlecallback#55 (1 comment by @igrigorik)
-
-
3 pull requests opened.
-
Change start idle period algorithm to avoid monkey patching event loop. w3c/requestidlecallback#60, by @rmcilroy.
-
Fix some respec issues w3c/requestidlecallback#59, by @rmcilroy.
-
Address feedback on timeRemaining method. w3c/requestidlecallback#58, by @rmcilroy.
-
-
2 pull requests merged.
-
Fix some respec issues w3c/requestidlecallback#59.
-
Address feedback on timeRemaining method. w3c/requestidlecallback#58.
-
-
3 pull requests received 22 new comments.
-
Change start idle period algorithm to avoid monkey patching event loop. w3c/requestidlecallback#60 (10 comments by @annevk, @igrigorik, @rmcilroy)
-
Address feedback on timeRemaining method. w3c/requestidlecallback#58 (9 comments by @annevk, @igrigorik, @rmcilroy)
-
w3c/resource-timing
-
1 issue opened.
-
Existing Test gap: Verify that toJSON is created properly w3c/resource-timing#115, by @toddreifsteck.
-
-
1 issue closed.
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/resource-timing#112.
-
-
4 issues received 10 new comments.
-
Existing Test gap: Verify that toJSON is created properly w3c/resource-timing#115 (6 comments by @igrigorik, @tobie, @toddreifsteck)
-
Increase limit of 150 for PerformanceEntrys? w3c/resource-timing#89 (2 comments by @clarkbw, @igrigorik)
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/resource-timing#112 (1 comment by @igrigorik)
-
-
1 pull request merged.
-
fix: define toJSON (closes #112) w3c/resource-timing#114.
-
-
1 pull request received 1 new comment.
w3c/hr-time
-
2 issues closed.
-
Performance.now() should use an underlying primitive w3c/hr-time#44.
-
-
2 pull requests opened.
-
Merge timeOrigin into Level 2 w3c/hr-time#51, by @igrigorik.
-
Define "current high resolution time" as primitive w3c/hr-time#50, by @igrigorik.
-
-
2 pull requests merged.
-
Merge timeOrigin into Level 2 w3c/hr-time#51.
-
Define "current high resolution time" as primitive w3c/hr-time#50.
-
-
3 pull requests received 9 new comments.
w3c/longtasks
-
6 issues closed.
-
TaskAttributionTiming[] syntax is not valid Web IDL w3c/longtasks#9.
-
Update links to w3c w3c/longtasks#21.
-
Guidelines to contribute (send a pull request) w3c/longtasks#5.
-
Notes and action items from TPAC 2016 w3c/longtasks#4.
-
Tracking microtasks? w3c/longtasks#2.
-
7 issues received 18 new comments.
-
PerformanceLongTaskTiming millisecond round vs floor w3c/longtasks#29 (8 comments by @igrigorik, @spanicker, @tdresser)
-
Does PerformanceLongTaskTiming's attribution attribute always return the same value? w3c/longtasks#20 (2 comments by @igrigorik, @spanicker)
-
-
3 pull requests opened.
-
Update index.bs w3c/longtasks#34, by @npm1.
-
No timing clamp for long tasks: index.html w3c/longtasks#33, by @npm1.
-
No timing clamp for long tasks: README.md w3c/longtasks#32, by @npm1.
-
-
4 pull requests merged.
-
Update index.bs w3c/longtasks#34.
-
No timing clamp for long tasks: README.md w3c/longtasks#32.
-
Link to Tim's time-to-interactive proposal w3c/longtasks#6.
-
Fix bikeshed syntax for URLs for author affiliations. w3c/longtasks#24.
-
-
1 pull request received 1 new comment.
w3c/charter-webperf
-
1 issue received 3 new comments.
-
Surface blocked scroll events in Performance Timeline? w3c/charter-webperf#31 (3 comments by @smaug----, @tdresser)
-
w3c/server-timing
-
3 issues opened.
-
Transition Level 1 to CR w3c/server-timing#24, by @igrigorik.
-
Visualizing `value` for server timing entries w3c/server-timing#22, by @cvazac.
-
Link to a defined extension hook in Resource Timing & Nav Timing w3c/server-timing#19, by @igrigorik.
-
-
1 issue closed.
-
Visualizing `value` for server timing entries w3c/server-timing#22.
-
-
3 issues received 14 new comments.
-
Visualizing `value` for server timing entries w3c/server-timing#22 (8 comments by @cvazac, @igrigorik)
-
Link to a defined extension hook in Resource Timing & Nav Timing w3c/server-timing#19 (1 comment by @cvazac)
-
-
6 pull requests opened.
-
fix example w3c/server-timing#26, by @cvazac.
-
various updates w3c/server-timing#25, by @cvazac.
-
value: double -> DOMHighResTimestamp w3c/server-timing#23, by @cvazac.
-
fix a few more linking issues w3c/server-timing#21, by @marcoscaceres.
-
fix small nits, xrefs w3c/server-timing#20, by @marcoscaceres.
-
chore: add pr-preview for pull requests w3c/server-timing#18, by @marcoscaceres.
-
-
6 pull requests merged.
-
fix example w3c/server-timing#26.
-
various updates w3c/server-timing#25.
-
fix a few more linking issues w3c/server-timing#21.
-
Editorial cleanup w3c/server-timing#16.
-
fix small nits, xrefs w3c/server-timing#20.
-
chore: add pr-preview for pull requests w3c/server-timing#18.
-
-
1 pull request closed.
-
value: double -> DOMHighResTimestamp w3c/server-timing#23.
-
-
5 pull requests received 16 new comments.
w3c/performance-timeline
-
1 issue opened.
-
Existing Test gap: Verify that toJSON output is created properly w3c/performance-timeline#83, by @toddreifsteck.
-
-
3 issues closed.
-
PerformanceObserver developer / RUM friendliness w3c/performance-timeline#79.
-
Clarity on buffered-until-onload (and buffers, buffers, everywhere) w3c/performance-timeline#78.
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/performance-timeline#82.
-
-
3 issues received 3 new comments.
-
Define buffering behaviors & hooks for queued (PerformanceObserver) entries w3c/performance-timeline#81 (1 comment by @igrigorik)
-
PerformanceObserver developer / RUM friendliness w3c/performance-timeline#79 (1 comment by @igrigorik)
-
Clarity on buffered-until-onload (and buffers, buffers, everywhere) w3c/performance-timeline#78 (1 comment by @igrigorik)
-
-
1 pull request opened.
-
Fix auto-publish w3c/performance-timeline#84, by @marcoscaceres.
-
-
1 pull request received 5 new comments.
-
Fix auto-publish w3c/performance-timeline#84 (5 comments by @deniak, @igrigorik, @marcoscaceres, @siusin)
-
w3c/user-timing
-
1 issue opened.
-
Existing Test gap: Verify that toJSON output is created properly w3c/user-timing#29, by @toddreifsteck.
-
-
1 issue received 1 new comment.
w3c/paint-timing
-
9 issues opened.
-
Remove index.html w3c/paint-timing#16, by @domenic.
-
Polishing the processing model section w3c/paint-timing#15, by @domenic.
-
Headings should be sentence case, not titlecase w3c/paint-timing#14, by @domenic.
-
Stray ###s in headings w3c/paint-timing#13, by @domenic.
-
Nits in "PerformancePaintTiming interface" w3c/paint-timing#12, by @domenic.
-
Nit: heading style for Paint timing w3c/paint-timing#11, by @domenic.
-
Cross-link to update the rendering w3c/paint-timing#10, by @domenic.
-
First Paint definition contains copy-paste error w3c/paint-timing#9, by @domenic.
-
DOMHighResTimeStamp should link w3c/paint-timing#8, by @domenic.
-
-
4 issues closed.
-
Polishing the processing model section w3c/paint-timing#15.
-
Define processing algorithm w3c/paint-timing#4.
-
Stray ###s in headings w3c/paint-timing#13.
-
Remove index.html w3c/paint-timing#16.
-
-
5 issues received 11 new comments.
w3c/device-memory
-
7 issues opened.
-
JavaScript API support w3c/device-memory#10, by @laukstein.
-
Spec's "this version" link is broken w3c/device-memory#8, by @RByers.
-
Header syntax in spec w3c/device-memory#7, by @domenic.
-
Bikeshed: RAM vs. memory w3c/device-memory#6, by @domenic.
-
Relevant links should be a bulleted list w3c/device-memory#5, by @domenic.
-
navigator.deviceRam -> navigator.deviceRAM w3c/device-memory#4, by @domenic.
-
Make it clearer that this is part of the client-hints family w3c/device-memory#3, by @domenic.
-
-
4 issues closed.
-
Header syntax in spec w3c/device-memory#7.
-
Make it clearer that this is part of the client-hints family w3c/device-memory#3.
-
navigator.deviceRam -> navigator.deviceRAM w3c/device-memory#4.
-
Relevant links should be a bulleted list w3c/device-memory#5.
-
-
6 issues received 19 new comments.
-
Bikeshed: RAM vs. memory w3c/device-memory#6 (13 comments by @domenic, @fmeawad, @igrigorik, @spanicker)
-
Make it clearer that this is part of the client-hints family w3c/device-memory#3 (2 comments by @domenic, @spanicker)
-
-
1 pull request opened.
-
editorial updates w3c/device-memory#9, by @igrigorik.
-
-
1 pull request merged.
-
editorial updates w3c/device-memory#9.
-
w3c/navigation-timing
-
1 issue opened.
-
Existing Test gap: Verify that toJSON is created properly w3c/navigation-timing#74, by @toddreifsteck.
-
-
1 issue closed.
-
Can't determine whether there were no redirects or redirect failed timing allow check w3c/navigation-timing#73.
-
-
3 issues received 8 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 (4 comments by @bzbarsky, @toddreifsteck)
-
Can't determine whether there were no redirects or redirect failed timing allow check w3c/navigation-timing#73 (2 comments by @andydavies, @igrigorik)
-
Obsolete partial interface to the Performance has incorrect exposure setting w3c/navigation-timing#70 (2 comments by @plehegar, @toddreifsteck)
-
-
1 pull request received 2 new comments.
w3c/reporting
-
1 issue received 3 new comments.
w3c/perf-timing-primer
-
1 pull request opened.
-
Typo fix for "navigation" w3c/perf-timing-primer#10, by @stephendonner.
-
-
1 pull request merged.
-
Typo fix for "navigation" w3c/perf-timing-primer#10.
-
TR publications
-
1 document published.
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Participants
-
1 organization joined.
-
Orange joined.
-
GitHub
w3c/longtasks
-
5 issues opened.
-
Needs toJSON defined w3c/longtasks#31, by @toddreifsteck.
-
Indicate script parse time in attribution w3c/longtasks#30, by @spanicker.
-
PerformanceLongTaskTiming millisecond round vs floor w3c/longtasks#29, by @npm1.
-
Can we find which script or function is taking longer than 50 ms? w3c/longtasks#28, by @Vasikaran.
-
How to clear longtask entries? w3c/longtasks#27, by @yoshuawuyts.
-
-
1 issue closed.
-
How to clear longtask entries? w3c/longtasks#27.
-
-
5 issues received 17 new comments.
-
PerformanceLongTaskTiming millisecond round vs floor w3c/longtasks#29 (8 comments by @igrigorik, @npm1, @spanicker, @tdresser)
-
Can we find which script or function is taking longer than 50 ms? w3c/longtasks#28 (4 comments by @spanicker, @Vasikaran)
-
w3c/navigation-timing
-
3 issues opened.
-
Can't determine whether there were no redirects or redirect failed timing allow check w3c/navigation-timing#73, by @andydavies.
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/navigation-timing#72, by @tobie.
-
Computing nextHopProtocol w3c/navigation-timing#71, by @spanicker.
-
-
2 issues closed.
-
Report URL in "name" attribute (instead of "document") w3c/navigation-timing#59.
-
Computing nextHopProtocol w3c/navigation-timing#71.
-
-
3 issues received 11 new comments.
-
Computing nextHopProtocol w3c/navigation-timing#71 (7 comments by @igrigorik, @spanicker, @yoavweiss)
-
Can't determine whether there were no redirects or redirect failed timing allow check w3c/navigation-timing#73 (2 comments by @igrigorik, @yoavweiss)
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/navigation-timing#72 (2 comments by @igrigorik, @tobie)
-
-
1 pull request merged.
-
set name to document address w3c/navigation-timing#61.
-
-
1 pull request received 3 new comments.
-
set name to document address w3c/navigation-timing#61 (3 comments by @igrigorik, @spanicker, @toddreifsteck)
-
w3c/resource-timing
-
1 issue opened.
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/resource-timing#112, by @tobie.
-
-
2 issues received 11 new comments.
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/resource-timing#112 (10 comments by @igrigorik, @marcoscaceres, @tobie)
-
Expose a way to link a call to fetch to an individual PerformanceResourceTiming object w3c/resource-timing#102 (1 comment by @LPardue)
-
-
2 pull requests opened.
-
fix: define toJSON (closes #112) w3c/resource-timing#114, by @marcoscaceres.
-
Fix links w3c/resource-timing#113, by @dontcallmedom.
-
-
1 pull request merged.
-
Fix links w3c/resource-timing#113.
-
-
1 pull request received 5 new comments.
-
fix: define toJSON (closes #112) w3c/resource-timing#114 (5 comments by @igrigorik, @marcoscaceres, @siusin, @toddreifsteck)
-
w3c/server-timing
-
1 issue opened.
-
Setup travis w3c/server-timing#17, by @igrigorik.
-
-
6 issues closed.
-
Setup travis w3c/server-timing#17.
-
Linking to ResourceTiming w3c/server-timing#14.
-
interface ServerEntry should be renamed to PerformanServerTiming w3c/server-timing#3.
-
Secure context only w3c/server-timing#9.
-
Server-Timing Headers Read from Browser Cache w3c/server-timing#13.
-
-
7 issues received 36 new comments.
-
ABNF for metric-value w3c/server-timing#12 (25 comments by @cvazac, @igrigorik, @mnot, @reschke, @yoavweiss)
-
Having duration with no start time makes it hard to profile servers with parallel processes. w3c/server-timing#10 (2 comments by @igrigorik)
-
interface ServerEntry should be renamed to PerformanServerTiming w3c/server-timing#3 (1 comment by @igrigorik)
-
-
2 pull requests opened.
-
Editorial cleanup w3c/server-timing#16, by @igrigorik.
-
rebase onto performance-timeline-2, etcetera w3c/server-timing#15, by @cvazac.
-
-
1 pull request merged.
-
rebase onto performance-timeline-2, etcetera w3c/server-timing#15.
-
-
2 pull requests received 16 new comments.
w3c/beacon
-
1 issue closed.
-
Privacy & Security section not current w3c/beacon#43.
-
-
1 pull request merged.
-
1 pull request received 1 new comment.
-
Update privacy & security section to reflect CORS processing logic. w3c/beacon#44 (1 comment by @igrigorik)
-
w3c/user-timing
-
1 pull request opened.
-
Clean up markup w3c/user-timing#28, by @dontcallmedom.
-
-
1 pull request merged.
-
Clean up markup w3c/user-timing#28.
-
-
1 pull request received 1 new comment.
w3c/reporting
-
1 issue opened.
-
OOM reporting in "crash" report w3c/reporting#44, by @spanicker.
-
-
3 issues received 5 new comments.
w3c/paint-timing
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Fix typo w3c/paint-timing#7, by @saschanaz.
-
-
1 pull request merged.
-
Fix typo w3c/paint-timing#7.
-
-
1 pull request received 1 new comment.
w3c/device-memory
-
1 issue closed.
-
Devices reporting (X GB - few MB) will report X/2 GB device-ram value w3c/device-memory#1.
-
-
1 issue received 4 new comments.
-
Devices reporting (X GB - few MB) will report X/2 GB device-ram value w3c/device-memory#1 (4 comments by @fmeawad, @igrigorik, @spanicker)
-
-
1 pull request opened.
-
Change the device-ram value based on the discussion in issue#1 w3c/device-memory#2, by @fmeawad.
-
-
1 pull request merged.
-
Change the device-ram value based on the discussion in issue#1 w3c/device-memory#2.
-
w3c/hr-time
-
1 issue opened.
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/hr-time#49, by @tobie.
-
-
1 issue closed.
-
Update worker reference w3c/hr-time#46.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Update workers refs w3c/hr-time#48, by @siusin.
-
-
1 pull request merged.
-
Update workers refs w3c/hr-time#48.
-
-
1 pull request received 1 new comment.
w3c/performance-timeline
-
2 issues opened.
-
WebIDL serializer has been deprecated in favor of toJSON operation w3c/performance-timeline#82, by @tobie.
-
Define buffering behaviors & hooks for queued (PerformanceObserver) entries w3c/performance-timeline#81, by @igrigorik.
-
-
2 issues received 9 new comments.
-
PerformanceObserver developer / RUM friendliness w3c/performance-timeline#79 (5 comments by @cvazac, @igrigorik, @nicjansma, @spanicker)
-
Clarity on buffered-until-onload (and buffers, buffers, everywhere) w3c/performance-timeline#78 (4 comments by @cvazac, @igrigorik)
-
-
1 pull request opened.
-
the `buffered` part of the processing algorithm needs to move above the potential short-circuit w3c/performance-timeline#80, by @cvazac.
-
-
1 pull request merged.
-
the `buffered` part of the processing algorithm needs to move above the potential short-circuit w3c/performance-timeline#80.
-
-
1 pull request received 1 new comment.
-
the `buffered` part of the processing algorithm needs to move above the potential short-circuit w3c/performance-timeline#80 (1 comment by @igrigorik)
-
w3c/charter-webperf
-
1 issue received 1 new comment.
-
Enable developers to create and queue custom PerformanceEntry objects w3c/charter-webperf#28 (1 comment by @igrigorik)
-
TR publications
-
3 documents published.
-
Navigation Timing Level 2 published twice as a Working Draft. History of Navigation Timing Level 2
-
Resource Hints published as a Working Draft. History of Resource Hints
-
Participants
-
1 organization joined.
-
Baidu, Inc. joined.
-
GitHub
w3c/performance-timeline
-
3 issues opened.
-
PerformanceObserver developer / RUM friendliness w3c/performance-timeline#79, by @nicjansma.
-
Clarity on buffered-until-onload (and buffers, buffers, everywhere) w3c/performance-timeline#78, by @nicjansma.
-
Add entryTypes method to enumerate type of entries observable via PerformanceObserver w3c/performance-timeline#77, by @spanicker.
-
-
1 issue closed.
-
Ability to observers past set of performance entries w3c/performance-timeline#56.
-
-
3 issues received 8 new comments.
-
Add entryTypes method to enumerate type of entries observable via PerformanceObserver w3c/performance-timeline#77 (6 comments by @igrigorik, @jfsiii, @spanicker)
-
Clarity on buffered-until-onload (and buffers, buffers, everywhere) w3c/performance-timeline#78 (1 comment by @nicjansma)
-
Ability to observers past set of performance entries w3c/performance-timeline#56 (1 comment by @igrigorik)
-
-
1 pull request merged.
-
`PerformanceObserverInit.buffered` and `add to performance entry buffer` flags w3c/performance-timeline#76.
-
-
1 pull request reopened.
-
`PerformanceObserverInit.buffered` and `add to performance entry buffer` flags w3c/performance-timeline#76, by @cvazac.
-
-
1 pull request received 10 new comments.
-
`PerformanceObserverInit.buffered` and `add to performance entry buffer` flags w3c/performance-timeline#76 (10 comments by @cvazac, @igrigorik)
-
w3c/reporting
-
2 issues opened.
-
The report having a property named `report` is confusing w3c/reporting#42, by @RByers.
-
Are report uploads supposed to send CORS preflights? w3c/reporting#41, by @estark37.
-
-
3 issues closed.
-
The report having a property named `report` is confusing w3c/reporting#42.
-
gh-pages copy not auto-updating w3c/reporting#31.
-
"Remove endpoint" is not handled when sending reports w3c/reporting#17.
-
-
4 issues received 22 new comments.
-
gh-pages copy not auto-updating w3c/reporting#31 (4 comments by @patrickkettner, @plehegar, @RByers)
-
The report having a property named `report` is confusing w3c/reporting#42 (3 comments by @mikewest, @RByers)
-
Are report uploads supposed to send CORS preflights? w3c/reporting#41 (3 comments by @estark37, @mikewest)
-
2 pull requests opened.
-
Rename 'report' member to 'body' w3c/reporting#43, by @RByers.
-
New auto deploy script w3c/reporting#40, by @plehegar.
-
-
3 pull requests merged.
-
Rename 'report' member to 'body' w3c/reporting#43.
-
Handle 'Remove endpoint' response in 'Send reports' algorithm. w3c/reporting#20.
-
New auto deploy script w3c/reporting#40.
-
-
2 pull requests closed.
-
update max-age section of explainer w3c/reporting#37.
-
Indentation fixes w3c/reporting#10.
-
-
3 pull requests received 3 new comments.
-
Handle 'Remove endpoint' response in 'Send reports' algorithm. w3c/reporting#20 (1 comment by @RByers)
w3c/server-timing
-
2 issues opened.
-
Linking to ResourceTiming w3c/server-timing#14, by @nicjansma.
-
Server-Timing Headers Read from Browser Cache w3c/server-timing#13, by @paulcalvano.
-
-
3 issues received 7 new comments.
-
Server-Timing Headers Read from Browser Cache w3c/server-timing#13 (5 comments by @andreas-marschke, @cvazac, @nicjansma)
-
Having duration with no start time makes it hard to profile servers with parallel processes. w3c/server-timing#10 (1 comment by @danielcompton)
-
-
1 pull request closed.
-
WIDL reference links are broken w3c/server-timing#6.
-
-
1 pull request received 1 new comment.
w3c/paint-timing
-
2 issues opened.
-
PerformanceTimeline or NavigationTiming support w3c/paint-timing#6, by @nicjansma.
-
Define processing algorithm w3c/paint-timing#4, by @igrigorik.
-
-
1 issue received 4 new comments.
-
PerformanceTimeline or NavigationTiming support w3c/paint-timing#6 (4 comments by @nicjansma, @spanicker)
-
-
1 pull request opened.
-
Link to processing algorithm discussion w3c/paint-timing#5, by @igrigorik.
-
-
1 pull request merged.
-
Link to processing algorithm discussion w3c/paint-timing#5.
-
w3c/longtasks
-
1 issue opened.
-
PerformanceTimeline support w3c/longtasks#26, by @nicjansma.
-
w3c/beacon
-
2 issues opened.
-
Privacy & Security section not current w3c/beacon#43, by @annevk.
-
maximum data size rules still seem ambiguous w3c/beacon#42, by @dbaron.
-
-
1 issue closed.
-
maximum data size rules still seem ambiguous w3c/beacon#42.
-
-
2 issues received 3 new comments.
-
1 pull request opened.
-
Update privacy & security section to reflect CORS processing logic. w3c/beacon#44, by @igrigorik.
-
-
2 pull requests received 15 new comments.
-
Update privacy & security section to reflect CORS processing logic. w3c/beacon#44 (11 comments by @annevk, @igrigorik)
-
w3c/navigation-timing
-
1 issue opened.
-
Obsolete partial interface to the Performance has incorrect exposure setting w3c/navigation-timing#70, by @saschanaz.
-
-
1 issue closed.
-
Need tests for TAO w3c/navigation-timing#58.
-
-
2 issues received 6 new comments.
-
Obsolete partial interface to the Performance has incorrect exposure setting w3c/navigation-timing#70 (5 comments by @igrigorik, @plehegar, @saschanaz)
-
-
3 pull requests opened.
-
editorial: use absolute URL for svg image w3c/navigation-timing#69, by @marcoscaceres.
-
fix: missing timestamp-diagram.svg w3c/navigation-timing#68, by @marcoscaceres.
-
chore(.travis.yml): run link checker before publishing w3c/navigation-timing#67, by @marcoscaceres.
-
-
1 pull request merged.
-
fix: missing timestamp-diagram.svg w3c/navigation-timing#68.
-
-
2 pull requests closed.
-
chore(.travis.yml): run link checker before publishing w3c/navigation-timing#67.
-
editorial: use absolute URL for svg image w3c/navigation-timing#69.
-
-
5 pull requests received 37 new comments.
-
chore(.travis.yml): run link checker before publishing w3c/navigation-timing#67 (13 comments by @igrigorik, @marcoscaceres, @yoavweiss)
-
editorial: use absolute URL for svg image w3c/navigation-timing#69 (8 comments by @dontcallmedom, @igrigorik, @marcoscaceres)
w3c/charter-webperf
-
1 issue received 1 new comment.
-
Expose First Paint, First Contentful Paint, ... to developers w3c/charter-webperf#32 (1 comment by @ctolkien)
-
w3c/resource-timing
-
1 issue opened.
-
ResourceTiming entry for the main (i.e. Initial) page/request w3c/resource-timing#111, by @mvadu.
-
-
2 issues closed.
-
ResourceTiming entry for the main (i.e. Initial) page/request w3c/resource-timing#111.
-
Missing TAO tests w3c/resource-timing#92.
-
-
5 issues received 9 new comments.
-
ResourceTiming entry for the main (i.e. Initial) page/request w3c/resource-timing#111 (4 comments by @igrigorik, @mvadu)
-
Server pushed resources in ResourceTiming w3c/resource-timing#53 (2 comments by @igrigorik, @nbeloglazov)
-
InitiatorType of service worker navigation preload w3c/resource-timing#110 (1 comment by @igrigorik)
-
w3c/hr-time
-
2 issues received 3 new comments.
-
1 pull request opened.
-
Test driven w3c/hr-time#47, by @plehegar.
-
-
1 pull request merged.
-
Test driven w3c/hr-time#47.
-
-
1 pull request received 8 new comments.
w3c/device-memory
-
1 issue opened.
-
Devices reporting (X GB - few MB) will report X/2 GB device-ram value w3c/device-memory#1, by @fmeawad.
-
-
1 issue received 4 new comments.
-
Devices reporting (X GB - few MB) will report X/2 GB device-ram value w3c/device-memory#1 (4 comments by @igrigorik, @mariakhomenko, @spanicker)
-
w3c/requestidlecallback
-
1 issue reopened.
-
timeRemaining() is badly defined, deadline argument w3c/requestidlecallback#55, by @swickr.
-
-
2 issues received 3 new comments.
-
timeRemaining() is badly defined, deadline argument w3c/requestidlecallback#55 (2 comments by @annevk, @swickr)
-
w3c/web-performance
-
2 pull requests opened.
-
Suggest using the type:untestable label for wpt w3c/web-performance#18, by @foolip.
-
Make the contribution process clearer w3c/web-performance#17, by @plehegar.
-
-
2 pull requests merged.
-
Suggest using the type:untestable label for wpt w3c/web-performance#18.
-
Make the contribution process clearer w3c/web-performance#17.
-
-
2 pull requests received 6 new comments.
-
Make the contribution process clearer w3c/web-performance#17 (4 comments by @igrigorik, @toddreifsteck)
-
Suggest using the type:untestable label for wpt w3c/web-performance#18 (2 comments by @foolip, @plehegar)
-
w3c/perf-timing-primer
-
1 pull request merged.
-
Typo fix w3c/perf-timing-primer#9.
-
-
1 pull request received 1 new comment.
TR publications
-
3 documents published.
-
Beacon published as a Candidate Recommendation Snapshot. History of Beacon
-
Navigation Timing Level 2 published twice as a Working Draft. History of Navigation Timing Level 2
-
Participants
-
1 organization joined.
-
Alibaba Group joined.
-
-
1 organization left.
-
Academia Animartec S.L. left.
-
GitHub
w3c/perf-timing-primer
-
1 pull request opened.
-
Editorial fixes w3c/perf-timing-primer#8, by @xfq.
-
-
1 pull request merged.
-
Editorial fixes w3c/perf-timing-primer#8.
-
-
1 pull request received 1 new comment.
w3c/performance-timeline
-
1 pull request received 27 new comments.
-
`PerformanceObserverInit.buffered` and `add to performance entry buffer` flags w3c/performance-timeline#76 (27 comments by @cvazac, @igrigorik, @spanicker, @yoavweiss)
-
w3c/resource-timing
-
3 issues opened.
-
InitiatorType of service worker navigation preload w3c/resource-timing#110, by @horo-t.
-
Prose link to PerformanceEntry is broken w3c/resource-timing#108, by @annevk.
-
Link PerformanceEntry in IDL w3c/resource-timing#107, by @annevk.
-
-
1 issue closed.
-
Custom ABNF Syntax specification w3c/resource-timing#99.
-
-
1 issue received 2 new comments.
-
Resource Timing entries within the context of a service worker for handled requests? w3c/resource-timing#88 (2 comments by @irori, @spanicker)
-
-
1 pull request opened.
-
ABNF uses list extension w3c/resource-timing#109, by @plehegar.
-
-
1 pull request merged.
-
ABNF uses list extension w3c/resource-timing#109.
-
-
1 pull request received 5 new comments.
w3c/longtasks
-
1 issue opened.
-
Document reasons for "unknown" attribution w3c/longtasks#25, by @spanicker.
-
-
1 issue closed.
-
Remove "Not Ready For Implementation" w3c/longtasks#22.
-
-
1 issue received 8 new comments.
-
Remove "Not Ready For Implementation" w3c/longtasks#22 (8 comments by @igrigorik, @plehegar, @spanicker, @tabatkins, @yoavweiss)
-
-
2 pull requests opened.
-
Fix bikeshed syntax for URLs for author affiliations. w3c/longtasks#24, by @dbaron.
-
Update index.html w3c/longtasks#23, by @foolip.
-
-
1 pull request merged.
-
Update index.html w3c/longtasks#23.
-
-
2 pull requests received 5 new comments.
-
Fix bikeshed syntax for URLs for author affiliations. w3c/longtasks#24 (3 comments by @dbaron, @igrigorik, @tabatkins)
-
w3c/navigation-timing
-
3 issues opened.
-
Please fix at least your broken links, if you want anyone to ever make any sense of your specs w3c/navigation-timing#65, by @bzbarsky.
-
IDL should xref PerformanceResourceTiming w3c/navigation-timing#64, by @annevk.
-
Please integrate directly with HTML w3c/navigation-timing#63, by @annevk.
-
-
2 issues received 3 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 (2 comments by @bzbarsky, @tripu)
-
-
1 pull request opened.
-
fix broken links w3c/navigation-timing#66, by @siusin.
-
-
1 pull request merged.
-
fix broken links w3c/navigation-timing#66.
-
-
1 pull request received 21 new comments.
-
fix broken links w3c/navigation-timing#66 (21 comments by @bzbarsky, @dontcallmedom, @igrigorik, @marcoscaceres, @siusin, @xfq)
-
w3c/hr-time
-
2 issues opened.
-
Update worker reference w3c/hr-time#46, by @igrigorik.
-
Performance.now() should use an underlying primitive w3c/hr-time#44, by @plehegar.
-
-
2 issues received 6 new comments.
-
Performance.now() should use an underlying primitive w3c/hr-time#44 (4 comments by @igrigorik, @plehegar)
-
-
1 pull request opened.
-
Remove one error and several respec warnings w3c/hr-time#45, by @plehegar.
-
-
1 pull request merged.
-
Remove one error and several respec warnings w3c/hr-time#45.
-
-
1 pull request closed.
-
Dummy change. please ignore w3c/hr-time#43.
-
-
2 pull requests received 8 new comments.
-
Remove one error and several respec warnings w3c/hr-time#45 (7 comments by @annevk, @igrigorik, @plehegar)
-
w3c/reporting
-
3 issues received 3 new comments.
-
What happens if *.foo.com and bar.foo.com configure differing endpoints? w3c/reporting#24 (1 comment by @juliatuttle)
-
w3c/requestidlecallback
-
4 issues opened.
-
Don't monkey patch the event loop algorithm w3c/requestidlecallback#57, by @annevk.
-
Defined IdleDeadline internal layout w3c/requestidlecallback#56, by @annevk.
-
timeRemaining() is badly defined, deadline argument w3c/requestidlecallback#55, by @annevk.
-
timeRemaining() is badly defined w3c/requestidlecallback#54, by @annevk.
-
-
2 issues received 9 new comments.
-
Don't monkey patch the event loop algorithm w3c/requestidlecallback#57 (8 comments by @annevk, @domenic, @plehegar)
-
timeRemaining() is badly defined, deadline argument w3c/requestidlecallback#55 (1 comment by @plehegar)
-
w3c/beacon
-
1 issue closed.
-
Transition Level 1 to CR w3c/beacon#36.
-
-
1 issue received 2 new comments.
w3c/server-timing
-
1 issue opened.
-
ABNF for metric-value w3c/server-timing#12, by @reschke.
-
-
1 issue received 2 new comments.
TR publications
-
7 documents published.
-
Resource Timing Level 1 published as a Candidate Recommendation Snapshot. History of Resource Timing Level 1
-
Page Visibility Level 2 published as a Candidate Recommendation Snapshot. History of Page Visibility Level 2
-
Resource Timing Level 2 published twice as a Working Draft. History of Resource Timing Level 2
-
Navigation Timing Level 2 published twice as a Working Draft. History of Navigation Timing Level 2
-
Resource Hints published as a Working Draft. History of Resource Hints
-
GitHub
w3c/performance-timeline
-
2 issues opened.
-
Add support for flushing observer via `takeRecords()` w3c/performance-timeline#74, by @igrigorik.
-
Redundant throw should be removed w3c/performance-timeline#73, by @marcoscaceres.
-
-
3 issues closed.
-
Redundant throw should be removed w3c/performance-timeline#73.
-
Clarify disconnecting a PerformanceObserver that has observed entries w3c/performance-timeline#66.
-
Add a note regarding feature detection options for new entry types w3c/performance-timeline#64.
-
-
1 issue received 7 new comments.
-
Clarify disconnecting a PerformanceObserver that has observed entries w3c/performance-timeline#66 (7 comments by @hiikezoe, @igrigorik, @JosephPecoraro, @spanicker, @toddreifsteck)
-
-
3 pull requests opened.
-
`PerformanceObserverInit.buffered` and `add to performance entry buffer` flags w3c/performance-timeline#76, by @cvazac.
-
Refactor, shuffle order, improve navigation w3c/performance-timeline#75, by @igrigorik.
-
Fixup: ReSpec warnings, structure, etc. w3c/performance-timeline#72, by @marcoscaceres.
-
-
4 pull requests merged.
-
Fixup: ReSpec warnings, structure, etc. w3c/performance-timeline#72.
-
Refactor, shuffle order, improve navigation w3c/performance-timeline#75.
-
add a note regarding feature detection w3c/performance-timeline#70.
-
fix Markup errors w3c/performance-timeline#71.
-
-
5 pull requests received 52 new comments.
-
Fixup: ReSpec warnings, structure, etc. w3c/performance-timeline#72 (24 comments by @igrigorik, @marcoscaceres, @plehegar, @tobie)
-
`PerformanceObserverInit.buffered` and `add to performance entry buffer` flags w3c/performance-timeline#76 (15 comments by @cvazac, @dontcallmedom, @igrigorik, @yoavweiss)
-
add a note regarding feature detection w3c/performance-timeline#70 (6 comments by @igrigorik, @yoavweiss)
-
Refactor, shuffle order, improve navigation w3c/performance-timeline#75 (4 comments by @igrigorik, @plehegar, @toddreifsteck)
-
w3c/user-timing
-
3 issues opened.
-
Should performance.measure() work with resource timing entries? w3c/user-timing#27, by @philipwalton.
-
measure() may throw InvalidAccessError w3c/user-timing#26, by @plehegar.
-
Provide a way to associate warnings with measurements w3c/user-timing#25, by @gaearon.
-
-
1 issue closed.
-
Enable namespace-based subscription for mark / measure w3c/user-timing#24.
-
-
3 issues received 17 new comments.
-
Enable namespace-based subscription for mark / measure w3c/user-timing#24 (10 comments by @eliperelman, @gaearon, @igrigorik, @nicjansma, @spanicker)
-
Provide a way to associate warnings with measurements w3c/user-timing#25 (6 comments by @eliperelman, @gaearon, @igrigorik, @toddreifsteck)
-
Should performance.measure() work with resource timing entries? w3c/user-timing#27 (1 comment by @igrigorik)
-
w3c/reporting
-
1 issue closed.
-
Sample reports aren't valid JSON w3c/reporting#33.
-
-
1 issue reopened.
-
gh-pages copy not auto-updating w3c/reporting#31, by @RByers.
-
-
5 issues received 9 new comments.
-
Enable reporting via meta tag (or otherwise via JS)? w3c/reporting#28 (3 comments by @igrigorik, @juliatuttle, @RByers)
-
-
2 pull requests merged.
-
update reports syntax to valid JSON w3c/reporting#36.
-
update travis script to fix publishing w3c/reporting#35.
-
-
1 pull request received 2 new comments.
w3c/resource-timing
-
1 issue opened.
-
Resource entry limit in Internet Explorer 10 w3c/resource-timing#104, by @dhineshbabu.
-
-
3 issues received 13 new comments.
-
Increase limit of 150 for PerformanceEntrys? w3c/resource-timing#89 (7 comments by @gaearon, @igrigorik, @nicjansma, @nolanlawson)
-
Resource entry limit in Internet Explorer 10 w3c/resource-timing#104 (3 comments by @igrigorik, @JosephPecoraro, @nolanlawson)
-
-
3 pull requests opened.
-
update the editor's draft for v2 w3c/resource-timing#106, by @siusin.
-
Replaced TAO section with L3 version w3c/resource-timing#105, by @plehegar.
-
More HTTP -> HTTPS w3c/resource-timing#103, by @xfq.
-
-
4 pull requests merged.
-
update the editor's draft for v2 w3c/resource-timing#106.
-
Replaced TAO section with L3 version w3c/resource-timing#105.
-
Merge V2 into gh-pages w3c/resource-timing#97.
-
More HTTP -> HTTPS w3c/resource-timing#103.
-
-
2 pull requests received 2 new comments.
w3c/longtasks
-
2 issues opened.
-
Remove "Not Ready For Implementation" w3c/longtasks#22, by @igrigorik.
-
Update links to w3c w3c/longtasks#21, by @igrigorik.
-
w3c/server-timing
-
1 issue opened.
-
Spec should clarify that metrics are in seconds w3c/server-timing#11, by @dpogue.
-
-
1 issue closed.
-
Spec should clarify that metrics are in seconds w3c/server-timing#11.
-
-
1 issue received 3 new comments.
-
Spec should clarify that metrics are in seconds w3c/server-timing#11 (3 comments by @dpogue, @igrigorik, @sroussey)
-
w3c/hr-time
-
1 issue received 7 new comments.
-
Add prompt to unload test w3c/hr-time#32 (7 comments by @foolip, @igrigorik, @RByers, @siusin, @toddreifsteck)
-
-
2 pull requests opened.
-
Dummy change. please ignore w3c/hr-time#43, by @plehegar.
-
Dummy change. please ignore w3c/hr-time#42, by @plehegar.
-
-
1 pull request closed.
-
Dummy change. please ignore w3c/hr-time#42.
-
-
1 pull request received 1 new comment.
w3c/navigation-timing
-
2 issues received 6 new comments.
-
data bias issues due to deferring reporting of all nav timing metrics to the load event w3c/navigation-timing#50 (3 comments by @igrigorik, @irori, @spanicker)
-
Report URL in "name" attribute (instead of "document") w3c/navigation-timing#59 (3 comments by @foolip, @igrigorik, @toddreifsteck)
-
w3c/beacon
-
1 issue closed.
-
Ambiguity on "maximum data size" limit and enforcement w3c/beacon#38.
-
-
2 issues received 2 new comments.
-
1 pull request merged.
-
Enforce payload limits via Fetch API w3c/beacon#39.
-
-
1 pull request received 1 new comment.
w3c/charter-webperf
-
1 pull request merged.
-
Adding new specifications to charter w3c/charter-webperf#34.
-
-
1 pull request received 1 new comment.
TR publications
-
2 documents published.
-
Navigation Timing Level 2 published twice as a Working Draft. History of Navigation Timing Level 2
-
GitHub
w3c/performance-timeline
-
2 issues opened.
-
Add "longtask" in the NOTE on valid entry types w3c/performance-timeline#69, by @spanicker.
-
performance.timing shouldn't be deprecated w3c/performance-timeline#68, by @rniwa.
-
-
4 issues closed.
-
performance.timing shouldn't be deprecated w3c/performance-timeline#68.
-
Clarify sort order for entries with equivalent startTime w3c/performance-timeline#67.
-
Add "longtask" in the NOTE on valid entry types w3c/performance-timeline#69.
-
Clarify how PerformanceObserver invokes the callback - arguments and `this` value w3c/performance-timeline#65.
-
-
4 issues received 16 new comments.
-
Clarify disconnecting a PerformanceObserver that has observed entries w3c/performance-timeline#66 (9 comments by @hiikezoe, @igrigorik, @JosephPecoraro, @overholt, @spanicker, @toddreifsteck)
-
performance.timing shouldn't be deprecated w3c/performance-timeline#68 (5 comments by @igrigorik, @rniwa, @toddreifsteck)
-
Clarify how PerformanceObserver invokes the callback - arguments and `this` value w3c/performance-timeline#65 (1 comment by @toddreifsteck)
-
Clarify sort order for entries with equivalent startTime w3c/performance-timeline#67 (1 comment by @toddreifsteck)
-
-
2 pull requests opened.
-
fix Markup errors w3c/performance-timeline#71, by @siusin.
-
add a note regarding feature detection w3c/performance-timeline#70, by @igrigorik.
-
-
1 pull request received 6 new comments.
w3c/charter-webperf
-
1 pull request opened.
-
Adding new specifications to charter w3c/charter-webperf#34, by @igrigorik.
-
-
1 pull request received 9 new comments.
-
Adding new specifications to charter w3c/charter-webperf#34 (9 comments by @igrigorik, @plehegar, @yoavweiss)
-
w3c/reporting
-
7 issues opened.
-
Add priority field to endpoint tuple and client w3c/reporting#39, by @juliatuttle.
-
Sample reports aren't valid JSON w3c/reporting#33, by @RByers.
-
Default value for max-age? w3c/reporting#32, by @RByers.
-
gh-pages copy not auto-updating w3c/reporting#31, by @RByers.
-
feedback on report failure? w3c/reporting#30, by @patrickkettner.
-
Observe reports from JavaScript w3c/reporting#29, by @RByers.
-
Enable reporting via meta tag (or otherwise via JS)? w3c/reporting#28, by @RByers.
-
-
2 issues closed.
-
feedback on report failure? w3c/reporting#30.
-
Allow origins to provide input into report scheduling w3c/reporting#18.
-
-
10 issues received 61 new comments.
-
Default value for max-age? w3c/reporting#32 (13 comments by @igrigorik, @juliatuttle, @patrickkettner, @RByers)
-
How to support "deprecation" and "intervention" use cases w3c/reporting#27 (9 comments by @igrigorik, @mikewest, @patrickkettner, @RByers, @ScottHelme)
-
feedback on report failure? w3c/reporting#30 (8 comments by @igrigorik, @juliatuttle, @patrickkettner)
-
Enable reporting via meta tag (or otherwise via JS)? w3c/reporting#28 (8 comments by @igrigorik, @patrickkettner, @RByers)
-
Observe reports from JavaScript w3c/reporting#29 (7 comments by @igrigorik, @juliatuttle, @mikewest, @patrickkettner, @RByers)
-
What happens if *.foo.com and bar.foo.com configure differing endpoints? w3c/reporting#24 (4 comments by @igrigorik, @juliatuttle, @patrickkettner)
-
Why is report.origin a separate field? w3c/reporting#25 (3 comments by @juliatuttle, @patrickkettner)
-
Allow origins to provide input into report scheduling w3c/reporting#18 (2 comments by @juliatuttle, @patrickkettner)
-
Clarify behavior around "send reports" with active delivery attempts w3c/reporting#11 (1 comment by @juliatuttle)
-
-
5 pull requests opened.
-
remove garbage collection. fixes #23 w3c/reporting#38, by @patrickkettner.
-
update max-age section of explainer w3c/reporting#37, by @patrickkettner.
-
update reports syntax to valid JSON w3c/reporting#36, by @patrickkettner.
-
update travis script to fix publishing w3c/reporting#35, by @patrickkettner.
-
Add Explainer w3c/reporting#34, by @RByers.
-
-
1 pull request merged.
-
Add Explainer w3c/reporting#34.
-
-
5 pull requests received 7 new comments.
-
update reports syntax to valid JSON w3c/reporting#36 (3 comments by @mathiasbynens, @patrickkettner)
-
Handle 'Remove endpoint' response in 'Send reports' algorithm. w3c/reporting#20 (1 comment by @patrickkettner)
-
w3c/navigation-timing
-
2 issues closed.
-
Effect of canceled navigation on navigation timing w3c/navigation-timing#60.
-
data bias issues due to deferring reporting of all nav timing metrics to the load event w3c/navigation-timing#50.
-
-
2 issues received 3 new comments.
-
Effect of canceled navigation on navigation timing w3c/navigation-timing#60 (2 comments by @bripkens, @igrigorik)
-
Report URL in "name" attribute (instead of "document") w3c/navigation-timing#59 (1 comment by @igrigorik)
-
-
2 pull requests opened.
-
Add user abort clause w3c/navigation-timing#62, by @igrigorik.
-
set name to document address w3c/navigation-timing#61, by @igrigorik.
-
-
1 pull request merged.
-
Add user abort clause w3c/navigation-timing#62.
-
-
1 pull request received 1 new comment.
w3c/server-timing
-
4 issues opened.
-
Having duration with no start time makes it hard to profile servers with parallel processes. w3c/server-timing#10, by @aickin.
-
Secure context only w3c/server-timing#9, by @marcoscaceres.
-
Metric values are timestamps in PerformanceServerTiming interface w3c/server-timing#7, by @bripkens.
-
Rendering bug in the spec w3c/server-timing#5, by @paulirish.
-
-
3 issues closed.
-
Allow user to get timing information for when a metric was received w3c/server-timing#4.
-
Rendering bug in the spec w3c/server-timing#5.
-
Metric values are timestamps in PerformanceServerTiming interface w3c/server-timing#7.
-
-
5 issues received 25 new comments.
-
Rendering bug in the spec w3c/server-timing#5 (15 comments by @igrigorik, @marcoscaceres, @varemenos)
-
Having duration with no start time makes it hard to profile servers with parallel processes. w3c/server-timing#10 (5 comments by @aickin, @igrigorik, @sroussey)
-
Metric values are timestamps in PerformanceServerTiming interface w3c/server-timing#7 (2 comments by @bripkens, @igrigorik)
-
Allow user to get timing information for when a metric was received w3c/server-timing#4 (1 comment by @igrigorik)
-
-
2 pull requests opened.
-
Refactor: convert to markdown w3c/server-timing#8, by @marcoscaceres.
-
WIDL reference links are broken w3c/server-timing#6, by @bripkens.
-
-
1 pull request merged.
-
Refactor: convert to markdown w3c/server-timing#8.
-
-
2 pull requests received 6 new comments.
w3c/hr-time
-
2 issues closed.
-
Time Origin in Workers - official moment of creation or not? w3c/hr-time#41.
-
2 issues received 2 new comments.
-
[Maintenance, reminder] Cycle environment variables that were encrypted with Travis w3c/hr-time#38 (1 comment by @igrigorik)
-
Time Origin in Workers - official moment of creation or not? w3c/hr-time#41 (1 comment by @JosephPecoraro)
-
-
1 pull request received 1 new comment.
w3c/beacon
-
1 pull request received 2 new comments.
w3c/resource-timing
-
6 issues opened.
-
Expose a way to link a call to fetch to an individual PerformanceResourceTiming object w3c/resource-timing#102, by @n8schloss.
-
Clarify what constitutes a "downloadable resource" w3c/resource-timing#100, by @JosephPecoraro.
-
Custom ABNF Syntax specification w3c/resource-timing#99, by @JosephPecoraro.
-
Graphic should indicate fetchStart is a required field, not a parenthesized zeroed field w3c/resource-timing#98, by @JosephPecoraro.
-
Clarify behavior of setResourceTimingBufferSize w3c/resource-timing#96, by @JosephPecoraro.
-
Clarify resourcetimingbufferfull conditions w3c/resource-timing#95, by @JosephPecoraro.
-
-
6 issues received 11 new comments.
-
Clarify what constitutes a "downloadable resource" w3c/resource-timing#100 (3 comments by @igrigorik, @JosephPecoraro)
-
Increase limit of 150 for PerformanceEntrys? w3c/resource-timing#89 (2 comments by @igrigorik, @nicjansma)
-
Determine whether to wait until after responseEnd to queue entry for ResourceTiming w3c/resource-timing#93 (2 comments by @JosephPecoraro, @spanicker)
-
Clarify when entry is added to performance entry buffer w3c/resource-timing#82 (1 comment by @JosephPecoraro)
-
Is it well defined when the "add a PerformanceResourceTiming entry" algorithm should run? w3c/resource-timing#55 (1 comment by @JosephPecoraro)
-
-
2 pull requests opened.
-
set up auto-pub on V2 w3c/resource-timing#101, by @siusin.
-
Merge V2 into gh-pages w3c/resource-timing#97, by @yoavweiss.
-
-
1 pull request merged.
-
set up auto-pub on V2 w3c/resource-timing#101.
-
-
2 pull requests received 3 new comments.
w3c/longtasks
-
5 issues opened.
-
Does PerformanceLongTaskTiming's attribution attribute always return the same value? w3c/longtasks#20, by @foolip.
-
Better understand correlating long tasks from different iframes w3c/longtasks#18, by @spanicker.
-
Should containerSrc be resolved as a URL? w3c/longtasks#17, by @foolip.
-
Editorial issues with the processing model w3c/longtasks#15, by @domenic.
-
-
3 issues closed.
-
Use [ w3c/longtasks#19.
-
Handle longtask attribution for embed & object in addition to iframe w3c/longtasks#13.
-
Should containerSrc be resolved as a URL? w3c/longtasks#17.
-
-
4 issues received 13 new comments.
-
Should containerSrc be resolved as a URL? w3c/longtasks#17 (6 comments by @domenic, @foolip, @spanicker)
-
Does PerformanceLongTaskTiming's attribution attribute always return the same value? w3c/longtasks#20 (5 comments by @domenic, @foolip, @spanicker)
-
Handle longtask attribution for embed & object in addition to iframe w3c/longtasks#13 (1 comment by @spanicker)
-
-
1 pull request opened.
-
Bikeshed w3c/longtasks#16, by @tabatkins.
-
-
1 pull request merged.
-
Bikeshed w3c/longtasks#16.
-
-
1 pull request received 1 new comment.
w3c/user-timing
-
1 issue received 1 new comment.
TR publications
-
2 documents published.
-
Cooperative Scheduling of Background Tasks published as a Candidate Recommendation Snapshot. History of Cooperative Scheduling of Background Tasks
-
Cooperative Scheduling of Background Tasks published as a Working Draft. History of Cooperative Scheduling of Background Tasks
-
GitHub
w3c/user-timing
-
2 issues opened.
-
Enable namespace-based subscription for mark / measure w3c/user-timing#24, by @spanicker.
-
mark() and measure() return PerformanceEntries w3c/user-timing#23, by @toddreifsteck.
-
-
4 issues received 4 new comments.
-
What does "navigationStart" mean as a second argument to performance.measure() in a web worker? w3c/user-timing#22 (1 comment by @JosephPecoraro)
w3c/requestidlecallback
-
2 issues closed.
-
Transition Level 1 to CR w3c/requestidlecallback#48.
-
diagram with frame commit and vsync is inaccurate for some browsers w3c/requestidlecallback#44.
-
-
2 issues received 7 new comments.
-
Transition Level 1 to CR w3c/requestidlecallback#48 (5 comments by @igrigorik, @plehegar, @rmcilroy)
-
diagram with frame commit and vsync is inaccurate for some browsers w3c/requestidlecallback#44 (2 comments by @igrigorik, @rmcilroy)
-
-
2 pull requests opened.
-
added link to tests and implementation report w3c/requestidlecallback#53, by @siusin.
-
Update diagrams to reference be related to HTML event loop. w3c/requestidlecallback#52, by @rmcilroy.
-
-
2 pull requests merged.
-
added link to tests and implementation report w3c/requestidlecallback#53.
-
Update diagrams to reference be related to HTML event loop. w3c/requestidlecallback#52.
-
-
2 pull requests received 4 new comments.
-
added link to tests and implementation report w3c/requestidlecallback#53 (2 comments by @igrigorik, @rmcilroy)
-
Update diagrams to reference be related to HTML event loop. w3c/requestidlecallback#52 (2 comments by @igrigorik, @rmcilroy)
-
w3c/performance-timeline
-
4 issues opened.
-
Clarify sort order for entries with equivalent startTime w3c/performance-timeline#67, by @JosephPecoraro.
-
Clarify disconnecting a PerformanceObserver that has observed entries w3c/performance-timeline#66, by @JosephPecoraro.
-
Clarify how PerformanceObserver invokes the callback - arguments and `this` value w3c/performance-timeline#65, by @JosephPecoraro.
-
Add a note regarding feature detection options for new entry types w3c/performance-timeline#64, by @yoavweiss.
-
-
4 issues received 16 new comments.
-
Add a note regarding feature detection options for new entry types w3c/performance-timeline#64 (8 comments by @igrigorik, @spanicker, @yoavweiss)
-
Ability to observers past set of performance entries w3c/performance-timeline#56 (6 comments by @igrigorik, @nicjansma, @rniwa, @yoavweiss)
-
Clarify sort order for entries with equivalent startTime w3c/performance-timeline#67 (1 comment by @JosephPecoraro)
-
Clarify disconnecting a PerformanceObserver that has observed entries w3c/performance-timeline#66 (1 comment by @JosephPecoraro)
-
w3c/hr-time
-
2 issues opened.
-
Time Origin in Workers - official moment of creation or not? w3c/hr-time#41, by @JosephPecoraro.
-
Why is Performance an EventTarget? w3c/hr-time#40, by @JosephPecoraro.
-
-
1 issue closed.
-
Why is Performance an EventTarget? w3c/hr-time#40.
-
-
2 issues received 4 new comments.
-
Time Origin in Workers - official moment of creation or not? w3c/hr-time#41 (2 comments by @igrigorik, @JosephPecoraro)
w3c/resource-timing
-
5 issues opened.
-
Clarify whether UA can clear the buffer under memory pressure w3c/resource-timing#94, by @spanicker.
-
Determine whether to wait until after responseEnd to queue entry for ResourceTiming w3c/resource-timing#93, by @spanicker.
-
Missing TAO tests w3c/resource-timing#92, by @igrigorik.
-
mark() and measure() return PerformanceEntries w3c/resource-timing#91, by @nolanlawson.
-
Add response status codes for resources in Resource Timing API. w3c/resource-timing#90, by @vaibhavtripathi.
-
-
1 issue closed.
-
mark() and measure() return PerformanceEntries w3c/resource-timing#91.
-
-
6 issues received 18 new comments.
-
Increase limit of 150 for PerformanceEntrys? w3c/resource-timing#89 (6 comments by @igrigorik, @nicjansma, @nolanlawson)
-
Server pushed resources in ResourceTiming w3c/resource-timing#53 (4 comments by @igrigorik, @valour01)
-
Determine whether to wait until after responseEnd to queue entry for ResourceTiming w3c/resource-timing#93 (3 comments by @nicjansma, @yoavweiss)
-
Clarify whether UA can clear the buffer under memory pressure w3c/resource-timing#94 (2 comments by @n8schloss, @yoavweiss)
-
mark() and measure() return PerformanceEntries w3c/resource-timing#91 (2 comments by @igrigorik, @toddreifsteck)
-
Add response status codes for resources in Resource Timing API. w3c/resource-timing#90 (1 comment by @yoavweiss)
-
w3c/beacon
-
2 issues opened.
-
Tests for CORS and sendBeacon() w3c/beacon#41, by @annevk.
-
w3c/longtasks
-
6 issues opened.
-
Provide an option for overriding the 50ms threshold w3c/longtasks#14, by @spanicker.
-
Handle longtask attribution for embed & object in addition to iframe w3c/longtasks#13, by @spanicker.
-
Processing model Google doc is not public w3c/longtasks#12, by @domenic.
-
Specifying the attributes of each object more rigorously w3c/longtasks#11, by @domenic.
-
s/PerformanceTaskTiming/PerformanceLongTaskTiming/ w3c/longtasks#10, by @domenic.
-
TaskAttributionTiming[] syntax is not valid Web IDL w3c/longtasks#9, by @domenic.
-
-
2 issues closed.
-
s/PerformanceTaskTiming/PerformanceLongTaskTiming/ w3c/longtasks#10.
-
Processing model Google doc is not public w3c/longtasks#12.
-
-
6 issues received 12 new comments.
-
Handle longtask attribution for embed & object in addition to iframe w3c/longtasks#13 (6 comments by @domenic, @igrigorik, @spanicker)
-
TaskAttributionTiming[] syntax is not valid Web IDL w3c/longtasks#9 (2 comments by @domenic, @spanicker)
-
-
2 pull requests opened.
-
A bunch of nits w3c/longtasks#8, by @yoavweiss.
-
Update with API changes: addition of "attribution" field w3c/longtasks#7, by @panickers.
-
-
2 pull requests merged.
-
A bunch of nits w3c/longtasks#8.
-
Update with API changes: addition of "attribution" field w3c/longtasks#7.
-
-
1 pull request received 1 new comment.
w3c/reporting
-
1 issue opened.
-
How to support "deprecation" and "intervention" use cases w3c/reporting#27, by @RByers.
-
-
1 issue received 3 new comments.
-
How to support "deprecation" and "intervention" use cases w3c/reporting#27 (3 comments by @igrigorik, @n8schloss, @nicjansma)
-
w3c/navigation-timing
-
1 issue opened.
-
Effect of canceled navigation on navigation timing w3c/navigation-timing#60, by @bripkens.
-
-
2 issues received 9 new comments.
-
Report URL in "name" attribute (instead of "document") w3c/navigation-timing#59 (8 comments by @cvazac, @igrigorik, @nicjansma, @spanicker, @toddreifsteck)
-
data bias issues due to deferring reporting of all nav timing metrics to the load event w3c/navigation-timing#50 (1 comment by @spanicker)
-
w3c/perf-timing-primer
-
1 issue opened.
-
https://www.w3.org/TR/perf-timing-primer/ leads to 404 w3c/perf-timing-primer#7, by @lmedini.
-
-
1 issue received 2 new comments.
-
https://www.w3.org/TR/perf-timing-primer/ leads to 404 w3c/perf-timing-primer#7 (2 comments by @igrigorik, @siusin)
-