Web Performance Working Group - Activity in 2015
No matches.
TR publications
-
6 documents published.
-
Beacon published as a Working Draft. History of Beacon
-
Cooperative Scheduling of Background Tasks published as a Working Draft. History of Cooperative Scheduling of Background Tasks
-
Frame Timing published as a Working Draft. History of Frame Timing
-
Performance Timeline Level 2 published twice as a Working Draft. History of Performance Timeline Level 2
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
GitHub
w3c/hr-time
-
1 issue closed.
-
Please add a giant red warning to http://www.w3.org/TR/hr-time/ w3c/hr-time#15.
-
-
4 issues received 25 new comments.
-
Translating high resolution timestamps between globals w3c/hr-time#22 (20 comments by @DigiTec, @igrigorik, @natduca, @sicking, @toddreifsteck)
-
Should time origin be defined in terms of a monotonic clock? w3c/hr-time#21 (1 comment by @igrigorik)
-
Please add a giant red warning to http://www.w3.org/TR/hr-time/ w3c/hr-time#15 (1 comment by @plehegar)
-
w3c/web-performance
-
1 issue opened.
-
Need to inline the CSS in the HTML w3c/web-performance#8, by @plehegar.
-
w3c/beacon
-
1 issue opened.
-
Is "ensuring" correct? w3c/beacon#21, by @npdoty.
-
-
5 issues closed.
-
Request coalescing as a platform primitive? w3c/beacon#20.
-
Fix broken links w3c/beacon#12.
-
Give guidelines on unload/visibilitystate/pagehide w3c/beacon#13.
-
Privacy section is misguided w3c/beacon#14.
-
editorial comments w3c/beacon#18.
-
-
1 issue reopened.
-
privacy considerations w3c/beacon#17, by @npdoty.
-
-
8 issues received 18 new comments.
-
Request coalescing as a platform primitive? w3c/beacon#20 (2 comments by @igrigorik, @toddreifsteck)
-
1 pull request merged.
-
Clarify & simplify w3c/beacon#19.
-
-
1 pull request received 1 new comment.
w3c/requestidlecallback
-
2 issues closed.
-
Why do we have two lists of callbacks? w3c/requestidlecallback#27.
-
Review TAG feedback w3c/requestidlecallback#31.
-
-
3 issues received 3 new comments.
-
Clarify meaning of "guarantee" for timeout callback w3c/requestidlecallback#33 (1 comment by @dentuzhik)
-
1 pull request merged.
-
Address some TAG review feedback. w3c/requestidlecallback#32.
-
-
1 pull request received 1 new comment.
w3c/user-timing
-
2 issues opened.
-
Enable association with input events. w3c/user-timing#15, by @tdresser.
-
Handling repeat metrics and measures + custom startTime? w3c/user-timing#14, by @igrigorik.
-
-
3 issues closed.
-
drop text about prefixes w3c/user-timing#7.
-
"from navigationStart to the current time" is incorrect w3c/user-timing#11.
-
Missing processing model w3c/user-timing#12.
-
-
3 issues received 4 new comments.
-
"from navigationStart to the current time" is incorrect w3c/user-timing#11 (2 comments by @igrigorik, @plehegar)
-
w3c/resource-timing
-
2 issues opened.
-
onresourcetimingbufferfull: EventHandler or GlobalEventHandler? w3c/resource-timing#49, by @AFBarstow.
-
Provide a way to get current buffer size? w3c/resource-timing#48, by @AFBarstow.
-
-
1 issue closed.
-
onresourcetimingbufferfull: EventHandler or GlobalEventHandler? w3c/resource-timing#49.
-
-
2 issues received 7 new comments.
-
onresourcetimingbufferfull: EventHandler or GlobalEventHandler? w3c/resource-timing#49 (5 comments by @AFBarstow, @plehegar)
-
w3c/performance-timeline
-
1 issue opened.
-
Mismatches between the shortNames in the w3c.json and the WebPerf repositories w3c/performance-timeline#51, by @siusin.
-
-
1 issue closed.
-
Mismatches between the shortNames in the w3c.json and the WebPerf repositories w3c/performance-timeline#51.
-
-
1 issue received 2 new comments.
-
Mismatches between the shortNames in the w3c.json and the WebPerf repositories w3c/performance-timeline#51 (2 comments by @plehegar)
-
TR publications
-
13 documents published.
-
Beacon published twice as a Working Draft. History of Beacon
-
Cooperative Scheduling of Background Tasks published as a Working Draft. History of Cooperative Scheduling of Background Tasks
-
Navigation Timing Level 2 published twice as a Working Draft. History of Navigation Timing Level 2
-
Performance Timeline Level 2 published twice as a Working Draft. History of Performance Timeline Level 2
-
Resource Timing published as a Working Draft. History of Resource Timing
-
Frame Timing published twice as a Working Draft. History of Frame Timing
-
High Resolution Time Level 2 published 3 times as a Working Draft. History of High Resolution Time Level 2
-
Participants
-
2 organizations joined.
-
Viacom inc. joined.
-
360 joined.
-
GitHub
w3c/beacon
-
6 issues opened.
-
Request coalescing as a platform primitive? w3c/beacon#20, by @igrigorik.
-
editorial comments w3c/beacon#18, by @plehegar.
-
privacy considerations w3c/beacon#17, by @plehegar.
-
security considerations and CORS w3c/beacon#16, by @plehegar.
-
Skip body processing w3c/beacon#15, by @plehegar.
-
Privacy section is misguided w3c/beacon#14, by @annevk.
-
-
1 issue closed.
-
Address Security/Privacy feedback from TPAC 2014 w3c/beacon#9.
-
-
3 issues received 19 new comments.
-
Request coalescing as a platform primitive? w3c/beacon#20 (12 comments by @annevk, @igrigorik, @sicking)
-
Privacy section is misguided w3c/beacon#14 (5 comments by @annevk, @dveditz, @igrigorik, @jakearchibald)
-
-
1 pull request opened.
-
Clarify & simplify w3c/beacon#19, by @igrigorik.
-
-
1 pull request received 12 new comments.
w3c/hr-time
-
5 issues opened.
-
Make translateTime work with Client objects w3c/hr-time#23, by @annevk.
-
Translating high resolution timestamps between globals w3c/hr-time#22, by @annevk.
-
Should time origin be defined in terms of a monotonic clock? w3c/hr-time#21, by @bzbarsky.
-
Privacy (PING) review w3c/hr-time#20, by @plehegar.
-
Need a changelist without translateTime so we can publish w3c/hr-time#16, by @toddreifsteck.
-
-
1 issue closed.
-
Need a changelist without translateTime so we can publish w3c/hr-time#16.
-
-
5 issues received 27 new comments.
-
Translating high resolution timestamps between globals w3c/hr-time#22 (16 comments by @annevk, @bzbarsky, @igrigorik, @sicking, @toddreifsteck)
-
Please add a giant red warning to http://www.w3.org/TR/hr-time/ w3c/hr-time#15 (3 comments by @igrigorik, @plehegar)
-
Should time origin be defined in terms of a monotonic clock? w3c/hr-time#21 (3 comments by @bzbarsky, @toddreifsteck)
-
Need a changelist without translateTime so we can publish w3c/hr-time#16 (3 comments by @igrigorik, @plehegar, @toddreifsteck)
-
-
3 pull requests opened.
-
Make the time origin definition more readable w3c/hr-time#19, by @plehegar.
-
Updated the status. translateTime is @ risk w3c/hr-time#18, by @plehegar.
-
Revert "Added a definition for 'current document'" w3c/hr-time#17, by @toddreifsteck.
-
-
4 pull requests merged.
-
Make the time origin definition more readable w3c/hr-time#19.
-
Updated the status. translateTime is @ risk w3c/hr-time#18.
-
Revert "Added a definition for 'current document'" w3c/hr-time#17.
-
Added a definition for 'current document' w3c/hr-time#14.
-
-
3 pull requests received 11 new comments.
-
Added a definition for 'current document' w3c/hr-time#14 (6 comments by @bzbarsky, @igrigorik, @plehegar, @toddreifsteck)
-
Make the time origin definition more readable w3c/hr-time#19 (3 comments by @bzbarsky, @igrigorik, @plehegar)
-
w3c/perf-timing-primer
-
3 pull requests opened.
-
A few more editorial suggestions w3c/perf-timing-primer#3, by @AFBarstow.
-
Editorial changes w3c/perf-timing-primer#2, by @AFBarstow.
-
Updated the draft according to the feedback from TPAC f2f meeting w3c/perf-timing-primer#1, by @siusin.
-
-
3 pull requests merged.
-
A few more editorial suggestions w3c/perf-timing-primer#3.
-
Editorial changes w3c/perf-timing-primer#2.
-
Updated the draft according to the feedback from TPAC f2f meeting w3c/perf-timing-primer#1.
-
-
2 pull requests received 9 new comments.
-
A few more editorial suggestions w3c/perf-timing-primer#3 (4 comments by @AFBarstow, @siusin, @yoavweiss)
w3c/requestidlecallback
-
2 issues opened.
-
Friendly callbacks w3c/requestidlecallback#34, by @Krinkle.
-
Clarify meaning of "guarantee" for timeout callback w3c/requestidlecallback#33, by @Krinkle.
-
-
3 issues closed.
-
Improve IDL markup w3c/requestidlecallback#24.
-
Are we sure we want integer handles? w3c/requestidlecallback#26.
-
Friendly callbacks w3c/requestidlecallback#34.
-
-
3 issues received 6 new comments.
-
1 pull request opened.
-
Clarify that an idle callback won't run in the same idle period as it's posted. w3c/requestidlecallback#35, by @rmcilroy.
-
-
1 pull request merged.
-
Clarify that an idle callback won't run in the same idle period as it's posted. w3c/requestidlecallback#35.
-
-
2 pull requests received 12 new comments.
-
Clarify that an idle callback won't run in the same idle period as it's posted. w3c/requestidlecallback#35 (4 comments by @bzbarsky, @igrigorik)
w3c/network-error-logging
-
4 issues opened.
-
Other 4xx server responses when submitting errors w3c/network-error-logging#60, by @bagder.
-
clarify the case with overlapping origins and subdomains w3c/network-error-logging#59, by @bagder.
-
Flag for 5xx reporting w3c/network-error-logging#58, by @netfeed.
-
broken link on is-origin-trustworthy in 2.2.1.1 w3c/network-error-logging#57, by @bagder.
-
-
2 issues received 5 new comments.
-
Other 4xx server responses when submitting errors w3c/network-error-logging#60 (4 comments by @bagder, @igrigorik)
-
clarify the case with overlapping origins and subdomains w3c/network-error-logging#59 (1 comment by @igrigorik)
-
w3c/navigation-timing
-
2 issues closed.
-
Drop prerenderSwitch from new draft? w3c/navigation-timing#38.
-
PerformanceTiming#dom* attributes are poorly defined w3c/navigation-timing#35.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Added the handling of the performance entry buffer w3c/navigation-timing#40.
-
-
1 pull request received 2 new comments.
-
Added the handling of the performance entry buffer w3c/navigation-timing#40 (2 comments by @toddreifsteck, @yoavweiss)
-
w3c/user-timing
-
1 pull request merged.
-
Rewrite and clean up w3c/user-timing#13.
-
-
1 pull request received 1 new comment.
w3c/resource-timing
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Added the handling of performance buffer w3c/resource-timing#47.
-
w3c/performance-timeline
-
1 pull request opened.
-
Observers observe user timing entries. w3c/performance-timeline#50, by @tdresser.
-
-
2 pull requests merged.
-
Added the performance entry buffer w3c/performance-timeline#49.
-
Observers observe user timing entries. w3c/performance-timeline#50.
-
-
2 pull requests received 6 new comments.
-
Added the performance entry buffer w3c/performance-timeline#49 (3 comments by @toddreifsteck, @yoavweiss)
-
Observers observe user timing entries. w3c/performance-timeline#50 (3 comments by @igrigorik, @tdresser)
-
TR publications
-
25 documents published.
-
Beacon published 3 times as a Working Draft. History of Beacon
-
Resource Timing published 9 times as a Working Draft. History of Resource Timing
-
High Resolution Time Level 2 published twice as a Working Draft. History of High Resolution Time Level 2
-
Navigation Timing Level 2 published twice as a Working Draft. History of Navigation Timing Level 2
-
Performance Timeline Level 2 published 3 times as a Working Draft. History of Performance Timeline Level 2
-
Network Error Logging published as a Working Draft. History of Network Error Logging
-
Frame Timing published twice as a Working Draft. History of Frame Timing
-
Preload published as a Working Draft. History of Preload
-
Resource Hints published twice as a Working Draft. History of Resource Hints
-
Participants
-
1 participant joined.
-
Philippe Le Hegaret (W3C) joined.
-
GitHub
w3c/network-error-logging
-
1 issue opened.
-
missing reference and broken links in 2.4 w3c/network-error-logging#56, by @bagder.
-
-
1 pull request received 4 new comments.
w3c/requestidlecallback
-
6 issues opened.
-
Review TAG feedback w3c/requestidlecallback#31, by @igrigorik.
-
It's odd to half-define inter-document callback ordering, but not fully define it w3c/requestidlecallback#29, by @bzbarsky.
-
The restriction on when a new idle period can start is rather odd. w3c/requestidlecallback#28, by @bzbarsky.
-
Why do we have two lists of callbacks? w3c/requestidlecallback#27, by @bzbarsky.
-
Are we sure we want integer handles? w3c/requestidlecallback#26, by @bzbarsky.
-
"the Window object's active document" makes no sense w3c/requestidlecallback#25, by @bzbarsky.
-
-
5 issues received 13 new comments.
-
Why do we have two lists of callbacks? w3c/requestidlecallback#27 (6 comments by @bzbarsky, @igrigorik, @rmcilroy)
-
It's odd to half-define inter-document callback ordering, but not fully define it w3c/requestidlecallback#29 (2 comments by @bzbarsky, @rmcilroy)
-
Are we sure we want integer handles? w3c/requestidlecallback#26 (2 comments by @igrigorik, @rmcilroy)
-
The restriction on when a new idle period can start is rather odd. w3c/requestidlecallback#28 (2 comments by @bzbarsky, @rmcilroy)
-
-
2 pull requests opened.
-
Address some TAG review feedback. w3c/requestidlecallback#32, by @rmcilroy.
-
Change IDL to be ReSpec compatible w3c/requestidlecallback#30, by @rmcilroy.
-
-
1 pull request closed.
-
Change IDL to be ReSpec compatible w3c/requestidlecallback#30.
-
-
2 pull requests received 12 new comments.
-
Change IDL to be ReSpec compatible w3c/requestidlecallback#30 (9 comments by @igrigorik, @plehegar, @rmcilroy, @toddreifsteck)
-
w3c/hr-time
-
1 issue opened.
-
Please add a giant red warning to http://www.w3.org/TR/hr-time/ w3c/hr-time#15, by @domenic.
-
-
1 issue received 6 new comments.
-
Please add a giant red warning to http://www.w3.org/TR/hr-time/ w3c/hr-time#15 (6 comments by @domenic, @igrigorik, @plehegar, @sideshowbarker)
-
-
1 pull request received 3 new comments.
-
Added a definition for 'current document' w3c/hr-time#14 (3 comments by @bzbarsky, @plehegar, @toddreifsteck)
-
w3c/navigation-timing
-
2 issues opened.
-
Contribute tests for navigation timing w3c/navigation-timing#39, by @toddreifsteck.
-
Drop prerenderSwitch from new draft? w3c/navigation-timing#38, by @igrigorik.
-
-
1 issue received 8 new comments.
-
Drop prerenderSwitch from new draft? w3c/navigation-timing#38 (8 comments by @igrigorik, @plehegar, @toddreifsteck, @yoavweiss)
-
-
1 pull request opened.
-
Added the handling of the performance entry buffer w3c/navigation-timing#40, by @plehegar.
-
w3c/performance-timeline
-
2 pull requests opened.
-
Added the performance entry buffer w3c/performance-timeline#49, by @plehegar.
-
Revamped the IDL markup and anchors w3c/performance-timeline#48, by @plehegar.
-
-
1 pull request merged.
-
Revamped the IDL markup and anchors w3c/performance-timeline#48.
-
-
2 pull requests received 3 new comments.
w3c/resource-timing
-
5 issues opened.
-
Contribute tests for resource timing w3c/resource-timing#46, by @toddreifsteck.
-
Timing-allow-check not well-defined for same-origin resources w3c/resource-timing#43, by @yoavweiss.
-
Distinguish "Not-Allowed" from zero value entries w3c/resource-timing#42, by @yoavweiss.
-
Clarify what transferSize, encodedBodySize should return in various conditions w3c/resource-timing#40, by @valenting.
-
Define Resource Timing in terms of Fetch w3c/resource-timing#39, by @igrigorik.
-
-
2 issues closed.
-
Timing-allow-check not well-defined for same-origin resources w3c/resource-timing#43.
-
Clarify what transferSize, encodedBodySize should return in various conditions w3c/resource-timing#40.
-
-
2 issues received 5 new comments.
-
Clarify what transferSize, encodedBodySize should return in various conditions w3c/resource-timing#40 (4 comments by @igrigorik, @valenting)
-
-
4 pull requests opened.
-
Added the handling of performance buffer w3c/resource-timing#47, by @plehegar.
-
Fix up a link towards the Fetch spec w3c/resource-timing#45, by @yoavweiss.
-
timing-allow-check handling of same-origin resources w3c/resource-timing#44, by @yoavweiss.
-
clarify {transfer,encodedBody,decodedBody}size w3c/resource-timing#41, by @igrigorik.
-
-
4 pull requests merged.
-
timing-allow-check handling of same-origin resources w3c/resource-timing#44.
-
Fix up a link towards the Fetch spec w3c/resource-timing#45.
-
clarify {transfer,encodedBody,decodedBody}size w3c/resource-timing#41.
-
Terminology w3c/resource-timing#38.
-
-
1 pull request closed.
-
improve initiatorType w3c/resource-timing#36.
-
-
6 pull requests received 16 new comments.
-
clarify {transfer,encodedBody,decodedBody}size w3c/resource-timing#41 (11 comments by @igrigorik, @valenting, @yoavweiss)
-
timing-allow-check handling of same-origin resources w3c/resource-timing#44 (1 comment by @igrigorik)
-
w3c/beacon
-
1 issue opened.
-
Give guidelines on unload/visibilitystate/pagehide w3c/beacon#13, by @plehegar.
-
-
2 issues reopened.
-
Address Security/Privacy feedback from TPAC 2014 w3c/beacon#9, by @toddreifsteck.
-
Clarify interaction with CORS (preflight requests) w3c/beacon#10, by @igrigorik.
-
-
2 issues received 7 new comments.
-
Clarify interaction with CORS (preflight requests) w3c/beacon#10 (4 comments by @annevk, @igrigorik, @toddreifsteck)
-
w3c/server-timing
-
1 issue opened.
-
interface ServerEntry should be renamed to PerformanServerTiming w3c/server-timing#3, by @plehegar.
-
w3c/user-timing
-
1 pull request received 9 new comments.
-
Rewrite and clean up w3c/user-timing#13 (9 comments by @eliperelman, @igrigorik, @plehegar, @toddreifsteck)
-
TR publications
-
45 documents published.
-
Resource Hints published 5 times as a Working Draft. History of Resource Hints
-
Beacon published 3 times as a Working Draft. History of Beacon
-
Cooperative Scheduling of Background Tasks published 4 times as a Working Draft. History of Cooperative Scheduling of Background Tasks
-
Frame Timing published 7 times as a Working Draft. History of Frame Timing
-
Network Error Logging published twice as a Working Draft. History of Network Error Logging
-
High Resolution Time Level 2 published 3 times as a Working Draft. History of High Resolution Time Level 2
-
Resource Timing published 7 times as a Working Draft. History of Resource Timing
-
Navigation Timing Level 2 published 6 times as a Working Draft. History of Navigation Timing Level 2
-
Performance Timeline Level 2 published 5 times as a Working Draft. History of Performance Timeline Level 2
-
Preload published as a Working Draft. History of Preload
-
Cooperative Scheduling of Background Tasks published as a First Public Working Draft. History of Cooperative Scheduling of Background Tasks
-
GitHub
w3c/user-timing
-
1 issue opened.
-
Missing processing model w3c/user-timing#12, by @plehegar.
-
-
3 issues received 4 new comments.
-
1 pull request opened.
-
Rewrite and clean up w3c/user-timing#13, by @plehegar.
-
-
1 pull request received 10 new comments.
w3c/hr-time
-
1 pull request opened.
-
Added a definition for 'current document' w3c/hr-time#14, by @plehegar.
-
-
1 pull request received 5 new comments.
-
Added a definition for 'current document' w3c/hr-time#14 (5 comments by @annevk, @bzbarsky, @igrigorik, @plehegar)
-
w3c/navigation-timing
-
1 issue opened.
-
NT should handle multi-request fetches w3c/navigation-timing#37, by @plehegar.
-
-
3 issues closed.
-
Connection between Navigation Timing 2 and Performance Timeline is underdefined w3c/navigation-timing#1.
-
Use Timing-Allow-Origin to determine same-origin on redirects w3c/navigation-timing#20.
-
Consider refactoring navigation-timing to extend resource-timing w3c/navigation-timing#11.
-
-
1 issue reopened.
-
PerformanceTiming#dom* attributes are poorly defined w3c/navigation-timing#35, by @plehegar.
-
-
4 issues received 10 new comments.
-
PerformanceTiming#dom* attributes are poorly defined w3c/navigation-timing#35 (4 comments by @igrigorik, @plehegar)
-
Connection between Navigation Timing 2 and Performance Timeline is underdefined w3c/navigation-timing#1 (2 comments by @igrigorik, @plehegar)
-
Use Timing-Allow-Origin to determine same-origin on redirects w3c/navigation-timing#20 (2 comments by @igrigorik, @plehegar)
-
Consider refactoring navigation-timing to extend resource-timing w3c/navigation-timing#11 (2 comments by @igrigorik, @plehegar)
-
-
1 pull request opened.
-
Resource timing as base w3c/navigation-timing#36, by @plehegar.
-
-
1 pull request merged.
-
Resource timing as base w3c/navigation-timing#36.
-
-
1 pull request received 23 new comments.
-
Resource timing as base w3c/navigation-timing#36 (23 comments by @igrigorik, @plehegar, @toddreifsteck)
-
w3c/requestidlecallback
-
4 issues opened.
-
Improve IDL markup w3c/requestidlecallback#24, by @igrigorik.
-
Future-proof the rIC API and make it extensible w3c/requestidlecallback#21, by @igrigorik.
-
Clamp requestIdleCallback deadline w3c/requestidlecallback#20, by @esprehn.
-
should requestIdleCallback return unsigned long? w3c/requestidlecallback#17, by @tetsuharuohzeki.
-
-
4 issues closed.
-
Clamp requestIdleCallback deadline w3c/requestidlecallback#20.
-
Future-proof the rIC API and make it extensible w3c/requestidlecallback#21.
-
Do we need to clarify that microtasks will execute within this period? w3c/requestidlecallback#13.
-
should requestIdleCallback return unsigned long? w3c/requestidlecallback#17.
-
-
4 issues received 21 new comments.
-
Future-proof the rIC API and make it extensible w3c/requestidlecallback#21 (8 comments by @bzbarsky, @eliperelman, @igrigorik, @rmcilroy, @toddreifsteck)
-
Clamp requestIdleCallback deadline w3c/requestidlecallback#20 (7 comments by @esprehn, @igrigorik, @rmcilroy)
-
should requestIdleCallback return unsigned long? w3c/requestidlecallback#17 (5 comments by @igrigorik, @rmcilroy, @tetsuharuohzeki)
-
Do we need to clarify that microtasks will execute within this period? w3c/requestidlecallback#13 (1 comment by @rmcilroy)
-
-
7 pull requests opened.
-
Clamp timeRemaining() to 5 microsecond resolution. w3c/requestidlecallback#23, by @rmcilroy.
-
Future-proof the rIC API and make it extensible. w3c/requestidlecallback#22, by @rmcilroy.
-
Change requestIdleCallback type to unsigned long. w3c/requestidlecallback#19, by @tetsuharuohzeki.
-
Fix errata w3c/requestidlecallback#18, by @simonhong.
-
Add tests for requestIdleCallback. w3c/requestidlecallback#16, by @rmcilroy.
-
Clarify that additional microtasks could be triggered from an idle callback w3c/requestidlecallback#15, by @rmcilroy.
-
Change timeRemaining to a function rather than an attribute. w3c/requestidlecallback#14, by @rmcilroy.
-
-
6 pull requests merged.
-
Clamp timeRemaining() to 5 microsecond resolution. w3c/requestidlecallback#23.
-
Future-proof the rIC API and make it extensible. w3c/requestidlecallback#22.
-
Change requestIdleCallback type to unsigned long. w3c/requestidlecallback#19.
-
Fix errata w3c/requestidlecallback#18.
-
Clarify that additional microtasks could be triggered from an idle callback w3c/requestidlecallback#15.
-
Change timeRemaining to a function rather than an attribute. w3c/requestidlecallback#14.
-
-
1 pull request closed.
-
Add tests for requestIdleCallback. w3c/requestidlecallback#16.
-
-
8 pull requests received 24 new comments.
-
Future-proof the rIC API and make it extensible. w3c/requestidlecallback#22 (8 comments by @bzbarsky, @igrigorik, @rmcilroy, @toddreifsteck)
-
Add tests for requestIdleCallback. w3c/requestidlecallback#16 (4 comments by @igrigorik, @plehegar, @rmcilroy)
-
Change requestIdleCallback type to unsigned long. w3c/requestidlecallback#19 (3 comments by @rmcilroy, @tetsuharuohzeki)
-
Change timeRemaining to a function rather than an attribute. w3c/requestidlecallback#14 (3 comments by @igrigorik, @rmcilroy)
-
Collapse IdleDeadline's deadline and isExceeded into IdleDeadline.timeRemaining() w3c/requestidlecallback#12 (2 comments by @igrigorik, @rmcilroy)
-
Clarify that additional microtasks could be triggered from an idle callback w3c/requestidlecallback#15 (2 comments by @igrigorik)
-
Clamp timeRemaining() to 5 microsecond resolution. w3c/requestidlecallback#23 (1 comment by @igrigorik)
-
w3c/resource-timing
-
3 issues closed.
-
Define processing model for insertion of entries into Performance Timeline w3c/resource-timing#31.
-
What value should secureConnectionStart have when using preexisting connection? w3c/resource-timing#17.
-
requestStart definition differ with navtimg w3c/resource-timing#25.
-
-
5 issues received 9 new comments.
-
Define processing model for insertion of entries into Performance Timeline w3c/resource-timing#31 (2 comments by @igrigorik, @plehegar)
-
What value should secureConnectionStart have when using preexisting connection? w3c/resource-timing#17 (2 comments by @igrigorik, @toddreifsteck)
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (1 comment by @toddreifsteck)
-
6 pull requests opened.
-
Terminology w3c/resource-timing#38, by @plehegar.
-
Queue the object for performance observers w3c/resource-timing#37, by @plehegar.
-
improve initiatorType w3c/resource-timing#36, by @igrigorik.
-
Added a note on requestEnd w3c/resource-timing#35, by @plehegar.
-
secureConnectionStart: Remove optional and handle pre-existing connec… w3c/resource-timing#34, by @toddreifsteck.
-
Size attributes: switch to unsigned long, and clarify TAO restrictions w3c/resource-timing#33, by @igrigorik.
-
-
5 pull requests merged.
-
Queue the object for performance observers w3c/resource-timing#37.
-
Added a note on requestEnd w3c/resource-timing#35.
-
Size attributes: switch to unsigned long, and clarify TAO restrictions w3c/resource-timing#33.
-
secureConnectionStart: Remove optional and handle pre-existing connec… w3c/resource-timing#34.
-
set responseEnd if connection is terminated w3c/resource-timing#32.
-
-
6 pull requests received 23 new comments.
-
Size attributes: switch to unsigned long, and clarify TAO restrictions w3c/resource-timing#33 (4 comments by @bzbarsky, @igrigorik, @toddreifsteck)
-
secureConnectionStart: Remove optional and handle pre-existing connec… w3c/resource-timing#34 (2 comments by @igrigorik, @toddreifsteck)
w3c/beacon
-
1 issue opened.
-
Fix broken links w3c/beacon#12, by @igrigorik.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
call Fetch to extract byte stream and content type w3c/beacon#11.
-
-
1 pull request received 7 new comments.
-
call Fetch to extract byte stream and content type w3c/beacon#11 (7 comments by @annevk, @igrigorik, @toddreifsteck)
-
w3c/performance-timeline
-
1 issue closed.
-
Clarify PerformanceObserver registration language in the spec w3c/performance-timeline#44.
-
-
1 issue received 15 new comments.
-
Clarify PerformanceObserver registration language in the spec w3c/performance-timeline#44 (15 comments by @annevk, @bzbarsky, @igrigorik)
-
-
1 pull request opened.
-
Clarify perf observer registration process w3c/performance-timeline#47, by @igrigorik.
-
-
1 pull request merged.
-
Clarify perf observer registration process w3c/performance-timeline#47.
-
-
1 pull request received 1 new comment.
Participants
-
1 participant joined.
-
Xiaoqian Wu (W3C) joined.
-
-
3 organizations joined.
-
Dynatrace LLC joined.
-
Akamai Technologies joined.
-
Mozilla Foundation joined.
-
GitHub
w3c/performance-timeline
-
2 issues opened.
-
Clarify when observe method is called more than once w3c/performance-timeline#45, by @hiikezoe.
-
Clarify PerformanceObserver registration language in the spec w3c/performance-timeline#44, by @igrigorik.
-
-
6 issues closed.
-
getEntries* are depending on the scope w3c/performance-timeline#39.
-
Clarify when observe method is called more than once w3c/performance-timeline#45.
-
When are new entries delivered to observer? w3c/performance-timeline#13.
-
createPerformanceObserver should be createObserver w3c/performance-timeline#38.
-
window.performance.createObserver feedback w3c/performance-timeline#40.
-
Allow creation of PerformanceObserver with flag to "emit timeline"? w3c/performance-timeline#41.
-
-
6 issues received 8 new comments.
-
Clarify when observe method is called more than once w3c/performance-timeline#45 (3 comments by @hiikezoe, @igrigorik, @mpb)
-
Clarify PerformanceObserver registration language in the spec w3c/performance-timeline#44 (1 comment by @bzbarsky)
-
createPerformanceObserver should be createObserver w3c/performance-timeline#38 (1 comment by @igrigorik)
-
Allow creation of PerformanceObserver with flag to "emit timeline"? w3c/performance-timeline#41 (1 comment by @toddreifsteck)
-
-
1 pull request opened.
-
Processing algorithm for PerformanceObserver w3c/performance-timeline#46, by @igrigorik.
-
-
2 pull requests merged.
-
Processing algorithm for PerformanceObserver w3c/performance-timeline#46.
-
Revert to using a constructor for PerformanceObserver. w3c/performance-timeline#43.
-
-
1 pull request closed.
-
(WIP) Observer-based processing w3c/performance-timeline#12.
-
-
3 pull requests received 22 new comments.
-
Processing algorithm for PerformanceObserver w3c/performance-timeline#46 (18 comments by @eliperelman, @esprehn, @hiikezoe, @igrigorik, @mpb, @natduca, @toddreifsteck)
-
Revert to using a constructor for PerformanceObserver. w3c/performance-timeline#43 (3 comments by @igrigorik, @mpb, @toddreifsteck)
-
w3c/requestidlecallback
-
2 issues opened.
-
Do we need to clarify that microtasks will execute within this period? w3c/requestidlecallback#13, by @toddreifsteck.
-
Collapse deadline and isExeeded into single function? w3c/requestidlecallback#11, by @igrigorik.
-
-
2 issues closed.
-
Collapse deadline and isExeeded into single function? w3c/requestidlecallback#11.
-
Promise based: idle() w3c/requestidlecallback#1.
-
-
2 issues received 11 new comments.
-
Collapse deadline and isExeeded into single function? w3c/requestidlecallback#11 (7 comments by @igrigorik, @ojanvafai, @rmcilroy)
-
Do we need to clarify that microtasks will execute within this period? w3c/requestidlecallback#13 (4 comments by @igrigorik, @rmcilroy, @toddreifsteck)
-
-
1 pull request opened.
-
Collapse IdleDeadline's deadline and isExceeded into IdleDeadline.timeRemaining() w3c/requestidlecallback#12, by @rmcilroy.
-
-
1 pull request merged.
-
Collapse IdleDeadline's deadline and isExceeded into IdleDeadline.timeRemaining() w3c/requestidlecallback#12.
-
-
2 pull requests received 16 new comments.
-
Collapse IdleDeadline's deadline and isExceeded into IdleDeadline.timeRemaining() w3c/requestidlecallback#12 (15 comments by @eliperelman, @igrigorik, @joshduck, @rmcilroy, @toddreifsteck)
-
w3c/navigation-timing
-
1 issue opened.
-
PerformanceTiming#dom* attributes are poorly defined w3c/navigation-timing#35, by @igrigorik.
-
-
1 issue closed.
-
window.performance.timing mention w3c/navigation-timing#15.
-
-
3 issues received 7 new comments.
-
Use Timing-Allow-Origin to determine same-origin on redirects w3c/navigation-timing#20 (3 comments by @igrigorik, @toddreifsteck)
-
PerformanceTiming#dom* attributes are poorly defined w3c/navigation-timing#35 (2 comments by @igrigorik, @Ms2ger)
-
window.performance.timing mention w3c/navigation-timing#15 (2 comments by @igrigorik, @toddreifsteck)
-
-
1 pull request merged.
-
performance.timing is deprecated w3c/navigation-timing#32.
-
w3c/resource-timing
-
1 issue opened.
-
Define processing model for insertion of entries into Performance Timeline w3c/resource-timing#31, by @toddreifsteck.
-
-
3 issues closed.
-
drop text about prefixes w3c/resource-timing#26.
-
PerformanceObserver when ResourceTiming array is full w3c/resource-timing#28.
-
Cached redirects + History traversal reveal cross-origin URLs w3c/resource-timing#29.
-
-
5 issues received 9 new comments.
-
requestStart definition differ with navtimg w3c/resource-timing#25 (3 comments by @igrigorik, @toddreifsteck)
-
Cached redirects + History traversal reveal cross-origin URLs w3c/resource-timing#29 (3 comments by @cgvwzq, @igrigorik)
-
What value should secureConnectionStart have when using preexisting connection? w3c/resource-timing#17 (1 comment by @igrigorik)
-
PerformanceObserver when ResourceTiming array is full w3c/resource-timing#28 (1 comment by @igrigorik)
-
-
1 pull request opened.
-
set responseEnd if connection is terminated w3c/resource-timing#32, by @igrigorik.
-
w3c/beacon
-
1 issue closed.
-
Beacon-Age registration w3c/beacon#5.
-
-
2 issues received 4 new comments.
-
Clarify interaction with CORS (preflight requests) w3c/beacon#10 (3 comments by @annevk, @igrigorik, @toddreifsteck)
-
-
1 pull request opened.
-
call Fetch to extract byte stream and content type w3c/beacon#11, by @igrigorik.
-
w3c/network-error-logging
-
1 issue received 4 new comments.
-
Interaction with ServiceWorker w3c/network-error-logging#54 (4 comments by @igrigorik, @jakearchibald, @jungkees)
-
TR publications
-
16 documents published.
-
Preload published twice as a Working Draft. History of Preload
-
High Resolution Time Level 2 published 4 times as a Working Draft. History of High Resolution Time Level 2
-
Navigation Timing Level 2 published 3 times as a Working Draft. History of Navigation Timing Level 2
-
Resource Timing published as a Working Draft. History of Resource Timing
-
Frame Timing published as a Working Draft. History of Frame Timing
-
Performance Timeline Level 2 published as a Working Draft. History of Performance Timeline Level 2
-
Resource Hints published as a Working Draft. History of Resource Hints
-
Server Timing published as a Working Draft. History of Server Timing
-
Preload published as a First Public Working Draft. History of Preload
-
Performance Timeline Level 2 published as a First Public Working Draft. History of Performance Timeline Level 2
-
Participants
-
1 participant joined.
-
Michael[tm] Smith (sideshowbarker) (W3C) joined.
-
-
8 organizations joined.
-
Vodafone joined.
-
Apple Inc. joined.
-
Intel Corporation joined.
-
SOASTA joined.
-
Mitsubishi Electric Corporation joined.
-
Microsoft Corporation joined.
-
Academia Animartec S.L. joined.
-
Google LLC joined.
-
GitHub
w3c/requestidlecallback
-
5 issues opened.
-
Processing model will not make progress w3c/requestidlecallback#7, by @lawnsea.
-
`isExceeded` specified backward? w3c/requestidlecallback#6, by @lawnsea.
-
Add an optional parameter which guarantees callback is executed w3c/requestidlecallback#3, by @rmcilroy.
-
Enable use of generator functions with yield in requestIdleCallback w3c/requestidlecallback#2, by @rmcilroy.
-
Promise based: idle() w3c/requestidlecallback#1, by @plehegar.
-
-
4 issues closed.
-
`isExceeded` specified backward? w3c/requestidlecallback#6.
-
Enable use of generator functions with yield in requestIdleCallback w3c/requestidlecallback#2.
-
Processing model will not make progress w3c/requestidlecallback#7.
-
Add an optional parameter which guarantees callback is executed w3c/requestidlecallback#3.
-
-
5 issues received 23 new comments.
-
Promise based: idle() w3c/requestidlecallback#1 (11 comments by @balasanjay, @domenic, @igrigorik, @rmcilroy)
-
Enable use of generator functions with yield in requestIdleCallback w3c/requestidlecallback#2 (5 comments by @domenic, @igrigorik, @jakearchibald, @rmcilroy)
-
Add an optional parameter which guarantees callback is executed w3c/requestidlecallback#3 (5 comments by @igrigorik, @lawnsea, @rmcilroy, @smaug----)
-
-
5 pull requests opened.
-
Add Lon Ingram to Acknowledgments w3c/requestidlecallback#10, by @rmcilroy.
-
Fix isExceeded to check deadline correctly. w3c/requestidlecallback#9, by @rmcilroy.
-
Allow processing model to make progress w3c/requestidlecallback#8, by @lawnsea.
-
Add missing word w3c/requestidlecallback#5, by @lawnsea.
-
Fix pluralization typo w3c/requestidlecallback#4, by @lawnsea.
-
-
5 pull requests merged.
-
Add Lon Ingram to Acknowledgments w3c/requestidlecallback#10.
-
Fix isExceeded to check deadline correctly. w3c/requestidlecallback#9.
-
Allow processing model to make progress w3c/requestidlecallback#8.
-
Add missing word w3c/requestidlecallback#5.
-
Fix pluralization typo w3c/requestidlecallback#4.
-
-
4 pull requests received 5 new comments.
-
Allow processing model to make progress w3c/requestidlecallback#8 (2 comments by @lawnsea, @rmcilroy)
-
w3c/performance-timeline
-
10 issues opened.
-
Performance should implement EventTarget w3c/performance-timeline#42, by @nicjansma.
-
Allow creation of PerformanceObserver with flag to "emit timeline"? w3c/performance-timeline#41, by @toddreifsteck.
-
window.performance.createObserver feedback w3c/performance-timeline#40, by @igrigorik.
-
getEntries* are depending on the scope w3c/performance-timeline#39, by @plehegar.
-
createPerformanceObserver should be createObserver w3c/performance-timeline#38, by @esprehn.
-
Add serializer to PerformanceEntry w3c/performance-timeline#36, by @toddreifsteck.
-
Performance should be a partial interface? w3c/performance-timeline#32, by @foolip.
-
PerformanceEntry.startTime/duration should be DOMHighResTimeStamp w3c/performance-timeline#31, by @foolip.
-
Behavior when invalid attribute is specifed for getEntries filter w3c/performance-timeline#30, by @hiikezoe.
-
s/eventTypes/typeFilter/ in EXAMPLE 2 w3c/performance-timeline#28, by @hiikezoe.
-
-
8 issues closed.
-
Performance should implement EventTarget w3c/performance-timeline#42.
-
Behavior when invalid attribute is specifed for getEntries filter w3c/performance-timeline#30.
-
Add serializer to PerformanceEntry w3c/performance-timeline#36.
-
drop text about prefixes w3c/performance-timeline#27.
-
startTime is relative to time origin of PerformanceEntry object's global w3c/performance-timeline#25.
-
PerformanceEntry.startTime/duration should be DOMHighResTimeStamp w3c/performance-timeline#31.
-
Performance should be a partial interface? w3c/performance-timeline#32.
-
s/eventTypes/typeFilter/ in EXAMPLE 2 w3c/performance-timeline#28.
-
-
11 issues received 45 new comments.
-
Performance should be a partial interface? w3c/performance-timeline#32 (12 comments by @foolip, @igrigorik)
-
window.performance.createObserver feedback w3c/performance-timeline#40 (9 comments by @annevk, @bzbarsky, @igrigorik)
-
Allow creation of PerformanceObserver with flag to "emit timeline"? w3c/performance-timeline#41 (7 comments by @eliperelman, @igrigorik, @natduca, @nicjansma, @toddreifsteck)
-
PerformanceEntry.startTime/duration should be DOMHighResTimeStamp w3c/performance-timeline#31 (4 comments by @eliperelman, @igrigorik, @plehegar, @toddreifsteck)
-
getEntries* are depending on the scope w3c/performance-timeline#39 (3 comments by @bzbarsky, @igrigorik)
-
Behavior when invalid attribute is specifed for getEntries filter w3c/performance-timeline#30 (3 comments by @bzbarsky, @igrigorik)
-
Performance should implement EventTarget w3c/performance-timeline#42 (2 comments by @nicjansma, @plehegar)
-
startTime is relative to time origin of PerformanceEntry object's global w3c/performance-timeline#25 (2 comments by @igrigorik, @plehegar)
-
-
6 pull requests opened.
-
Revert to using a constructor for PerformanceObserver. w3c/performance-timeline#43, by @mpb.
-
entryType enum + consistent use w3c/performance-timeline#37, by @igrigorik.
-
Change PerformanceObserver from using a constructor to using Performance interface. w3c/performance-timeline#35, by @mpb.
-
Vendor prefixes w3c/performance-timeline#33, by @plehegar.
-
PerformanceObserver.observe() needs 'target' w3c/performance-timeline#29, by @mpb.
-
-
5 pull requests merged.
-
entryType enum + consistent use w3c/performance-timeline#37.
-
Change PerformanceObserver from using a constructor to using Performance interface. w3c/performance-timeline#35.
-
Vendor prefixes w3c/performance-timeline#33.
-
Fixes #31 w3c/performance-timeline#34.
-
Now uses HR-TIME as the basis w3c/performance-timeline#26.
-
-
1 pull request closed.
-
PerformanceObserver.observe() needs 'target' w3c/performance-timeline#29.
-
-
7 pull requests received 87 new comments.
-
PerformanceObserver.observe() needs 'target' w3c/performance-timeline#29 (39 comments by @bzbarsky, @domenic, @eliperelman, @esprehn, @hiikezoe, @igrigorik, @mpb)
-
entryType enum + consistent use w3c/performance-timeline#37 (35 comments by @bzbarsky, @hiikezoe, @igrigorik, @mpb, @toddreifsteck)
-
Revert to using a constructor for PerformanceObserver. w3c/performance-timeline#43 (5 comments by @annevk, @igrigorik, @mpb)
-
Change PerformanceObserver from using a constructor to using Performance interface. w3c/performance-timeline#35 (2 comments by @eliperelman, @igrigorik)
-
w3c/user-timing
-
2 issues opened.
-
"from navigationStart to the current time" is incorrect w3c/user-timing#11, by @plehegar.
-
Add Exposed=Worker,Window to Extension to Performance interface w3c/user-timing#10, by @toddreifsteck.
-
-
4 issues closed.
-
Add Exposed=Worker,Window to Extension to Performance interface w3c/user-timing#10.
-
Better Recommended Mark Names? w3c/user-timing#5.
-
Custom UserTiming Payloads w3c/user-timing#3.
-
Platform indicators w3c/user-timing#6.
-
-
6 issues received 22 new comments.
-
SYNTAX_ERR exception for markName argument w3c/user-timing#1 (6 comments by @igrigorik, @marcoscaceres, @plehegar)
-
"from navigationStart to the current time" is incorrect w3c/user-timing#11 (3 comments by @igrigorik, @plehegar)
-
Add Exposed=Worker,Window to Extension to Performance interface w3c/user-timing#10 (2 comments by @igrigorik, @toddreifsteck)
-
-
2 pull requests opened.
-
Drop recommended marks w3c/user-timing#9, by @plehegar.
-
Expose interfaces to workers w3c/user-timing#8, by @plehegar.
-
-
2 pull requests merged.
-
Drop recommended marks w3c/user-timing#9.
-
Expose interfaces to workers w3c/user-timing#8.
-
-
1 pull request received 2 new comments.
w3c/resource-timing
-
3 issues opened.
-
Cached redirects + History traversal reveal cross-origin URLs w3c/resource-timing#29, by @igrigorik.
-
PerformanceObserver when ResourceTiming array is full w3c/resource-timing#28, by @nicjansma.
-
Same-origin policy & observing no-cors fetches w3c/resource-timing#27, by @igrigorik.
-
-
2 issues closed.
-
Same-origin policy & observing no-cors fetches w3c/resource-timing#27.
-
Clarify "zero time" in Workers w3c/resource-timing#23.
-
-
5 issues received 19 new comments.
-
Same-origin policy & observing no-cors fetches w3c/resource-timing#27 (15 comments by @annevk, @davidben, @igrigorik, @toddreifsteck)
-
Cached redirects + History traversal reveal cross-origin URLs w3c/resource-timing#29 (1 comment by @dveditz)
-
PerformanceObserver when ResourceTiming array is full w3c/resource-timing#28 (1 comment by @igrigorik)
-
-
1 pull request opened.
-
Exclude no-cors cross-origin stylesheet subresources w3c/resource-timing#30, by @igrigorik.
-
-
1 pull request merged.
-
Exclude no-cors cross-origin stylesheet subresources w3c/resource-timing#30.
-
-
1 pull request received 3 new comments.
-
Exclude no-cors cross-origin stylesheet subresources w3c/resource-timing#30 (3 comments by @igrigorik, @plehegar)
-
w3c/network-error-logging
-
1 issue closed.
-
At least one examples at the start of doc w3c/network-error-logging#41.
-
-
3 issues received 14 new comments.
-
Interaction with ServiceWorker w3c/network-error-logging#54 (12 comments by @annevk, @igrigorik, @slightlyoff)
-
-
1 pull request opened.
-
Define NEL in terms of Fetch w3c/network-error-logging#55, by @igrigorik.
-
w3c/navigation-timing
-
7 issues opened.
-
PerformanceNavigation.type and redirectCount should be unsigned short w3c/navigation-timing#29, by @foolip.
-
PerformanceNavigation.TYPE_RESERVED should be 255 (or be removed) w3c/navigation-timing#28, by @foolip.
-
Define serializer in spec to ensure JSON.stringify performs well w3c/navigation-timing#23, by @toddreifsteck.
-
Is the merge of PerformanceTiming and PerformanceNavigation into PerformanceNavigationTiming web compatible? w3c/navigation-timing#22, by @foolip.
-
First paint time w3c/navigation-timing#21, by @Diokuz.
-
Use Timing-Allow-Origin to determine same-origin on redirects w3c/navigation-timing#20, by @bmaurer.
-
click/touch events start time. w3c/navigation-timing#19, by @furoshiki.
-
-
7 issues closed.
-
PerformanceNavigation.type and redirectCount should be unsigned short w3c/navigation-timing#29.
-
PerformanceNavigation.TYPE_RESERVED should be 255 (or be removed) w3c/navigation-timing#28.
-
drop text about prefixes w3c/navigation-timing#18.
-
Define serializer in spec to ensure JSON.stringify performs well w3c/navigation-timing#23.
-
click/touch events start time. w3c/navigation-timing#19.
-
First paint time w3c/navigation-timing#21.
-
-
1 issue reopened.
-
Use Timing-Allow-Origin to determine same-origin on redirects w3c/navigation-timing#20, by @toddreifsteck.
-
-
8 issues received 46 new comments.
-
Is the merge of PerformanceTiming and PerformanceNavigation into PerformanceNavigationTiming web compatible? w3c/navigation-timing#22 (23 comments by @bzbarsky, @foolip, @igrigorik, @plehegar, @toddreifsteck)
-
PerformanceNavigation.TYPE_RESERVED should be 255 (or be removed) w3c/navigation-timing#28 (5 comments by @foolip, @igrigorik, @plehegar)
-
Use Timing-Allow-Origin to determine same-origin on redirects w3c/navigation-timing#20 (5 comments by @igrigorik, @toddreifsteck)
-
click/touch events start time. w3c/navigation-timing#19 (4 comments by @furoshiki, @igrigorik, @plehegar, @toddreifsteck)
-
PerformanceNavigation.type and redirectCount should be unsigned short w3c/navigation-timing#29 (2 comments by @igrigorik, @plehegar)
-
Consider refactoring navigation-timing to extend resource-timing w3c/navigation-timing#11 (1 comment by @plehegar)
-
Define serializer in spec to ensure JSON.stringify performs well w3c/navigation-timing#23 (1 comment by @toddreifsteck)
-
-
9 pull requests opened.
-
Removed one more reference to linkNegotiation w3c/navigation-timing#34, by @plehegar.
-
Fixed various broken links (workerStart, processing model, etc.) w3c/navigation-timing#33, by @plehegar.
-
performance.timing is deprecated w3c/navigation-timing#32, by @plehegar.
-
Historical redirectCount and type are unsigned short w3c/navigation-timing#31, by @plehegar.
-
TYPE_RESERVED is 255 w3c/navigation-timing#30, by @plehegar.
-
Removed section on vendor prefixes w3c/navigation-timing#27, by @plehegar.
-
Revert "Expose the interface to Window and Worker" w3c/navigation-timing#26, by @plehegar.
-
Expose the interface to Window and Worker w3c/navigation-timing#25, by @plehegar.
-
Added historical section for Nagivation Timing 1 object w3c/navigation-timing#24, by @plehegar.
-
-
8 pull requests merged.
-
Fixed various broken links (workerStart, processing model, etc.) w3c/navigation-timing#33.
-
Removed one more reference to linkNegotiation w3c/navigation-timing#34.
-
Historical redirectCount and type are unsigned short w3c/navigation-timing#31.
-
TYPE_RESERVED is 255 w3c/navigation-timing#30.
-
Removed section on vendor prefixes w3c/navigation-timing#27.
-
Revert "Expose the interface to Window and Worker" w3c/navigation-timing#26.
-
Added historical section for Nagivation Timing 1 object w3c/navigation-timing#24.
-
Expose the interface to Window and Worker w3c/navigation-timing#25.
-
-
5 pull requests received 18 new comments.
-
Added historical section for Nagivation Timing 1 object w3c/navigation-timing#24 (11 comments by @igrigorik, @plehegar, @toddreifsteck)
-
Expose the interface to Window and Worker w3c/navigation-timing#25 (4 comments by @igrigorik, @plehegar, @toddreifsteck)
-
Fixed various broken links (workerStart, processing model, etc.) w3c/navigation-timing#33 (1 comment by @igrigorik)
-
w3c/hr-time
-
3 issues opened.
-
Define the performance attribute for workers w3c/hr-time#10, by @foolip.
-
Define the window.performance attribute w3c/hr-time#9, by @foolip.
-
Performance should be a partial interface? w3c/hr-time#8, by @foolip.
-
-
4 issues closed.
-
Timing attacks w3c/hr-time#4.
-
Define the window.performance attribute w3c/hr-time#9.
-
Define the performance attribute for workers w3c/hr-time#10.
-
Performance should be a partial interface? w3c/hr-time#8.
-
-
1 issue reopened.
-
Timing attacks w3c/hr-time#4, by @igrigorik.
-
-
4 issues received 20 new comments.
-
Define the performance attribute for workers w3c/hr-time#10 (13 comments by @bzbarsky, @foolip, @igrigorik, @toddreifsteck)
-
-
3 pull requests opened.
-
Improve translateTime description and clarify monotonic clock section w3c/hr-time#13, by @plehegar.
-
Clamp resolution to 5 microseconds w3c/hr-time#12, by @igrigorik.
-
Added a serializer on performance objects w3c/hr-time#11, by @plehegar.
-
-
3 pull requests merged.
-
Clamp resolution to 5 microseconds w3c/hr-time#12.
-
Added a serializer on performance objects w3c/hr-time#11.
-
-
2 pull requests received 8 new comments.
-
Clamp resolution to 5 microseconds w3c/hr-time#12 (7 comments by @igrigorik, @plehegar, @toddreifsteck, @yoavweiss)
-
Improve translateTime description and clarify monotonic clock section w3c/hr-time#13 (1 comment by @igrigorik)
-
w3c/web-performance
-
1 issue opened.
-
Need to address security bug in performance.now() in the spec w3c/web-performance#7, by @bzbarsky.
-
-
1 issue closed.
-
Need to address security bug in performance.now() in the spec w3c/web-performance#7.
-
-
1 issue received 1 new comment.
-
Need to address security bug in performance.now() in the spec w3c/web-performance#7 (1 comment by @igrigorik)
-
Lifecycle
-
1 charter started.
-
Chartered until 31 May 2016. Participants had to rejoin under this charter.
-
TR publications
-
7 documents published.
-
Navigation Timing 2 published twice as a Working Draft. History of Navigation Timing 2
-
Frame Timing published as a Working Draft. History of Frame Timing
-
High Resolution Time Level 2 published as a Working Draft. History of High Resolution Time Level 2
-
Resource Timing published 3 times as a Working Draft. History of Resource Timing
-
Participants
-
5 participants left.
-
Xiaoqian Wu (W3C) left.
-
David Newton (W3C Invited Experts) left.
-
Rob Dickinson (W3C Invited Experts) left.
-
Michael[tm] Smith (sideshowbarker) (W3C) left.
-
Philippe Le Hegaret (W3C) left.
-
-
1 organization joined.
-
OpenJS Foundation joined.
-
-
22 organizations left.
-
Alibaba Group left.
-
SOASTA left.
-
Apple Inc. left.
-
Tencent left.
-
Mozilla Foundation left.
-
Baidu, Inc. left.
-
Vodafone left.
-
Rakuten Group, Inc. left.
-
Mitsubishi Electric Corporation left.
-
Verizon left.
-
Infraware, Inc left.
-
Afilias Limited left.
-
Microsoft Corporation left.
-
Orange left.
-
Verisign, Inc. left.
-
eBay left.
-
Google LLC left.
-
OpenJS Foundation left.
-
Akamai Technologies left.
-
Dynatrace LLC left.
-
Yandex left.
-
Intel Corporation left.
-
GitHub
w3c/performance-timeline
-
2 issues opened.
-
drop text about prefixes w3c/performance-timeline#27, by @plehegar.
-
startTime is relative to time origin of PerformanceEntry object's global w3c/performance-timeline#25, by @plehegar.
-
-
8 issues closed.
-
get(Entries|EntriesByType|EntriesByName) methods spec'ed to return a copy w3c/performance-timeline#20.
-
Spec needs to clarify what to do with existing records when observing w3c/performance-timeline#16.
-
Annotation of performance entries w3c/performance-timeline#2.
-
Second example disconnects immediately which means nothing is delivered w3c/performance-timeline#15.
-
Timing of the observer callbacks is not defined w3c/performance-timeline#14.
-
Lazy prefix on LazyPerformanceEntryList doesn't add value w3c/performance-timeline#17.
-
typedef for PerformanceEntryList looks wrong w3c/performance-timeline#18.
-
observe should throw a TypeError not an AbortError for invalid arguments w3c/performance-timeline#19.
-
-
9 issues received 42 new comments.
-
get(Entries|EntriesByType|EntriesByName) methods spec'ed to return a copy w3c/performance-timeline#20 (17 comments by @bzbarsky, @igrigorik, @mpb, @natduca, @nicjansma, @toddreifsteck)
-
When are new entries delivered to observer? w3c/performance-timeline#13 (11 comments by @annevk, @hiikezoe, @igrigorik, @nicjansma, @plehegar)
-
Spec needs to clarify what to do with existing records when observing w3c/performance-timeline#16 (6 comments by @esprehn, @igrigorik, @mpb)
-
Lazy prefix on LazyPerformanceEntryList doesn't add value w3c/performance-timeline#17 (3 comments by @igrigorik, @mpb)
-
Timing of the observer callbacks is not defined w3c/performance-timeline#14 (1 comment by @igrigorik)
-
observe should throw a TypeError not an AbortError for invalid arguments w3c/performance-timeline#19 (1 comment by @mpb)
-
Second example disconnects immediately which means nothing is delivered w3c/performance-timeline#15 (1 comment by @mpb)
-
-
5 pull requests opened.
-
Now uses HR-TIME as the basis w3c/performance-timeline#26, by @plehegar.
-
AbortError => TypeError w3c/performance-timeline#24, by @mpb.
-
Fix typedef syntax w3c/performance-timeline#23, by @mpb.
-
Changed parameter name to remove 'Lazy' w3c/performance-timeline#22, by @mpb.
-
Fix: #15 Second example disconnects immediately w3c/performance-timeline#21, by @mpb.
-
-
5 pull requests merged.
-
Extend getEntries to allow attribute filtering w3c/performance-timeline#11.
-
Fix: #15 Second example disconnects immediately w3c/performance-timeline#21.
-
Changed parameter name to remove 'Lazy' w3c/performance-timeline#22.
-
Fix typedef syntax w3c/performance-timeline#23.
-
AbortError => TypeError w3c/performance-timeline#24.
-
-
7 pull requests received 25 new comments.
-
Now uses HR-TIME as the basis w3c/performance-timeline#26 (6 comments by @igrigorik, @plehegar, @toddreifsteck)
-
Extend getEntries to allow attribute filtering w3c/performance-timeline#11 (5 comments by @DigiTec, @igrigorik)
-
Fix: #15 Second example disconnects immediately w3c/performance-timeline#21 (5 comments by @igrigorik, @mpb)
-
w3c/user-timing
-
3 issues opened.
-
drop text about prefixes w3c/user-timing#7, by @plehegar.
-
Platform indicators w3c/user-timing#6, by @plehegar.
-
Better Recommended Mark Names? w3c/user-timing#5, by @plehegar.
-
-
1 issue closed.
-
negative duration values w3c/user-timing#2.
-
-
5 issues received 23 new comments.
-
1 pull request opened.
-
Negative measure values are valid w3c/user-timing#4, by @igrigorik.
-
-
1 pull request merged.
-
Negative measure values are valid w3c/user-timing#4.
-
-
1 pull request received 4 new comments.
-
Negative measure values are valid w3c/user-timing#4 (4 comments by @eliperelman, @igrigorik, @toddreifsteck)
-
w3c/hr-time
-
3 issues opened.
-
Switch editor's draft to respec w3c/hr-time#5, by @plehegar.
-
Timing attacks w3c/hr-time#4, by @plehegar.
-
workerStart and "current document" ? w3c/hr-time#3, by @plehegar.
-
-
2 issues closed.
-
workerStart and "current document" ? w3c/hr-time#3.
-
Switch editor's draft to respec w3c/hr-time#5.
-
-
1 issue received 3 new comments.
-
2 pull requests opened.
-
respec and moving the base interface w3c/hr-time#7, by @plehegar.
-
Update 'time origin' and `workerStart` definitions w3c/hr-time#6, by @igrigorik.
-
-
2 pull requests merged.
-
Update 'time origin' and `workerStart` definitions w3c/hr-time#6.
-
respec and moving the base interface w3c/hr-time#7.
-
-
2 pull requests received 25 new comments.
-
Update 'time origin' and `workerStart` definitions w3c/hr-time#6 (21 comments by @bzbarsky, @DigiTec, @igrigorik, @toddreifsteck)
-
respec and moving the base interface w3c/hr-time#7 (4 comments by @igrigorik, @plehegar, @toddreifsteck)
-
w3c/navigation-timing
-
3 issues opened.
-
drop text about prefixes w3c/navigation-timing#18, by @plehegar.
-
Drop linkNegotiation w3c/navigation-timing#16, by @plehegar.
-
window.performance.timing mention w3c/navigation-timing#15, by @plehegar.
-
-
1 issue closed.
-
Drop linkNegotiation w3c/navigation-timing#16.
-
-
1 issue received 2 new comments.
-
Consider refactoring navigation-timing to extend resource-timing w3c/navigation-timing#11 (2 comments by @plehegar)
-
-
2 pull requests opened.
-
Removed linkNegotiation w3c/navigation-timing#17, by @plehegar.
-
secureConnectionStart is mandatory resource-timing/issues/16 w3c/navigation-timing#14, by @plehegar.
-
-
2 pull requests merged.
-
Removed linkNegotiation w3c/navigation-timing#17.
-
secureConnectionStart is mandatory resource-timing/issues/16 w3c/navigation-timing#14.
-
-
2 pull requests received 7 new comments.
-
secureConnectionStart is mandatory resource-timing/issues/16 w3c/navigation-timing#14 (4 comments by @igrigorik, @plehegar, @toddreifsteck)
-
w3c/resource-timing
-
2 issues opened.
-
drop text about prefixes w3c/resource-timing#26, by @plehegar.
-
requestStart definition differ with navtimg w3c/resource-timing#25, by @plehegar.
-
-
3 issues closed.
-
Capturing basic auth credentials in URLs w3c/resource-timing#7.
-
Make secureConnectionStart a mandatory attribute w3c/resource-timing#16.
-
secureConnectionStart should account for non-HTTPS secure transports w3c/resource-timing#14.
-
-
3 issues received 15 new comments.
-
Capturing basic auth credentials in URLs w3c/resource-timing#7 (8 comments by @annevk, @igrigorik, @toddreifsteck)
-
Make secureConnectionStart a mandatory attribute w3c/resource-timing#16 (4 comments by @plehegar, @toddreifsteck, @yoavweiss)
-
secureConnectionStart should account for non-HTTPS secure transports w3c/resource-timing#14 (3 comments by @furoshiki, @plehegar, @toddreifsteck)
-
-
1 pull request opened.
-
secureConnectionStart is mandatory #16 w3c/resource-timing#24, by @plehegar.
-
-
1 pull request merged.
-
secureConnectionStart is mandatory #16 w3c/resource-timing#24.
-
-
2 pull requests received 5 new comments.
-
secureConnectionStart is mandatory #16 w3c/resource-timing#24 (4 comments by @igrigorik, @plehegar, @toddreifsteck)
-
Convert HTTPS to secure transport to ensure it is recorded for secure tr... w3c/resource-timing#15 (1 comment by @nicjansma)
-
w3c/charter-webperf
-
5 issues opened.
-
Workers support and mapping timelines w3c/charter-webperf#22, by @plehegar.
-
Deliverables and their interrelationships are a bit of a mess. w3c/charter-webperf#21, by @plehegar.
-
Generating use cases and review other specs w3c/charter-webperf#20, by @plehegar.
-
Shut down the webperf wg, move all specs to webapps. w3c/charter-webperf#19, by @Ms2ger.
-
Get rid of telcons. w3c/charter-webperf#18, by @Ms2ger.
-
-
5 issues closed.
-
Generating use cases and review other specs w3c/charter-webperf#20.
-
Get rid of telcons. w3c/charter-webperf#18.
-
Deliverables and their interrelationships are a bit of a mess. w3c/charter-webperf#21.
-
Workers support and mapping timelines w3c/charter-webperf#22.
-
Shut down the webperf wg, move all specs to webapps. w3c/charter-webperf#19.
-
-
5 issues received 28 new comments.
-
Get rid of telcons. w3c/charter-webperf#18 (13 comments by @igrigorik, @Ms2ger, @plehegar, @tobint, @toddreifsteck, @wayneca)
-
Generating use cases and review other specs w3c/charter-webperf#20 (6 comments by @igrigorik, @plehegar, @toddreifsteck, @wayneca)
-
Workers support and mapping timelines w3c/charter-webperf#22 (4 comments by @igrigorik, @plehegar, @toddreifsteck)
-
Shut down the webperf wg, move all specs to webapps. w3c/charter-webperf#19 (3 comments by @igrigorik, @plehegar)
-
Deliverables and their interrelationships are a bit of a mess. w3c/charter-webperf#21 (2 comments by @plehegar, @toddreifsteck)
-
-
4 pull requests opened.
-
Added primer and dependencies/processing model w3c/charter-webperf#26, by @plehegar.
-
Added primer and dependencies/processing model w3c/charter-webperf#25, by @plehegar.
-
Added horizontal reviews and user guides w3c/charter-webperf#24, by @plehegar.
-
Asynchronous decisions w3c/charter-webperf#23, by @plehegar.
-
-
4 pull requests merged.
-
Asynchronous decisions w3c/charter-webperf#23.
-
Added primer and dependencies/processing model w3c/charter-webperf#25.
-
Added primer and dependencies/processing model w3c/charter-webperf#26.
-
Added horizontal reviews and user guides w3c/charter-webperf#24.
-
-
4 pull requests received 12 new comments.
-
Added primer and dependencies/processing model w3c/charter-webperf#25 (6 comments by @igrigorik, @plehegar, @toddreifsteck)
-
Added primer and dependencies/processing model w3c/charter-webperf#26 (2 comments by @igrigorik, @toddreifsteck)
-
Added horizontal reviews and user guides w3c/charter-webperf#24 (2 comments by @igrigorik, @toddreifsteck)
-
w3c/network-error-logging
-
1 issue received 7 new comments.
w3c/beacon
-
1 issue received 3 new comments.
-
Clarify interaction with CORS (preflight requests) w3c/beacon#10 (3 comments by @annevk, @igrigorik)
-
TR publications
-
2 documents published.
-
Navigation Timing 2 published as a Working Draft. History of Navigation Timing 2
-
Resource Timing published as a Working Draft. History of Resource Timing
-
GitHub
w3c/performance-timeline
-
8 issues opened.
-
get(Entries|EntriesByType|EntriesByName) methods spec'ed to return a copy w3c/performance-timeline#20, by @esprehn.
-
observe should throw a TypeError not an AbortError for invalid arguments w3c/performance-timeline#19, by @esprehn.
-
typedef for PerformanceEntryList looks wrong w3c/performance-timeline#18, by @esprehn.
-
Lazy prefix on LazyPerformanceEntryList doesn't add value w3c/performance-timeline#17, by @esprehn.
-
Spec needs to clarify what to do with existing records when observing w3c/performance-timeline#16, by @esprehn.
-
Second example disconnects immediately which means nothing is delivered w3c/performance-timeline#15, by @esprehn.
-
Timing of the observer callbacks is not defined w3c/performance-timeline#14, by @esprehn.
-
When are new entries delivered to observer? w3c/performance-timeline#13, by @igrigorik.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
(WIP) Observer-based processing w3c/performance-timeline#12, by @igrigorik.
-
-
1 pull request closed.
-
Add "group" concept to performance timeline w3c/performance-timeline#9.
-
-
2 pull requests received 23 new comments.
-
Extend getEntries to allow attribute filtering w3c/performance-timeline#11 (22 comments by @DigiTec, @igrigorik, @lawnsea, @natduca, @toddreifsteck)
-
w3c/navigation-timing
-
1 issue opened.
-
domLoading entry does not seem to have a purpose in modern browsers w3c/navigation-timing#13, by @toddreifsteck.
-
-
1 issue closed.
-
domLoading entry does not seem to have a purpose in modern browsers w3c/navigation-timing#13.
-
-
1 issue received 10 new comments.
-
domLoading entry does not seem to have a purpose in modern browsers w3c/navigation-timing#13 (10 comments by @igrigorik, @nicjansma, @plehegar, @toddreifsteck)
-
w3c/resource-timing
-
2 issues opened.
-
Clarify "zero time" in Workers w3c/resource-timing#23, by @igrigorik.
-
RT should tell about the failed request and http status code. w3c/resource-timing#22, by @sahilb.
-
-
3 issues closed.
-
Consider adding networkDuration w3c/resource-timing#13.
-
Resource timing vs Resource timing lvl 2 w3c/resource-timing#2.
-
RT should tell about the failed request and http status code. w3c/resource-timing#22.
-
-
1 issue reopened.
-
Clarify presence of requests that don't return a response w3c/resource-timing#12, by @igrigorik.
-
-
6 issues received 14 new comments.
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (7 comments by @annevk, @bluesmoon, @igrigorik, @toddreifsteck)
-
Make secureConnectionStart a mandatory attribute w3c/resource-timing#16 (2 comments by @igrigorik, @toddreifsteck)
-
RT should tell about the failed request and http status code. w3c/resource-timing#22 (1 comment by @igrigorik)
-
-
1 pull request merged.
-
Convert HTTPS to secure transport to ensure it is recorded for secure tr... w3c/resource-timing#15.
-
-
1 pull request received 1 new comment.
-
Convert HTTPS to secure transport to ensure it is recorded for secure tr... w3c/resource-timing#15 (1 comment by @igrigorik)
-
w3c/beacon
-
1 issue opened.
-
Clarify interaction with CORS (preflight requests) w3c/beacon#10, by @igrigorik.
-
-
2 issues received 5 new comments.
w3c/network-error-logging
-
2 issues opened.
-
Interaction with ServiceWorker w3c/network-error-logging#54, by @igrigorik.
-
Header syntax w3c/network-error-logging#52, by @mnot.
-
-
1 issue closed.
-
Header syntax w3c/network-error-logging#52.
-
-
2 issues received 4 new comments.
-
1 pull request opened.
-
Header cleanup w3c/network-error-logging#53, by @igrigorik.
-
-
1 pull request merged.
-
Header cleanup w3c/network-error-logging#53.
-
-
1 pull request received 4 new comments.
w3c/user-timing
-
2 issues received 5 new comments.
-
SYNTAX_ERR exception for markName argument w3c/user-timing#1 (3 comments by @igrigorik, @toddreifsteck)
-
w3c/server-timing
-
1 pull request merged.
-
Fix Server-Timing header w3c/server-timing#2.
-
-
1 pull request received 1 new comment.
TR publications
-
8 documents published.
-
Server Timing published as a Working Draft. History of Server Timing
-
Frame Timing published as a Working Draft. History of Frame Timing
-
Network Error Logging published twice as a Working Draft. History of Network Error Logging
-
Resource Hints published twice as a Working Draft. History of Resource Hints
-
Navigation Timing 2 published as a Working Draft. History of Navigation Timing 2
-
Resource Timing published as a Working Draft. History of Resource Timing
-
Participants
-
1 organization joined.
-
Alibaba Group joined.
-
GitHub
w3c/performance-timeline
-
2 issues closed.
-
Notification for new performance entries w3c/performance-timeline#1.
-
Add firstPaint PerformanceEntry w3c/performance-timeline#4.
-
-
3 issues received 4 new comments.
-
2 pull requests opened.
-
Extend getEntries to allow attribute filtering w3c/performance-timeline#11, by @igrigorik.
-
PerformanceObserver w3c/performance-timeline#10, by @igrigorik.
-
-
1 pull request merged.
-
PerformanceObserver w3c/performance-timeline#10.
-
-
1 pull request closed.
-
(WIP) PerformanceObserver w3c/performance-timeline#8.
-
-
3 pull requests received 10 new comments.
-
Add "group" concept to performance timeline w3c/performance-timeline#9 (7 comments by @igrigorik, @lawnsea, @nicjansma)
-
w3c/server-timing
-
1 pull request opened.
-
Fix Server-Timing header w3c/server-timing#2, by @igrigorik.
-
w3c/resource-timing
-
1 issue opened.
-
RT should handle multi-request fetches w3c/resource-timing#21, by @igrigorik.
-
-
1 issue closed.
-
Add workerStart attribute to measure (Service)Worker startup time w3c/resource-timing#11.
-
-
2 issues received 3 new comments.
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (2 comments by @annevk, @igrigorik)
-
-
2 pull requests opened.
-
fixing typo w3c/resource-timing#20, by @dret.
-
Surface failed fetches in the performance timeline w3c/resource-timing#19, by @igrigorik.
-
-
3 pull requests merged.
-
Surface failed fetches in the performance timeline w3c/resource-timing#19.
-
fixing typo w3c/resource-timing#20.
-
Add workerStart attribute to measure SW startup w3c/resource-timing#18.
-
-
3 pull requests received 9 new comments.
-
Surface failed fetches in the performance timeline w3c/resource-timing#19 (7 comments by @igrigorik, @mikewest, @toddreifsteck, @yoavweiss)
-
w3c/navigation-timing
-
1 issue closed.
-
Account for ServiceWorker startup time w3c/navigation-timing#7.
-
-
2 issues received 4 new comments.
-
Consider refactoring navigation-timing to extend resource-timing w3c/navigation-timing#11 (3 comments by @igrigorik, @plehegar, @toddreifsteck)
-
-
1 pull request merged.
-
removing definition of Performance interface w3c/navigation-timing#10.
-
-
1 pull request received 1 new comment.
w3c/beacon
-
1 issue opened.
-
Address Security/Privacy feedback from TPAC 2014 w3c/beacon#9, by @plehegar.
-
w3c/user-timing
-
1 issue opened.
-
Custom UserTiming Payloads w3c/user-timing#3, by @nicjansma.
-
-
1 issue received 2 new comments.
w3c/charter-webperf
-
10 issues opened.
-
Add setImmediate? w3c/charter-webperf#13, by @igrigorik.
-
Add Server Timing w3c/charter-webperf#12, by @igrigorik.
-
Drop 1 & 2 references for Nav/Resource Timing w3c/charter-webperf#11, by @igrigorik.
-
Add memory/CPU general problem statement w3c/charter-webperf#10, by @igrigorik.
-
Remove PerformanceObserver, part of PerfTimeline w3c/charter-webperf#9, by @igrigorik.
-
Remove the 1/2 nomenclature from the charter w3c/charter-webperf#8, by @toddreifsteck.
-
Fill in the schedule table w3c/charter-webperf#7, by @toddreifsteck.
-
Add section to Dependencies for review w3c/charter-webperf#6, by @toddreifsteck.
-
Add section to allow creation of use-cases that come up through feedback to group w3c/charter-webperf#5, by @toddreifsteck.
-
Scope and deliverables for the new charter w3c/charter-webperf#3, by @igrigorik.
-
-
10 issues closed.
-
Add section to allow creation of use-cases that come up through feedback to group w3c/charter-webperf#5.
-
Add section to Dependencies for review w3c/charter-webperf#6.
-
Fill in the schedule table w3c/charter-webperf#7.
-
Remove the 1/2 nomenclature from the charter w3c/charter-webperf#8.
-
Remove PerformanceObserver, part of PerfTimeline w3c/charter-webperf#9.
-
Add memory/CPU general problem statement w3c/charter-webperf#10.
-
Add Server Timing w3c/charter-webperf#12.
-
Add setImmediate? w3c/charter-webperf#13.
-
Scope and deliverables for the new charter w3c/charter-webperf#3.
-
Drop 1 & 2 references for Nav/Resource Timing w3c/charter-webperf#11.
-
-
2 issues received 2 new comments.
-
7 pull requests opened.
-
2015-2016 charter w3c/charter-webperf#16, by @igrigorik.
-
2015 draft w3c/charter-webperf#15, by @igrigorik.
-
Remove RCS timestamp w3c/charter-webperf#14, by @sideshowbarker.
-
Initial draft of 2015 charter w3c/charter-webperf#4, by @toddreifsteck.
-
Replace prerender with resource hints and added preload w3c/charter-webperf#2, by @yoavweiss.
-
Added visibility observer w3c/charter-webperf#1, by @yoavweiss.
-
5 pull requests merged.
-
Tweaks w3c/charter-webperf#17.
-
2015-2016 charter w3c/charter-webperf#16.
-
2015 draft w3c/charter-webperf#15.
-
Initial draft of 2015 charter w3c/charter-webperf#4.
-
Remove RCS timestamp w3c/charter-webperf#14.
-
-
2 pull requests closed.
-
Added visibility observer w3c/charter-webperf#1.
-
Replace prerender with resource hints and added preload w3c/charter-webperf#2.
-
-
6 pull requests received 16 new comments.
-
Replace prerender with resource hints and added preload w3c/charter-webperf#2 (2 comments by @igrigorik, @yoavweiss)
w3c/network-error-logging
-
1 pull request opened.
-
updating JSON reference w3c/network-error-logging#51, by @dret.
-
-
1 pull request merged.
-
updating JSON reference w3c/network-error-logging#51.
-
-
1 pull request received 1 new comment.
TR publications
-
1 document published.
-
Network Error Logging published as a Working Draft. History of Network Error Logging
-
Participants
-
1 organization joined.
-
SOASTA joined.
-
GitHub
w3c/beacon
-
1 issue opened.
-
The context for fetching the beacon should be "beacon" w3c/beacon#7, by @ehsan.
-
-
1 issue closed.
-
The context for fetching the beacon should be "beacon" w3c/beacon#7.
-
-
1 issue received 5 new comments.
-
The context for fetching the beacon should be "beacon" w3c/beacon#7 (5 comments by @annevk, @ehsan, @igrigorik, @plehegar)
-
-
1 pull request opened.
-
Change the context for the beacon fetch to 'beacon' w3c/beacon#8, by @ehsan.
-
-
1 pull request merged.
-
Change the context for the beacon fetch to 'beacon' w3c/beacon#8.
-
-
1 pull request reopened.
-
Change the context for the beacon fetch to 'beacon' w3c/beacon#8, by @plehegar.
-
w3c/resource-timing
-
1 issue opened.
-
What value should secureConnectionStart have when using preexisting connection? w3c/resource-timing#17, by @toddreifsteck.
-
-
2 issues received 21 new comments.
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (19 comments by @andydavies, @bluesmoon, @gui-poa, @igrigorik, @nicjansma, @toddreifsteck)
-
Add workerStart attribute to measure (Service)Worker startup time w3c/resource-timing#11 (2 comments by @KenjiBaheux)
-
-
1 pull request opened.
-
Add workerStart attribute to measure SW startup w3c/resource-timing#18, by @igrigorik.
-
-
1 pull request merged.
-
Make RT "worker friendly" w3c/resource-timing#10.
-
-
3 pull requests received 6 new comments.
-
Add workerStart attribute to measure SW startup w3c/resource-timing#18 (3 comments by @igrigorik, @plehegar, @toddreifsteck)
-
Convert HTTPS to secure transport to ensure it is recorded for secure tr... w3c/resource-timing#15 (1 comment by @toddreifsteck)
-
w3c/navigation-timing
-
2 issues opened.
-
Where are instances of PerformanceNavigationTiming created? w3c/navigation-timing#12, by @plehegar.
-
Consider refactoring navigation-timing to extend resource-timing w3c/navigation-timing#11, by @toddreifsteck.
-
-
1 issue closed.
-
Where are instances of PerformanceNavigationTiming created? w3c/navigation-timing#12.
-
-
3 issues received 5 new comments.
-
Connection between Navigation Timing 2 and Performance Timeline is underdefined w3c/navigation-timing#1 (3 comments by @bzbarsky, @igrigorik, @toddreifsteck)
-
Where are instances of PerformanceNavigationTiming created? w3c/navigation-timing#12 (1 comment by @plehegar)
-
Consider refactoring navigation-timing to extend resource-timing w3c/navigation-timing#11 (1 comment by @igrigorik)
-
w3c/network-error-logging
-
15 issues opened.
-
Interaction with proxies w3c/network-error-logging#49, by @igrigorik.
-
DNS errors? w3c/network-error-logging#48, by @annevk.
-
uri -> url w3c/network-error-logging#47, by @annevk.
-
Clarify report delivery to be restricted to https scheme w3c/network-error-logging#46, by @igrigorik.
-
Provide privacy section w3c/network-error-logging#45, by @igrigorik.
-
Restrict report-uri's to absolute URIs w3c/network-error-logging#44, by @igrigorik.
-
Referer reporting should be subject to Referer policy w3c/network-error-logging#43, by @igrigorik.
-
NEL registration should be based on origin & restricted to HTTPS w3c/network-error-logging#42, by @igrigorik.
-
At least one examples at the start of doc w3c/network-error-logging#41, by @marcoscaceres.
-
Network Error Logging w3c/network-error-logging#40, by @marcoscaceres.
-
repeated secure transport requirement w3c/network-error-logging#39, by @marcoscaceres.
-
Processing directive fields w3c/network-error-logging#38, by @marcoscaceres.
-
directive names not in ABNF? w3c/network-error-logging#37, by @marcoscaceres.
-
Mixed content w3c/network-error-logging#36, by @marcoscaceres.
-
secure transport errors or warnings w3c/network-error-logging#35, by @marcoscaceres.
-
-
12 issues closed.
-
NEL registration should be based on origin & restricted to HTTPS w3c/network-error-logging#42.
-
Provide privacy section w3c/network-error-logging#45.
-
Referer reporting should be subject to Referer policy w3c/network-error-logging#43.
-
Restrict report-uri's to absolute URIs w3c/network-error-logging#44.
-
Clarify report delivery to be restricted to https scheme w3c/network-error-logging#46.
-
uri -> url w3c/network-error-logging#47.
-
secure transport errors or warnings w3c/network-error-logging#35.
-
Network Error Logging w3c/network-error-logging#40.
-
repeated secure transport requirement w3c/network-error-logging#39.
-
Processing directive fields w3c/network-error-logging#38.
-
directive names not in ABNF? w3c/network-error-logging#37.
-
Mixed content w3c/network-error-logging#36.
-
-
8 issues received 15 new comments.
-
NEL registration should be based on origin & restricted to HTTPS w3c/network-error-logging#42 (4 comments by @annevk, @igrigorik, @mcmanus, @yoavweiss)
-
Clarify report delivery to be restricted to https scheme w3c/network-error-logging#46 (3 comments by @igrigorik, @mikewest, @yoavweiss)
-
-
3 pull requests opened.
-
Restrict NEL to "Potentially Trustworthy" origins w3c/network-error-logging#50, by @igrigorik.
-
removed use of MAY keyword in informative section w3c/network-error-logging#34, by @marcoscaceres.
-
Rewrite of abstract w3c/network-error-logging#33, by @marcoscaceres.
-
-
2 pull requests merged.
-
Restrict NEL to "Potentially Trustworthy" origins w3c/network-error-logging#50.
-
removed use of MAY keyword in informative section w3c/network-error-logging#34.
-
-
1 pull request closed.
-
Rewrite of abstract w3c/network-error-logging#33.
-
-
1 pull request received 2 new comments.
w3c/performance-timeline
-
1 issue closed.
-
Expose performance interface to worker w3c/performance-timeline#6.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Add "group" concept to performance timeline w3c/performance-timeline#9, by @igrigorik.
-
(WIP) PerformanceObserver w3c/performance-timeline#8, by @igrigorik.
-
-
1 pull request merged.
-
Define Performance interface w3c/performance-timeline#7.
-
-
3 pull requests received 12 new comments.
-
Add "group" concept to performance timeline w3c/performance-timeline#9 (5 comments by @igrigorik, @natduca, @nicjansma, @toddreifsteck)
-
w3c/hr-time
-
1 issue closed.
-
Clarify ServiceWorker time origin w3c/hr-time#1.
-
-
1 pull request merged.
-
Consistent time origin for Shared+Dedicated workers w3c/hr-time#2.
-
-
1 pull request received 1 new comment.
TR publications
-
2 documents published.
-
Frame Timing published as a Working Draft. History of Frame Timing
-
Server Timing published as a First Public Working Draft. History of Server Timing
-
GitHub
w3c/resource-timing
-
8 issues opened.
-
Make secureConnectionStart a mandatory attribute w3c/resource-timing#16, by @igrigorik.
-
secureConnectionStart should account for non-HTTPS secure transports w3c/resource-timing#14, by @toddreifsteck.
-
Consider adding networkDuration w3c/resource-timing#13, by @toddreifsteck.
-
Clarify presence of requests that don't return a response w3c/resource-timing#12, by @igrigorik.
-
Add workerStart attribute to measure (Service)Worker startup time w3c/resource-timing#11, by @igrigorik.
-
How should time for HSTS "redirect" from http to https be represented? w3c/resource-timing#9, by @toddreifsteck.
-
Improve "initiator" reporting w3c/resource-timing#8, by @vayam.
-
Capturing basic auth credentials in URLs w3c/resource-timing#7, by @plehegar.
-
-
1 issue closed.
-
How should time for HSTS "redirect" from http to https be represented? w3c/resource-timing#9.
-
-
5 issues received 18 new comments.
-
Add workerStart attribute to measure (Service)Worker startup time w3c/resource-timing#11 (6 comments by @furoshiki, @igrigorik, @slightlyoff, @toddreifsteck, @vigneshshanmugam, @yoavweiss)
-
How should time for HSTS "redirect" from http to https be represented? w3c/resource-timing#9 (4 comments by @igrigorik, @toddreifsteck)
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (1 comment by @andydavies)
-
Are PerformanceResourceTiming instances supposed to have a serializer? w3c/resource-timing#3 (1 comment by @bzbarsky)
-
-
2 pull requests opened.
-
Convert HTTPS to secure transport to ensure it is recorded for secure tr... w3c/resource-timing#15, by @toddreifsteck.
-
Make RT "worker friendly" w3c/resource-timing#10, by @igrigorik.
-
-
2 pull requests received 4 new comments.
-
Convert HTTPS to secure transport to ensure it is recorded for secure tr... w3c/resource-timing#15 (3 comments by @igrigorik, @plehegar)
-
w3c/performance-timeline
-
1 issue opened.
-
Expose performance interface to worker w3c/performance-timeline#6, by @igrigorik.
-
-
2 issues received 4 new comments.
-
Expose performance interface to worker w3c/performance-timeline#6 (3 comments by @igrigorik, @plehegar, @toddreifsteck)
-
-
1 pull request opened.
-
Define Performance interface w3c/performance-timeline#7, by @igrigorik.
-
-
1 pull request received 5 new comments.
w3c/hr-time
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Consistent time origin for Shared+Dedicated workers w3c/hr-time#2, by @igrigorik.
-
w3c/network-error-logging
-
17 issues opened.
-
Investigate report-uri management workflows w3c/network-error-logging#32, by @igrigorik.
-
How does a site that does not default to a secure connection enable NEL? w3c/network-error-logging#28, by @toddreifsteck.
-
error codes should ideally link to definitions w3c/network-error-logging#27, by @toddreifsteck.
-
Please add POST ReportUri to all examples w3c/network-error-logging#26, by @toddreifsteck.
-
What is a navigation error? w3c/network-error-logging#25, by @toddreifsteck.
-
Navigation Initiation needs link to its definition w3c/network-error-logging#24, by @toddreifsteck.
-
extensions to error codes w3c/network-error-logging#23, by @toddreifsteck.
-
extensions to NEL directives w3c/network-error-logging#22, by @toddreifsteck.
-
Add link to formatting of IPv4/IPv6 addresses w3c/network-error-logging#21, by @toddreifsteck.
-
Please add example clarifying 2.2 NELHost language w3c/network-error-logging#20, by @toddreifsteck.
-
Add link to Navigation definition w3c/network-error-logging#19, by @toddreifsteck.
-
Protocol assumes HTTP w3c/network-error-logging#18, by @toddreifsteck.
-
Cross-Origin reporting w3c/network-error-logging#17, by @toddreifsteck.
-
More scenarios w3c/network-error-logging#16, by @toddreifsteck.
-
client-side type filtering w3c/network-error-logging#15, by @toddreifsteck.
-
Mechanism to disable report-uri from the server and/or user-agent? w3c/network-error-logging#14, by @toddreifsteck.
-
how are network disconnects handled? w3c/network-error-logging#13, by @toddreifsteck.
-
-
24 issues closed.
-
Mechanism to disable report-uri from the server and/or user-agent? w3c/network-error-logging#14.
-
What is a navigation error? w3c/network-error-logging#25.
-
Please add example clarifying 2.2 NELHost language w3c/network-error-logging#20.
-
Add link to formatting of IPv4/IPv6 addresses w3c/network-error-logging#21.
-
extensions to NEL directives w3c/network-error-logging#22.
-
Navigation Initiation needs link to its definition w3c/network-error-logging#24.
-
Add link to Navigation definition w3c/network-error-logging#19.
-
extensions to error codes w3c/network-error-logging#23.
-
How does a site that does not default to a secure connection enable NEL? w3c/network-error-logging#28.
-
Protocol assumes HTTP w3c/network-error-logging#18.
-
client-side type filtering w3c/network-error-logging#15.
-
Please add POST ReportUri to all examples w3c/network-error-logging#26.
-
how are network disconnects handled? w3c/network-error-logging#13.
-
Cross-Origin reporting w3c/network-error-logging#17.
-
Define error types w3c/network-error-logging#8.
-
Define collected data w3c/network-error-logging#7.
-
startTimeUTC is insufficient due to client's clock skew w3c/network-error-logging#4.
-
Best effort attempt to transmit the error w3c/network-error-logging#2.
-
Reporting multiple errors w3c/network-error-logging#1.
-
Security model for registering reporting URL w3c/network-error-logging#5.
-
Support for multiple reporting URLs? w3c/network-error-logging#9.
-
Do we need 'resource name' and url patterns? w3c/network-error-logging#10.
-
Exposing server IP in error reports w3c/network-error-logging#11.
-
Remove JS interface? w3c/network-error-logging#12.
-
-
23 issues received 50 new comments.
-
Mechanism to disable report-uri from the server and/or user-agent? w3c/network-error-logging#14 (15 comments by @AloisReitbauer, @igrigorik, @toddreifsteck)
-
extensions to NEL directives w3c/network-error-logging#22 (3 comments by @igrigorik, @toddreifsteck)
-
How does a site that does not default to a secure connection enable NEL? w3c/network-error-logging#28 (2 comments by @igrigorik, @toddreifsteck)
-
Please add POST ReportUri to all examples w3c/network-error-logging#26 (2 comments by @igrigorik, @toddreifsteck)
-
how are network disconnects handled? w3c/network-error-logging#13 (2 comments by @igrigorik, @toddreifsteck)
-
Please add example clarifying 2.2 NELHost language w3c/network-error-logging#20 (1 comment by @igrigorik)
-
Navigation Initiation needs link to its definition w3c/network-error-logging#24 (1 comment by @igrigorik)
-
startTimeUTC is insufficient due to client's clock skew w3c/network-error-logging#4 (1 comment by @igrigorik)
-
-
3 pull requests opened.
-
first cut at defining "network error" w3c/network-error-logging#30, by @igrigorik.
-
first cut at report-url unregister and retry logic w3c/network-error-logging#29, by @igrigorik.
-
2 pull requests merged.
-
first cut at report-url unregister and retry logic w3c/network-error-logging#29.
-
first cut at defining "network error" w3c/network-error-logging#30.
-
-
1 pull request closed.
-
fix-links w3c/network-error-logging#31.
-
-
1 pull request received 2 new comments.
w3c/navigation-timing
-
1 pull request opened.
-
removing definition of Performance interface w3c/navigation-timing#10, by @igrigorik.
-
w3c/server-timing
-
1 pull request opened.
-
Changed the respec URL to be relative w3c/server-timing#1, by @yoavweiss.
-
-
1 pull request merged.
-
Changed the respec URL to be relative w3c/server-timing#1.
-
-
1 pull request received 1 new comment.
w3c/user-timing
-
2 issues opened.
-
negative duration values w3c/user-timing#2, by @plehegar.
-
SYNTAX_ERR exception for markName argument w3c/user-timing#1, by @plehegar.
-
TR publications
-
2 documents published.
-
Navigation Timing 2 published as a Working Draft. History of Navigation Timing 2
-
Frame Timing published as a First Public Working Draft. History of Frame Timing
-
Participants
-
1 organization joined.
-
Apple Inc. joined.
-
GitHub
w3c/performance-timeline
-
1 pull request opened.
-
Added a serializer for PerformanceEntry objects w3c/performance-timeline#5, by @plehegar.
-
-
1 pull request merged.
-
Added a serializer for PerformanceEntry objects w3c/performance-timeline#5.
-
w3c/resource-timing
-
1 issue closed.
-
Are PerformanceResourceTiming instances supposed to have a serializer? w3c/resource-timing#3.
-
-
1 issue received 3 new comments.
-
Are PerformanceResourceTiming instances supposed to have a serializer? w3c/resource-timing#3 (3 comments by @igrigorik, @plehegar)
-
-
1 pull request opened.
-
Added a serializer for PerformanceResourceTiming objects w3c/resource-timing#6, by @plehegar.
-
-
1 pull request merged.
-
Added a serializer for PerformanceResourceTiming objects w3c/resource-timing#6.
-
-
1 pull request closed.
-
Fix the broken link for NT in refs w3c/resource-timing#5.
-
w3c/beacon
-
1 issue closed.
-
TAG comments? w3c/beacon#4.
-
-
1 issue received 1 new comment.
w3c/navigation-timing
-
1 pull request opened.
-
Fix Tobin's last name w3c/navigation-timing#9, by @astorije.
-
-
1 pull request merged.
-
Fix Tobin's last name w3c/navigation-timing#9.
-
-
1 pull request received 1 new comment.