Web Performance Working Group - Activity in 2016
No matches.
TR publications
-
4 documents published.
-
Performance Timeline Level 2 published as a Candidate Recommendation Snapshot. History of Performance Timeline Level 2
-
Cooperative Scheduling of Background Tasks published as a Working Draft. History of Cooperative Scheduling of Background Tasks
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Resource Hints published as a Working Draft. History of Resource Hints
-
Participants
-
1 participant left.
-
Wesley Hales (W3C Invited Experts) left.
-
-
1 organization joined.
-
Stripe joined.
-
GitHub
w3c/resource-timing
-
3 issues opened.
-
Increase limit of 150 for PerformanceEntrys? w3c/resource-timing#89, by @nolanlawson.
-
Resource Timing entries within the context of a service worker for handled requests? w3c/resource-timing#88, by @KenjiBaheux.
-
Ensure that first byte measurement and 1XX responses are covered by tests w3c/resource-timing#87, by @toddreifsteck.
-
-
1 issue closed.
-
Clarify definition of responseStart w3c/resource-timing#63.
-
-
4 issues received 9 new comments.
-
Increase limit of 150 for PerformanceEntrys? w3c/resource-timing#89 (3 comments by @igrigorik, @nolanlawson)
-
RT should tell about the failed request and http status code. w3c/resource-timing#22 (3 comments by @igrigorik, @vaibhavtripathi)
-
Resource Timing entries within the context of a service worker for handled requests? w3c/resource-timing#88 (2 comments by @igrigorik, @wanderview)
-
-
3 pull requests opened.
-
s/MUST/MAY semantics for failed fetches in L2 w3c/resource-timing#85, by @igrigorik.
-
fix a small bug in the example w3c/resource-timing#84, by @siusin.
-
4 pull requests merged.
-
clarify responseStart w3c/resource-timing#83.
-
Typo fix w3c/resource-timing#86.
-
s/MUST/MAY semantics for failed fetches in L2 w3c/resource-timing#85.
-
fix a small bug in the example w3c/resource-timing#84.
-
-
4 pull requests received 9 new comments.
-
s/MUST/MAY semantics for failed fetches in L2 w3c/resource-timing#85 (2 comments by @igrigorik, @plehegar)
w3c/performance-timeline
-
2 issues closed.
-
[Maintenance, reminder] Cycle environment variables that were encrypted with Travis w3c/performance-timeline#63.
-
Transition Level 2 to CR w3c/performance-timeline#62.
-
-
3 issues received 4 new comments.
-
Ability to observers past set of performance entries w3c/performance-timeline#56 (1 comment by @igrigorik)
-
[Maintenance, reminder] Cycle environment variables that were encrypted with Travis w3c/performance-timeline#63 (1 comment by @igrigorik)
w3c/navigation-timing
-
5 issues opened.
-
Report URL in "name" attribute (instead of "document") w3c/navigation-timing#59, by @spanicker.
-
Need tests for TAO w3c/navigation-timing#58, by @toddreifsteck.
-
Automatic publication of the spec fails due to markup errors w3c/navigation-timing#57, by @tripu.
-
Links in status section are broken w3c/navigation-timing#54, by @bripkens.
-
Clarify TAO check for unloadEventStart|End w3c/navigation-timing#53, by @spanicker.
-
-
4 issues closed.
-
Contribute tests for navigation timing w3c/navigation-timing#39.
-
Automatic publication of the spec fails due to markup errors w3c/navigation-timing#57.
-
Clarify TAO check for unloadEventStart|End w3c/navigation-timing#53.
-
Links in status section are broken w3c/navigation-timing#54.
-
-
4 issues received 11 new comments.
-
Automatic publication of the spec fails due to markup errors w3c/navigation-timing#57 (5 comments by @igrigorik, @plehegar, @siusin, @tripu)
-
data bias issues due to deferring reporting of all nav timing metrics to the load event w3c/navigation-timing#50 (4 comments by @bmaurer, @igrigorik)
-
Report URL in "name" attribute (instead of "document") w3c/navigation-timing#59 (1 comment by @igrigorik)
-
-
2 pull requests opened.
-
chore: use new school WebIDL w3c/navigation-timing#56, by @marcoscaceres.
-
apply TAO check w3c/navigation-timing#55, by @igrigorik.
-
-
2 pull requests merged.
-
apply TAO check w3c/navigation-timing#55.
-
chore: use new school WebIDL w3c/navigation-timing#56.
-
-
2 pull requests received 4 new comments.
w3c/user-timing
-
2 issues opened.
-
measure() may throw SyntaxError w3c/user-timing#21, by @plehegar.
-
2 issues received 7 new comments.
-
What does "navigationStart" mean as a second argument to performance.measure() in a web worker? w3c/user-timing#22 (5 comments by @bzbarsky, @igrigorik, @nicjansma, @toddreifsteck)
-
w3c/requestidlecallback
-
1 issue opened.
-
Images not found for w3.org w3c/requestidlecallback#51, by @Krinkle.
-
-
7 issues closed.
-
Integration with IntersectionObserver w3c/requestidlecallback#36.
-
Images not found for w3.org w3c/requestidlecallback#51.
-
What should occur if requestIdleCallback backs up? w3c/requestidlecallback#43.
-
Improve the specification of how requestIdleCallback events are ordered w3c/requestidlecallback#41.
-
When/how could 50 ms chunks of time occur vs. typical frame-based 16 ms? w3c/requestidlecallback#42.
-
Use push/pop or append/take-the-first w3c/requestidlecallback#45.
-
-
6 issues received 14 new comments.
-
diagram with frame commit and vsync is inaccurate for some browsers w3c/requestidlecallback#44 (9 comments by @igrigorik, @rmcilroy, @toddreifsteck)
-
What should occur if requestIdleCallback backs up? w3c/requestidlecallback#43 (1 comment by @toddreifsteck)
-
It is unclear what IdleDeadline.timeRemaining() should return if JS keeps the IdleDealing object alive even after the callback call. w3c/requestidlecallback#47 (1 comment by @bzbarsky)
-
-
1 pull request merged.
-
Incorporate feedback w3c/requestidlecallback#50.
-
-
1 pull request received 2 new comments.
w3c/beacon
-
1 issue closed.
-
Need to add tests for sendBeacon w3c/beacon#29.
-
-
2 issues received 3 new comments.
-
Ambiguity on "maximum data size" limit and enforcement w3c/beacon#38 (2 comments by @andrewwakeling, @igrigorik)
-
-
1 pull request received 1 new comment.
w3c/longtasks
-
1 issue closed.
-
Demo is locked to Google employees? w3c/longtasks#3.
-
-
1 issue received 1 new comment.
w3c/perf-timing-primer
-
3 pull requests opened.
-
Fix a minor bug in an example of RT w3c/perf-timing-primer#6, by @xfq.
-
Remove translateTime w3c/perf-timing-primer#5, by @xfq.
-
Some editorial changes w3c/perf-timing-primer#4, by @xfq.
-
-
3 pull requests merged.
-
Remove translateTime w3c/perf-timing-primer#5.
-
Fix a minor bug in an example of RT w3c/perf-timing-primer#6.
-
Some editorial changes w3c/perf-timing-primer#4.
-
-
3 pull requests received 6 new comments.
w3c/paint-timing
-
1 issue closed.
-
Transfer to WICG w3c/paint-timing#2.
-
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Fix grammatical typo in README w3c/paint-timing#3, by @piperchester.
-
-
1 pull request received 1 new comment.
TR publications
-
7 documents published.
-
Page Visibility Level 2 published as a Candidate Recommendation Snapshot. History of Page Visibility Level 2
-
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
-
Performance Timeline Level 2 published as a Working Draft. History of Performance Timeline Level 2
-
Resource Timing Level 2 published as a First Public Working Draft. History of Resource Timing Level 2
-
User Timing Level 2 published as a First Public Working Draft. History of User Timing Level 2
-
GitHub
w3c/navigation-timing
-
2 issues opened.
-
[Maintenance, reminder] Cycle environment variables that were encrypted with Travis w3c/navigation-timing#51, by @tripu.
-
data bias issues due to deferring reporting of all nav timing metrics to the load event w3c/navigation-timing#50, by @bryanmcquade.
-
-
6 issues closed.
-
Processing Model is confusing in respect of startTime and beforeunload w3c/navigation-timing#48.
-
Processing Model chart is missing domLoading marker w3c/navigation-timing#44.
-
[Maintenance, reminder] Cycle environment variables that were encrypted with Travis w3c/navigation-timing#51.
-
Relationship between performance.timing.navigationStart and hr-time time origin w3c/navigation-timing#43.
-
enum values should be hyphenated w3c/navigation-timing#47.
-
-
7 issues received 30 new comments.
-
enum values should be hyphenated w3c/navigation-timing#47 (10 comments by @dontcallmedom, @foolip, @igrigorik, @toddreifsteck)
-
Processing Model chart is missing domLoading marker w3c/navigation-timing#44 (9 comments by @igrigorik, @plehegar, @toddreifsteck, @yoavweiss)
-
It is not defined what "The PerformanceNavigationTiming interface participates in the [PERFORMANCE-TIMELINE-2] " means w3c/navigation-timing#46 (4 comments by @igrigorik, @plehegar)
-
data bias issues due to deferring reporting of all nav timing metrics to the load event w3c/navigation-timing#50 (3 comments by @bluesmoon, @bmaurer, @igrigorik)
-
Processing Model is confusing in respect of startTime and beforeunload w3c/navigation-timing#48 (2 comments by @igrigorik)
-
[Maintenance, reminder] Cycle environment variables that were encrypted with Travis w3c/navigation-timing#51 (1 comment by @igrigorik)
-
Relationship between performance.timing.navigationStart and hr-time time origin w3c/navigation-timing#43 (1 comment by @plehegar)
-
-
1 pull request opened.
-
updated timing attributes diagram w3c/navigation-timing#52, by @igrigorik.
-
-
1 pull request merged.
-
updated timing attributes diagram w3c/navigation-timing#52.
-
-
1 pull request received 4 new comments.
-
updated timing attributes diagram w3c/navigation-timing#52 (4 comments by @igrigorik, @toddreifsteck, @yoavweiss)
-
w3c/resource-timing
-
7 issues opened.
-
Clarify when entry is added to performance entry buffer w3c/resource-timing#82, by @igrigorik.
-
[Maintenance, reminder] Cycle environment variables that were encrypted with Travis w3c/resource-timing#77, by @tripu.
-
Add information about local cache performance w3c/resource-timing#76, by @bmaurer.
-
Expose the TLS certificate + other TLS parameters for a resource w3c/resource-timing#75, by @bmaurer.
-
Add fields for identifying the security protocol, cipher, signature and so on w3c/resource-timing#74, by @phistuck.
-
Clarify nextHopProtocol value for cached fetch w3c/resource-timing#73, by @igrigorik.
-
could not get the timing of xhr sometimes w3c/resource-timing#72, by @SuperMarioX.
-
-
7 issues closed.
-
Is it well defined when the "add a PerformanceResourceTiming entry" algorithm should run? w3c/resource-timing#55.
-
Initiator is not well defined w3c/resource-timing#69.
-
Review web-platform tests w3c/resource-timing#66.
-
Clarify nextHopProtocol value for cached fetch w3c/resource-timing#73.
-
could not get the timing of xhr sometimes w3c/resource-timing#72.
-
[Maintenance, reminder] Cycle environment variables that were encrypted with Travis w3c/resource-timing#77.
-
transferSize and TAO redirects w3c/resource-timing#61.
-
-
12 issues received 63 new comments.
-
Add fields for identifying the security protocol, cipher, signature and so on w3c/resource-timing#74 (22 comments by @bmaurer, @igrigorik, @mikewest, @phistuck, @sleevi)
-
Clarify nextHopProtocol value for cached fetch w3c/resource-timing#73 (10 comments by @bmaurer, @bzbarsky, @igrigorik, @toddreifsteck, @valenting)
-
Add information about local cache performance w3c/resource-timing#76 (6 comments by @bmaurer, @igrigorik, @yoavweiss)
-
Is it well defined when the "add a PerformanceResourceTiming entry" algorithm should run? w3c/resource-timing#55 (5 comments by @igrigorik, @toddreifsteck, @yoavweiss)
-
Server pushed resources in ResourceTiming w3c/resource-timing#53 (5 comments by @igrigorik, @yoavweiss)
-
Clarify definition of responseStart w3c/resource-timing#63 (4 comments by @igrigorik, @toddreifsteck)
-
[Maintenance, reminder] Cycle environment variables that were encrypted with Travis w3c/resource-timing#77 (1 comment by @siusin)
-
-
5 pull requests opened.
-
clarify responseStart w3c/resource-timing#83, by @igrigorik.
-
updated timing attribute diagram w3c/resource-timing#81, by @igrigorik.
-
Clarify initiatorType w3c/resource-timing#80, by @igrigorik.
-
Recommendation for when add/queue steps should run w3c/resource-timing#79, by @igrigorik.
-
nextHopProtocol is an empty string for local fetch w3c/resource-timing#78, by @igrigorik.
-
-
4 pull requests merged.
-
Recommendation for when add/queue steps should run w3c/resource-timing#79.
-
updated timing attribute diagram w3c/resource-timing#81.
-
Clarify initiatorType w3c/resource-timing#80.
-
nextHopProtocol is an empty string for local fetch w3c/resource-timing#78.
-
-
5 pull requests received 22 new comments.
-
Clarify initiatorType w3c/resource-timing#80 (11 comments by @igrigorik, @nicjansma, @plehegar, @toddreifsteck, @yoavweiss)
-
nextHopProtocol is an empty string for local fetch w3c/resource-timing#78 (6 comments by @igrigorik, @toddreifsteck, @valenting, @yoavweiss)
-
Recommendation for when add/queue steps should run w3c/resource-timing#79 (3 comments by @igrigorik, @toddreifsteck)
-
w3c/paint-timing
-
1 issue opened.
-
Transfer to WICG w3c/paint-timing#2, by @igrigorik.
-
-
1 issue received 5 new comments.
w3c/requestidlecallback
-
1 issue closed.
-
implementations should be allowed to consider work beyond "other event loops" w3c/requestidlecallback#46.
-
-
6 issues received 13 new comments.
-
It is unclear what IdleDeadline.timeRemaining() should return if JS keeps the IdleDealing object alive even after the callback call. w3c/requestidlecallback#47 (4 comments by @bzbarsky, @igrigorik, @rmcilroy)
-
diagram with frame commit and vsync is inaccurate for some browsers w3c/requestidlecallback#44 (3 comments by @igrigorik, @rmcilroy)
-
Use push/pop or append/take-the-first w3c/requestidlecallback#45 (2 comments by @igrigorik, @rmcilroy)
-
When/how could 50 ms chunks of time occur vs. typical frame-based 16 ms? w3c/requestidlecallback#42 (2 comments by @igrigorik, @rmcilroy)
-
Improve the specification of how requestIdleCallback events are ordered w3c/requestidlecallback#41 (1 comment by @igrigorik)
-
What should occur if requestIdleCallback backs up? w3c/requestidlecallback#43 (1 comment by @igrigorik)
-
-
1 pull request opened.
-
Incorporate feedback w3c/requestidlecallback#50, by @igrigorik.
-
w3c/charter-webperf
-
1 issue received 9 new comments.
-
Expose First Paint, First Contentful Paint, ... to developers w3c/charter-webperf#32 (9 comments by @addyosmani, @igrigorik, @krutzler, @spanicker, @toddreifsteck)
-
w3c/longtasks
-
1 pull request opened.
-
Link to Tim's time-to-interactive proposal w3c/longtasks#6, by @addyosmani.
-
-
1 pull request received 1 new comment.
w3c/performance-timeline
-
1 issue opened.
-
[Maintenance, reminder] Cycle environment variables that were encrypted with Travis w3c/performance-timeline#63, by @tripu.
-
-
1 issue reopened.
-
Transition Level 2 to CR w3c/performance-timeline#62, by @toddreifsteck.
-
-
1 issue received 8 new comments.
-
Transition Level 2 to CR w3c/performance-timeline#62 (8 comments by @igrigorik, @plehegar, @toddreifsteck)
-
w3c/beacon
-
1 issue received 9 new comments.
-
Ambiguity on "maximum data size" limit and enforcement w3c/beacon#38 (9 comments by @igrigorik, @toddreifsteck, @tyoshino)
-
-
1 pull request opened.
-
Enforce payload limits via Fetch API w3c/beacon#39, by @igrigorik.
-
-
1 pull request received 7 new comments.
w3c/user-timing
-
2 issues received 4 new comments.
w3c/hr-time
-
1 issue opened.
-
2 issues closed.
-
timeOrigin prose doesn't make sense w3c/hr-time#36.
-
Transition Level 2 to CR w3c/hr-time#34.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Improve latest version headers w3c/hr-time#39, by @plehegar.
-
-
1 pull request merged.
-
clarify timeOrigin timestamp w3c/hr-time#37.
-
-
2 pull requests received 15 new comments.
-
clarify timeOrigin timestamp w3c/hr-time#37 (10 comments by @bzbarsky, @igrigorik, @plehegar, @toddreifsteck)
-
w3c/reporting
-
3 issues opened.
-
Why is report.origin a separate field? w3c/reporting#25, by @juliatuttle.
-
What happens if *.foo.com and bar.foo.com configure differing endpoints? w3c/reporting#24, by @juliatuttle.
-
GCing an active but failing endpoint is counterproductive w3c/reporting#23, by @juliatuttle.
-
-
1 issue received 1 new comment.
-
GCing an active but failing endpoint is counterproductive w3c/reporting#23 (1 comment by @igrigorik)
-
-
1 pull request opened.
-
Update JFV reference w3c/reporting#26, by @reschke.
-
-
1 pull request merged.
-
Update JFV reference w3c/reporting#26.
-
TR publications
-
9 documents published.
-
Beacon published twice as a Working Draft. History of Beacon
-
Performance Timeline Level 2 published twice as a Working Draft. History of Performance Timeline Level 2
-
Page Visibility Level 2 published as a Working Draft. History of Page Visibility Level 2
-
High Resolution Time Level 2 published 3 times as a Working Draft. History of High Resolution Time Level 2
-
High Resolution Time Level 3 published as a First Public Working Draft. History of High Resolution Time Level 3
-
Participants
-
1 organization left.
-
Vodafone left.
-
GitHub
w3c/hr-time
-
4 issues opened.
-
timeOrigin prose doesn't make sense w3c/hr-time#36, by @bzbarsky.
-
Transition Level 2 to CR w3c/hr-time#34, by @igrigorik.
-
Move boilerplate URLs to HTTPS w3c/hr-time#33, by @tripu.
-
Add prompt to unload test w3c/hr-time#32, by @toddreifsteck.
-
-
4 issues closed.
-
Move boilerplate URLs to HTTPS w3c/hr-time#33.
-
Should time origin be defined in terms of a monotonic clock? w3c/hr-time#21.
-
Translating high resolution timestamps between globals w3c/hr-time#22.
-
Should time-origin and Date.now be related? w3c/hr-time#27.
-
-
7 issues received 29 new comments.
-
Should time origin be defined in terms of a monotonic clock? w3c/hr-time#21 (5 comments by @bzbarsky, @igrigorik, @toddreifsteck)
-
Translating high resolution timestamps between globals w3c/hr-time#22 (2 comments by @igrigorik, @toddreifsteck)
-
Should time-origin and Date.now be related? w3c/hr-time#27 (2 comments by @igrigorik, @toddreifsteck)
-
3 pull requests opened.
-
clarify timeOrigin timestamp w3c/hr-time#37, by @igrigorik.
-
Service worker reference isn't needed w3c/hr-time#35, by @plehegar.
-
remove translateTime from Level 2 w3c/hr-time#31, by @igrigorik.
-
-
2 pull requests merged.
-
Service worker reference isn't needed w3c/hr-time#35.
-
remove translateTime from Level 2 w3c/hr-time#31.
-
-
1 pull request closed.
-
Mechanism to translate timestamps between globals w3c/hr-time#29.
-
-
3 pull requests received 12 new comments.
-
Mechanism to translate timestamps between globals w3c/hr-time#29 (8 comments by @igrigorik, @plehegar, @rniwa, @toddreifsteck)
-
w3c/longtasks
-
2 issues opened.
-
Guidelines to contribute (send a pull request) w3c/longtasks#5, by @Marlysson.
-
Notes and action items from TPAC 2016 w3c/longtasks#4, by @igrigorik.
-
-
2 issues received 5 new comments.
-
Guidelines to contribute (send a pull request) w3c/longtasks#5 (2 comments by @spanicker, @yoavweiss)
w3c/resource-timing
-
3 issues opened.
-
Transition Level 2 to CR w3c/resource-timing#71, by @igrigorik.
-
Exposing CSS subresource URLs w3c/resource-timing#70, by @toddreifsteck.
-
Initiator is not well defined w3c/resource-timing#69, by @yoavweiss.
-
-
4 issues received 10 new comments.
-
Server pushed resources in ResourceTiming w3c/resource-timing#53 (7 comments by @DanielBaulig, @igrigorik, @MattMenke2, @n8schloss, @yoavweiss)
-
w3c/charter-webperf
-
7 issues opened.
-
Expose Memory Pressure API? w3c/charter-webperf#33, by @igrigorik.
-
Expose First Paint, First Contentful Paint, ... to developers w3c/charter-webperf#32, by @igrigorik.
-
Surface blocked scroll events in Performance Timeline? w3c/charter-webperf#31, by @igrigorik.
-
Element Timing API: added to DOM, painted, ... w3c/charter-webperf#30, by @igrigorik.
-
Could we expose browser crashes to developers? w3c/charter-webperf#29, by @igrigorik.
-
Enable developers to create and queue custom PerformanceEntry objects w3c/charter-webperf#28, by @igrigorik.
-
Improve RUM observability and monitoring of single page apps w3c/charter-webperf#27, by @igrigorik.
-
-
4 issues received 35 new comments.
-
Improve RUM observability and monitoring of single page apps w3c/charter-webperf#27 (12 comments by @bluesmoon, @igrigorik, @mjackson, @nicjansma, @paulirish, @philipwalton)
-
Expose First Paint, First Contentful Paint, ... to developers w3c/charter-webperf#32 (11 comments by @igrigorik, @rniwa, @spanicker, @tdresser)
-
Surface blocked scroll events in Performance Timeline? w3c/charter-webperf#31 (11 comments by @bzbarsky, @igrigorik, @rniwa, @tdresser, @yoavweiss)
-
w3c/beacon
-
3 issues opened.
-
Ambiguity on "maximum data size" limit and enforcement w3c/beacon#38, by @igrigorik.
-
Beacon is only exposed to Worker in Microsoft Edge w3c/beacon#37, by @toddreifsteck.
-
Transition Level 1 to CR w3c/beacon#36, by @igrigorik.
-
-
3 issues closed.
-
Beacon is only exposed to Worker in Microsoft Edge w3c/beacon#37.
-
Should sendBeacon support GET? w3c/beacon#22.
-
Allow setting HTTP(S) headers in beacon w3c/beacon#30.
-
-
6 issues received 14 new comments.
-
Ambiguity on "maximum data size" limit and enforcement w3c/beacon#38 (4 comments by @igrigorik, @toddreifsteck)
-
Beacon is only exposed to Worker in Microsoft Edge w3c/beacon#37 (4 comments by @annevk, @bzbarsky, @igrigorik)
-
-
1 pull request closed.
-
Add method to sendBeacon w3c/beacon#27.
-
-
1 pull request received 2 new comments.
w3c/requestidlecallback
-
2 issues opened.
-
Allow requesting a minimum time budget w3c/requestidlecallback#49, by @cramforce.
-
Transition Level 1 to CR w3c/requestidlecallback#48, by @igrigorik.
-
-
1 issue received 3 new comments.
-
Allow requesting a minimum time budget w3c/requestidlecallback#49 (3 comments by @cramforce, @igrigorik)
-
w3c/user-timing
-
2 issues opened.
-
Worker tests for User Timing w3c/user-timing#20, by @igrigorik.
-
Transition Level 2 to CR w3c/user-timing#19, by @igrigorik.
-
-
1 issue received 7 new comments.
w3c/performance-timeline
-
1 issue opened.
-
Transition Level 2 to CR w3c/performance-timeline#62, by @igrigorik.
-
-
1 issue received 8 new comments.
-
Transition Level 2 to CR w3c/performance-timeline#62 (8 comments by @igrigorik, @plehegar, @toddreifsteck)
-
w3c/navigation-timing
-
1 issue opened.
-
Transition Level 2 to CR w3c/navigation-timing#49, by @igrigorik.
-
-
1 issue closed.
-
Pl include firstPaint time in navigation timings w3c/navigation-timing#45.
-
-
1 issue received 1 new comment.
TR publications
-
3 documents published.
-
Performance Timeline Level 2 published 3 times as a Working Draft. History of Performance Timeline Level 2
-
Participants
-
3 organizations joined.
-
HTML5 Converged Technology Forum joined.
-
X joined.
-
Meta joined.
-
GitHub
w3c/hr-time
-
1 issue received 1 new comment.
w3c/resource-timing
-
2 issues closed.
-
Confusion around allowed `Timing-Allow-Origin` values w3c/resource-timing#62.
-
Clarify presence of requests that don't return a response w3c/resource-timing#12.
-
-
3 issues received 23 new comments.
-
Clarify definition of responseStart w3c/resource-timing#63 (14 comments by @bluesmoon, @igrigorik, @MattMenke2, @mcmanus)
-
Confusion around allowed `Timing-Allow-Origin` values w3c/resource-timing#62 (8 comments by @igrigorik, @nolanlawson, @toddreifsteck, @yoavweiss)
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (1 comment by @igrigorik)
-
-
1 pull request opened.
-
Change TAO to support comma separated field values w3c/resource-timing#68, by @igrigorik.
-
-
2 pull requests merged.
-
Change TAO to support comma separated field values w3c/resource-timing#68.
-
Define failure scenario timing resolution for same origin and T… w3c/resource-timing#67.
-
-
2 pull requests received 12 new comments.
-
Change TAO to support comma separated field values w3c/resource-timing#68 (9 comments by @annevk, @igrigorik, @toddreifsteck)
-
Define failure scenario timing resolution for same origin and T… w3c/resource-timing#67 (3 comments by @igrigorik, @wesleyhales)
-
w3c/performance-timeline
-
2 issues opened.
-
getEntries(<filter>) isn't supported w3c/performance-timeline#60, by @plehegar.
-
performance.getEntries() can't get failed requests. w3c/performance-timeline#59, by @Handsome2734.
-
-
3 issues closed.
-
getEntries(<filter>) isn't supported w3c/performance-timeline#60.
-
getEntriesByName and friends should explain if they're case sensitive or not w3c/performance-timeline#57.
-
performance.getEntries() can't get failed requests. w3c/performance-timeline#59.
-
-
2 issues received 15 new comments.
-
getEntriesByName and friends should explain if they're case sensitive or not w3c/performance-timeline#57 (14 comments by @igrigorik, @plehegar, @RByers, @toddreifsteck, @yoavweiss)
-
performance.getEntries() can't get failed requests. w3c/performance-timeline#59 (1 comment by @igrigorik)
-
-
2 pull requests opened.
-
remove PerformanceEntryFilterOptions w3c/performance-timeline#61, by @igrigorik.
-
Case sensitivity for getEntries w3c/performance-timeline#58, by @plehegar.
-
-
2 pull requests merged.
-
remove PerformanceEntryFilterOptions w3c/performance-timeline#61.
-
Case sensitivity for getEntries w3c/performance-timeline#58.
-
-
2 pull requests received 12 new comments.
-
Case sensitivity for getEntries w3c/performance-timeline#58 (7 comments by @igrigorik, @plehegar, @yoavweiss)
-
remove PerformanceEntryFilterOptions w3c/performance-timeline#61 (5 comments by @igrigorik, @plehegar, @toddreifsteck)
-
w3c/longtasks
-
1 issue opened.
-
Demo is locked to Google employees? w3c/longtasks#3, by @nolanlawson.
-
-
1 issue received 1 new comment.
w3c/user-timing
-
1 issue closed.
-
SYNTAX_ERR exception for markName argument w3c/user-timing#1.
-
-
2 issues received 14 new comments.
-
Declarative marks w3c/user-timing#17 (12 comments by @bluesmoon, @bmaurer, @csharrison, @eliperelman, @igrigorik, @spanicker, @yoavweiss)
-
SYNTAX_ERR exception for markName argument w3c/user-timing#1 (2 comments by @igrigorik, @toddreifsteck)
-
-
1 pull request opened.
-
clarify conditions for SYNTAX_ERR w3c/user-timing#18, by @igrigorik.
-
-
1 pull request merged.
-
clarify conditions for SYNTAX_ERR w3c/user-timing#18.
-
-
1 pull request received 2 new comments.
w3c/navigation-timing
-
3 issues received 4 new comments.
-
Pl include firstPaint time in navigation timings w3c/navigation-timing#45 (2 comments by @spanicker, @yoavweiss)
-
Relationship between performance.timing.navigationStart and hr-time time origin w3c/navigation-timing#43 (1 comment by @igrigorik)
-
Processing Model chart is missing domLoading marker w3c/navigation-timing#44 (1 comment by @igrigorik)
-
w3c/paint-timing
-
1 pull request opened.
-
Add link to Why First Paint w3c/paint-timing#1, by @spanicker.
-
-
1 pull request merged.
-
Add link to Why First Paint w3c/paint-timing#1.
-
w3c/reporting
-
4 issues received 4 new comments.
-
"Process reporting endpoints..." adds 0-ttl client to new endpoint w3c/reporting#15 (1 comment by @juliatuttle)
-
3 pull requests opened.
-
Fix spurious 0-ttl client, rename new in 'Process reporting endpoints'. w3c/reporting#22, by @juliatuttle.
-
Fix superdomain match logic. w3c/reporting#21, by @juliatuttle.
-
Handle 'Remove endpoint' response in 'Send reports' algorithm. w3c/reporting#20, by @juliatuttle.
-
TR publications
-
1 document published.
-
Beacon published as a Working Draft. History of Beacon
-
GitHub
w3c/performance-timeline
-
1 issue opened.
-
getEntriesByName and friends should explain if they're case sensitive or not w3c/performance-timeline#57, by @esprehn.
-
w3c/resource-timing
-
3 issues opened.
-
Review web-platform tests w3c/resource-timing#66, by @igrigorik.
-
Resource timing for audio w3c/resource-timing#65, by @apals.
-
HEIST w3c/resource-timing#64, by @igrigorik.
-
-
2 issues closed.
-
HEIST w3c/resource-timing#64.
-
Resource timing for audio w3c/resource-timing#65.
-
-
6 issues received 85 new comments.
-
HEIST w3c/resource-timing#64 (74 comments by @annevk, @danaucoin, @domenic, @igrigorik, @jakearchibald, @mikewest, @sleevi, @tomvangoethem, @yoavweiss)
-
For all resources, add timestamp of when it was available to the browser w3c/resource-timing#60 (1 comment by @bmaurer)
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (1 comment by @igrigorik)
-
-
1 pull request opened.
-
Define failure scenario timing resolution for same origin and T… w3c/resource-timing#67, by @wesleyhales.
-
-
1 pull request received 21 new comments.
-
Define failure scenario timing resolution for same origin and T… w3c/resource-timing#67 (21 comments by @annevk, @igrigorik, @plehegar, @toddreifsteck, @wesleyhales)
-
w3c/beacon
-
1 issue opened.
-
Set the keep-alive flag in the fetch sendBeacon performs w3c/beacon#35, by @domenic.
-
-
1 issue closed.
-
Set the keep-alive flag in the fetch sendBeacon performs w3c/beacon#35.
-
-
1 pull request merged.
-
switch to whitelist for corsMode w3c/beacon#34.
-
-
2 pull requests received 15 new comments.
w3c/requestidlecallback
-
1 issue opened.
-
1 issue received 4 new comments.
-
It is unclear what IdleDeadline.timeRemaining() should return if JS keeps the IdleDealing object alive even after the callback call. w3c/requestidlecallback#47 (4 comments by @bzbarsky, @rmcilroy, @smaug----, @toddreifsteck)
-
w3c/hr-time
-
1 issue closed.
-
1 issue received 1 new comment.
-
Security consequences of measuring time of operations on cross-origin data w3c/hr-time#28 (1 comment by @igrigorik)
-
-
1 pull request received 14 new comments.
-
Mechanism to translate timestamps between globals w3c/hr-time#29 (14 comments by @bmaurer, @igrigorik, @plehegar, @toddreifsteck)
-
w3c/longtasks
-
1 issue opened.
-
Tracking microtasks? w3c/longtasks#2, by @nolanlawson.
-
-
1 issue received 5 new comments.
w3c/reporting
-
9 issues opened.
-
Privacy concerns with blacklist/whitelist w3c/reporting#19, by @hillbrad.
-
Allow origins to provide input into report scheduling w3c/reporting#18, by @juliatuttle.
-
"Remove endpoint" is not handled when sending reports w3c/reporting#17, by @juliatuttle.
-
Superdomain match logic is backwards w3c/reporting#16, by @juliatuttle.
-
"Process reporting endpoints..." adds 0-ttl client to new endpoint w3c/reporting#15, by @juliatuttle.
-
Specify better data structures w3c/reporting#14, by @juliatuttle.
-
Don't name variables in the spec _new_ w3c/reporting#13, by @juliatuttle.
-
Clarify input to HTTP-JFV in "Parse reporting endpoint tuples from _value_" w3c/reporting#12, by @juliatuttle.
-
Clarify behavior around "send reports" with active delivery attempts w3c/reporting#11, by @juliatuttle.
-
-
1 issue closed.
-
Privacy concerns with blacklist/whitelist w3c/reporting#19.
-
-
2 issues received 5 new comments.
-
Clarify behavior around "send reports" with active delivery attempts w3c/reporting#11 (1 comment by @juliatuttle)
w3c/user-timing
-
1 issue received 2 new comments.
w3c/navigation-timing
-
1 issue opened.
-
Processing Model is confusing in respect of startTime and beforeunload w3c/navigation-timing#48, by @ahest.
-
-
1 issue received 8 new comments.
-
Pl include firstPaint time in navigation timings w3c/navigation-timing#45 (8 comments by @andydavies, @bluesmoon, @igrigorik, @pmeenan, @spanicker)
-
Lifecycle
-
1 charter started.
-
Chartered until 31 May 2018.
-
TR publications
-
6 documents published.
-
Resource Timing Level 1 published as a Candidate Recommendation Snapshot. History of Resource Timing Level 1
-
High Resolution Time Level 2 published twice as a Working Draft. History of High Resolution Time Level 2
-
Preload published as a Working Draft. History of Preload
-
Frame Timing published as a Note. History of Frame Timing
-
Network Error Logging published as a Note. History of Network Error Logging
-
GitHub
w3c/resource-timing
-
2 issues opened.
-
Clarify definition of responseStart w3c/resource-timing#63, by @igrigorik.
-
Confusion around allowed `Timing-Allow-Origin` values w3c/resource-timing#62, by @igrigorik.
-
-
3 issues received 34 new comments.
-
Confusion around allowed `Timing-Allow-Origin` values w3c/resource-timing#62 (29 comments by @annevk, @igrigorik, @nolanlawson, @reschke, @toddreifsteck, @valenting, @yoavweiss)
-
Clarify definition of responseStart w3c/resource-timing#63 (4 comments by @annevk, @igrigorik, @toddreifsteck)
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (1 comment by @wesleyhales)
-
w3c/hr-time
-
3 issues received 9 new comments.
-
Translating high resolution timestamps between globals w3c/hr-time#22 (7 comments by @igrigorik, @sicking, @toddreifsteck)
-
Security consequences of measuring time of operations on cross-origin data w3c/hr-time#28 (1 comment by @igrigorik)
-
-
2 pull requests opened.
-
Security consequences of exposing time measurement w3c/hr-time#30, by @igrigorik.
-
Mechanism to translate timestamps between globals w3c/hr-time#29, by @igrigorik.
-
-
1 pull request merged.
-
Security consequences of exposing time measurement w3c/hr-time#30.
-
-
2 pull requests received 14 new comments.
-
Mechanism to translate timestamps between globals w3c/hr-time#29 (8 comments by @igrigorik, @sicking, @toddreifsteck)
-
Security consequences of exposing time measurement w3c/hr-time#30 (6 comments by @igrigorik, @martinthomson, @toddreifsteck)
-
w3c/beacon
-
1 issue closed.
-
CO Redirect in the face of CORs may not be correct in specs w3c/beacon#32.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
switch to whitelist for corsMode w3c/beacon#34, by @igrigorik.
-
-
2 pull requests received 35 new comments.
-
switch to whitelist for corsMode w3c/beacon#34 (33 comments by @annevk, @igrigorik, @toddreifsteck, @tyoshino)
-
w3c/longtasks
-
1 issue opened.
-
Why is it called "name" instead of "url"? w3c/longtasks#1, by @domenic.
-
-
1 issue closed.
-
Why is it called "name" instead of "url"? w3c/longtasks#1.
-
-
1 issue received 2 new comments.
w3c/reporting
-
1 pull request opened.
-
Indentation fixes w3c/reporting#10, by @yoavweiss.
-
-
1 pull request received 1 new comment.
w3c/navigation-timing
-
1 issue opened.
-
enum values should be hyphenated w3c/navigation-timing#47, by @dontcallmedom.
-
-
1 issue received 1 new comment.
TR publications
-
3 documents published.
-
Beacon published as a Working Draft. History of Beacon
-
Page Visibility 2 published as a First Public Working Draft. History of Page Visibility 2
-
Reporting API 1 published as a Note. History of Reporting API 1
-
Participants
-
1 participant joined.
-
Wesley Hales (W3C Invited Experts) joined.
-
GitHub
w3c/beacon
-
1 issue opened.
-
CO Redirect in the face of CORs may not be correct in specs w3c/beacon#32, by @toddreifsteck.
-
-
3 issues received 13 new comments.
-
CO Redirect in the face of CORs may not be correct in specs w3c/beacon#32 (9 comments by @annevk, @igrigorik, @toddreifsteck)
-
Privacy concern caused by unspecified delay of requests w3c/beacon#31 (2 comments by @kinu, @Rob--W)
-
-
1 pull request opened.
-
Set request's cors mode based on payload's object type w3c/beacon#33, by @igrigorik.
-
-
1 pull request merged.
-
Set request's cors mode based on payload's object type w3c/beacon#33.
-
-
1 pull request received 5 new comments.
-
Set request's cors mode based on payload's object type w3c/beacon#33 (5 comments by @annevk, @toddreifsteck)
-
w3c/resource-timing
-
3 issues opened.
-
transferSize and TAO redirects w3c/resource-timing#61, by @yoavweiss.
-
For all resources, add timestamp of when it was available to the browser w3c/resource-timing#60, by @bluesmoon.
-
Behaviour with regards to caching w3c/resource-timing#59, by @Krinkle.
-
-
4 issues closed.
-
Behaviour with regards to caching w3c/resource-timing#59.
-
Provide a way to get current buffer size? w3c/resource-timing#48.
-
Contribute tests for resource timing w3c/resource-timing#46.
-
Distinguish "Not-Allowed" from zero value entries w3c/resource-timing#42.
-
-
10 issues received 22 new comments.
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (5 comments by @annevk, @igrigorik, @toddreifsteck, @wesleyhales)
-
Behaviour with regards to caching w3c/resource-timing#59 (4 comments by @igrigorik, @Krinkle, @yoavweiss)
-
Is it well defined when the "add a PerformanceResourceTiming entry" algorithm should run? w3c/resource-timing#55 (3 comments by @CTJyeh, @igrigorik)
-
For all resources, add timestamp of when it was available to the browser w3c/resource-timing#60 (2 comments by @bluesmoon, @igrigorik)
-
initiatorType definition doesn't define initiator in multiple element scenarios w3c/resource-timing#54 (1 comment by @igrigorik)
-
-
1 pull request received 1 new comment.
-
Surface failed fetches in the performance timeline w3c/resource-timing#19 (1 comment by @Safinssssss)
-
w3c/hr-time
-
1 issue opened.
-
1 issue closed.
-
3 issues received 15 new comments.
-
Translating high resolution timestamps between globals w3c/hr-time#22 (12 comments by @igrigorik, @martinthomson, @sicking, @toddreifsteck)
-
Discussion of privacy issue mitigations for possible transferal of timestamps across contexts w3c/hr-time#26 (1 comment by @igrigorik)
-
w3c/navigation-timing
-
3 issues received 3 new comments.
-
It is not defined what "The PerformanceNavigationTiming interface participates in the [PERFORMANCE-TIMELINE-2] " means w3c/navigation-timing#46 (1 comment by @igrigorik)
-
w3c/performance-timeline
-
3 issues opened.
-
Ability to observers past set of performance entries w3c/performance-timeline#56, by @plehegar.
-
Very noticeable delay when loading the "Latest editor's draft" (github.io version) w3c/performance-timeline#55, by @JonasNo.
-
Link to performance observer interface is incorrect w3c/performance-timeline#54, by @JonasNo.
-
-
2 issues closed.
-
Link to performance observer interface is incorrect w3c/performance-timeline#54.
-
Very noticeable delay when loading the "Latest editor's draft" (github.io version) w3c/performance-timeline#55.
-
-
3 issues received 7 new comments.
-
Link to performance observer interface is incorrect w3c/performance-timeline#54 (3 comments by @igrigorik, @JonasNo, @plehegar)
-
Ability to observers past set of performance entries w3c/performance-timeline#56 (2 comments by @igrigorik, @plehegar)
-
Very noticeable delay when loading the "Latest editor's draft" (github.io version) w3c/performance-timeline#55 (2 comments by @igrigorik, @plehegar)
-
w3c/user-timing
-
1 issue opened.
-
Declarative marks w3c/user-timing#17, by @igrigorik.
-
-
1 issue received 4 new comments.
w3c/requestidlecallback
-
1 issue opened.
-
implementations should be allowed to consider work beyond "other event loops" w3c/requestidlecallback#46, by @dbaron.
-
-
2 issues received 4 new comments.
-
implementations should be allowed to consider work beyond "other event loops" w3c/requestidlecallback#46 (3 comments by @igrigorik, @plehegar, @rmcilroy)
-
w3c/web-performance
-
1 issue closed.
-
Need to inline the CSS in the HTML w3c/web-performance#8.
-
-
1 issue received 1 new comment.
-
7 pull requests opened.
-
Added time for F2F w3c/web-performance#16, by @yoavweiss.
-
Update arrangements.md w3c/web-performance#15, by @shubhie.
-
Adding myself w3c/web-performance#14, by @nicjansma.
-
Added Patrick Meenan w3c/web-performance#13, by @pmeenan.
-
Added Akamai participants w3c/web-performance#12, by @yoavweiss.
-
Add myself to the attendee list. w3c/web-performance#11, by @rniwa.
-
Add Wesley w3c/web-performance#10, by @yoavweiss.
-
-
6 pull requests merged.
-
Added time for F2F w3c/web-performance#16.
-
Update arrangements.md w3c/web-performance#15.
-
Adding myself w3c/web-performance#14.
-
Added Akamai participants w3c/web-performance#12.
-
Add Wesley w3c/web-performance#10.
-
Add myself to the attendee list. w3c/web-performance#11.
-
-
1 pull request closed.
-
Added Patrick Meenan w3c/web-performance#13.
-
-
5 pull requests received 8 new comments.
w3c/perf-security-privacy
-
2 issues received 2 new comments.
-
1 pull request merged.
-
a few editorial fixes w3c/perf-security-privacy#4.
-
-
1 pull request received 1 new comment.
TR publications
-
7 documents published.
-
Resource Hints published twice as a Working Draft. History of Resource Hints
-
Cooperative Scheduling of Background Tasks published as a Working Draft. History of Cooperative Scheduling of Background Tasks
-
Preload published as a Working Draft. History of Preload
-
Network Error Logging published as a Note. History of Network Error Logging
-
Frame Timing published as a Note. History of Frame Timing
-
Server Timing published as a Note. History of Server Timing
-
Participants
-
1 organization joined.
-
Tencent joined.
-
GitHub
w3c/resource-timing
-
5 issues opened.
-
ResourceTiming and preconnect w3c/resource-timing#58, by @yoavweiss.
-
startTime is missing from PerformanceResourceTiming entry IDL w3c/resource-timing#56, by @yoavweiss.
-
Is it well defined when the "add a PerformanceResourceTiming entry" algorithm should run? w3c/resource-timing#55, by @yoavweiss.
-
initiatorType definition doesn't define initiator in multiple element scenarios w3c/resource-timing#54, by @yoavweiss.
-
Server pushed resources in ResourceTiming w3c/resource-timing#53, by @igrigorik.
-
-
1 issue closed.
-
startTime is missing from PerformanceResourceTiming entry IDL w3c/resource-timing#56.
-
-
7 issues received 25 new comments.
-
initiatorType definition doesn't define initiator in multiple element scenarios w3c/resource-timing#54 (8 comments by @igrigorik, @toddreifsteck, @yoavweiss)
-
Is it well defined when the "add a PerformanceResourceTiming entry" algorithm should run? w3c/resource-timing#55 (6 comments by @igrigorik, @plehegar, @yoavweiss)
-
Contribute tests for resource timing w3c/resource-timing#46 (4 comments by @igrigorik, @toddreifsteck, @yoavweiss)
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (3 comments by @igrigorik, @yoavweiss)
-
Server pushed resources in ResourceTiming w3c/resource-timing#53 (2 comments by @igrigorik, @yoavweiss)
-
startTime is missing from PerformanceResourceTiming entry IDL w3c/resource-timing#56 (1 comment by @yoavweiss)
-
-
1 pull request opened.
-
Added startTime to IDL w3c/resource-timing#57, by @yoavweiss.
-
-
1 pull request closed.
-
Added startTime to IDL w3c/resource-timing#57.
-
-
1 pull request received 4 new comments.
w3c/perf-security-privacy
-
3 issues opened.
-
Global reporting opt-out? w3c/perf-security-privacy#3, by @wseltzer.
-
Don't report across network-state changes w3c/perf-security-privacy#2, by @wseltzer.
-
Typos w3c/perf-security-privacy#1, by @noncombatant.
-
-
1 issue closed.
-
Typos w3c/perf-security-privacy#1.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
a few editorial fixes w3c/perf-security-privacy#4, by @wseltzer.
-
w3c/hr-time
-
1 issue opened.
-
Should time-origin and Date.now be related? w3c/hr-time#27, by @toddreifsteck.
-
-
1 issue closed.
-
Make translateTime work with Client objects w3c/hr-time#23.
-
-
3 issues received 8 new comments.
-
Should time-origin and Date.now be related? w3c/hr-time#27 (4 comments by @igrigorik, @toddreifsteck)
-
Translating high resolution timestamps between globals w3c/hr-time#22 (3 comments by @igrigorik, @sicking)
-
-
1 pull request closed.
-
1 pull request received 1 new comment.
-
Define performance.transferable + TransferableDOMHighResTimeStamp interface w3c/hr-time#25 (1 comment by @igrigorik)
-
w3c/user-timing
-
1 pull request opened.
-
Note for how to retrieve recorded metrics w3c/user-timing#16, by @igrigorik.
-
-
1 pull request merged.
-
Note for how to retrieve recorded metrics w3c/user-timing#16.
-
-
1 pull request received 4 new comments.
-
Note for how to retrieve recorded metrics w3c/user-timing#16 (4 comments by @igrigorik, @toddreifsteck)
-
w3c/web-performance
-
1 pull request opened.
-
Added meeting location for June 2016 w3c/web-performance#9, by @yoavweiss.
-
-
1 pull request merged.
-
Added meeting location for June 2016 w3c/web-performance#9.
-
-
1 pull request received 1 new comment.
w3c/requestidlecallback
-
5 issues opened.
-
Use push/pop or append/take-the-first w3c/requestidlecallback#45, by @jyasskin.
-
diagram with frame commit and vsync is inaccurate for some browsers w3c/requestidlecallback#44, by @toddreifsteck.
-
What should occur if requestIdleCallback backs up? w3c/requestidlecallback#43, by @toddreifsteck.
-
When/how could 50 ms chunks of time occur vs. typical frame-based 16 ms? w3c/requestidlecallback#42, by @toddreifsteck.
-
Improve the specification of how requestIdleCallback events are ordered w3c/requestidlecallback#41, by @toddreifsteck.
-
-
1 issue closed.
-
The restriction on when a new idle period can start is rather odd. w3c/requestidlecallback#28.
-
-
4 issues received 6 new comments.
-
The restriction on when a new idle period can start is rather odd. w3c/requestidlecallback#28 (3 comments by @bzbarsky, @igrigorik)
-
When/how could 50 ms chunks of time occur vs. typical frame-based 16 ms? w3c/requestidlecallback#42 (1 comment by @rmcilroy)
-
What should occur if requestIdleCallback backs up? w3c/requestidlecallback#43 (1 comment by @rmcilroy)
-
Improve the specification of how requestIdleCallback events are ordered w3c/requestidlecallback#41 (1 comment by @rmcilroy)
-
w3c/navigation-timing
-
1 issue opened.
-
1 issue reopened.
-
2 issues received 7 new comments.
-
It is not defined what "The PerformanceNavigationTiming interface participates in the [PERFORMANCE-TIMELINE-2] " means w3c/navigation-timing#46 (4 comments by @igrigorik, @plehegar, @smaug----)
-
Relationship between performance.timing.navigationStart and hr-time time origin w3c/navigation-timing#43 (3 comments by @plehegar, @toddreifsteck)
-
w3c/beacon
-
2 issues opened.
-
Privacy concern caused by unspecified delay of requests w3c/beacon#31, by @Rob--W.
-
Allow setting HTTP(S) headers in beacon w3c/beacon#30, by @bhamiltoncx.
-
-
1 issue closed.
-
Privacy concern caused by unspecified delay of requests w3c/beacon#31.
-
-
3 issues received 10 new comments.
-
Privacy concern caused by unspecified delay of requests w3c/beacon#31 (7 comments by @igrigorik, @Rob--W)
-
-
1 pull request received 1 new comment.
w3c/reporting
-
1 issue received 2 new comments.
-
Tie retries to user browsing behavior for better privacy? w3c/reporting#4 (2 comments by @cbentzel, @igrigorik)
-
TR publications
-
9 documents published.
-
Preload published as a Working Draft. History of Preload
-
Cooperative Scheduling of Background Tasks published twice as a Working Draft. History of Cooperative Scheduling of Background Tasks
-
Resource Timing Level 1 published 3 times as a Working Draft. History of Resource Timing Level 1
-
Navigation Timing Level 2 published as a Working Draft. History of Navigation Timing Level 2
-
Performance Timeline Level 2 published as a Working Draft. History of Performance Timeline Level 2
-
Reporting API 1 published as a First Public Working Draft. History of Reporting API 1
-
GitHub
w3c/reporting
-
7 issues opened.
-
`age` could become negative w3c/reporting#9, by @estark37.
-
Conflicting advice about switching networks w3c/reporting#8, by @estark37.
-
Handle loops of reports w3c/reporting#5, by @estark37.
-
Tie retries to user browsing behavior for better privacy? w3c/reporting#4, by @estark37.
-
grammar/content nit w3c/reporting#2, by @dret.
-
-
1 issue closed.
-
grammar/content nit w3c/reporting#2.
-
-
2 issues received 4 new comments.
-
Tie retries to user browsing behavior for better privacy? w3c/reporting#4 (2 comments by @adrifelt, @estark37)
-
-
1 pull request opened.
-
proposed fix for #2 w3c/reporting#3, by @dret.
-
-
1 pull request merged.
-
proposed fix for #2 w3c/reporting#3.
-
-
1 pull request received 1 new comment.
w3c/requestidlecallback
-
3 issues closed.
-
It's odd to half-define inter-document callback ordering, but not fully define it w3c/requestidlecallback#29.
-
"the Window object's active document" makes no sense w3c/requestidlecallback#25.
-
Clarify meaning of "guarantee" for timeout callback w3c/requestidlecallback#33.
-
-
4 issues received 15 new comments.
-
It's odd to half-define inter-document callback ordering, but not fully define it w3c/requestidlecallback#29 (7 comments by @bzbarsky, @igrigorik, @rmcilroy)
-
"the Window object's active document" makes no sense w3c/requestidlecallback#25 (5 comments by @domenic, @igrigorik, @rmcilroy)
-
idle callbacks should not be scheduled, if layout is dirty w3c/requestidlecallback#37 (2 comments by @aFarkas, @skyostil)
-
Clarify meaning of "guarantee" for timeout callback w3c/requestidlecallback#33 (1 comment by @igrigorik)
-
-
3 pull requests opened.
-
Allow arbitrary inter-document callback ordering w3c/requestidlecallback#40, by @igrigorik.
-
Reword timeout description w3c/requestidlecallback#39, by @igrigorik.
-
associate rIC callbacks with Window w3c/requestidlecallback#38, by @igrigorik.
-
-
3 pull requests merged.
-
Allow arbitrary inter-document callback ordering w3c/requestidlecallback#40.
-
associate rIC callbacks with Window w3c/requestidlecallback#38.
-
Reword timeout description w3c/requestidlecallback#39.
-
-
3 pull requests received 39 new comments.
-
associate rIC callbacks with Window w3c/requestidlecallback#38 (29 comments by @bzbarsky, @domenic, @igrigorik, @rmcilroy)
-
Allow arbitrary inter-document callback ordering w3c/requestidlecallback#40 (7 comments by @bzbarsky, @igrigorik)
-
w3c/performance-timeline
-
1 issue opened.
-
tests for PerformanceObservers w3c/performance-timeline#53, by @plehegar.
-
-
1 issue closed.
-
tests for PerformanceObservers w3c/performance-timeline#53.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Explain why PerfObserver in the introduction w3c/performance-timeline#52, by @igrigorik.
-
-
1 pull request merged.
-
Explain why PerfObserver in the introduction w3c/performance-timeline#52.
-
-
1 pull request received 1 new comment.
w3c/resource-timing
-
1 issue opened.
-
Resource sizes should be restricted to CORS or same origin w3c/resource-timing#52, by @esprehn.
-
-
1 issue closed.
-
Resource sizes should be restricted to CORS or same origin w3c/resource-timing#52.
-
-
5 issues received 15 new comments.
-
Clarify presence of requests that don't return a response w3c/resource-timing#12 (7 comments by @annevk, @toddreifsteck, @wesleyhales)
-
Distinguish "Not-Allowed" from zero value entries w3c/resource-timing#42 (5 comments by @igrigorik, @yoavweiss)
-
Resource sizes should be restricted to CORS or same origin w3c/resource-timing#52 (1 comment by @igrigorik)
-
-
1 pull request merged.
-
Continuous idl w3c/resource-timing#51.
-
-
1 pull request received 2 new comments.
w3c/navigation-timing
-
3 issues opened.
-
Pl include firstPaint time in navigation timings w3c/navigation-timing#45, by @gopalmor.
-
Processing Model chart is missing domLoading marker w3c/navigation-timing#44, by @andydavies.
-
Relationship between performance.timing.navigationStart and hr-time time origin w3c/navigation-timing#43, by @majido.
-
-
1 issue received 1 new comment.
-
Relationship between performance.timing.navigationStart and hr-time time origin w3c/navigation-timing#43 (1 comment by @igrigorik)
-
-
1 pull request merged.
-
Use continuous IDL. Cleanup prerender further. w3c/navigation-timing#41.
-
-
1 pull request received 1 new comment.
w3c/beacon
-
1 issue opened.
-
Need to add tests for sendBeacon w3c/beacon#29, by @toddreifsteck.
-
-
1 issue received 6 new comments.
-
1 pull request received 2 new comments.
TR publications
-
2 documents published.
-
Preload published twice as a Working Draft. History of Preload
-
GitHub
w3c/resource-timing
-
3 issues received 6 new comments.
-
Distinguish "Not-Allowed" from zero value entries w3c/resource-timing#42 (3 comments by @igrigorik, @yoavweiss)
-
-
1 pull request received 5 new comments.
w3c/requestidlecallback
-
2 issues opened.
-
idle callbacks should not be scheduled, if layout is dirty w3c/requestidlecallback#37, by @aFarkas.
-
Integration with IntersectionObserver w3c/requestidlecallback#36, by @igrigorik.
-
-
1 issue closed.
-
idle callbacks should not be scheduled, if layout is dirty w3c/requestidlecallback#37.
-
-
1 issue received 8 new comments.
-
idle callbacks should not be scheduled, if layout is dirty w3c/requestidlecallback#37 (8 comments by @aFarkas, @igrigorik, @rmcilroy, @skyostil)
-
w3c/server-timing
-
1 issue opened.
-
Allow user to get timing information for when a metric was received w3c/server-timing#4, by @bmaurer.
-
-
1 issue received 2 new comments.
-
Allow user to get timing information for when a metric was received w3c/server-timing#4 (2 comments by @bmaurer, @sroussey)
-
w3c/beacon
-
1 pull request received 17 new comments.
-
Add method to sendBeacon w3c/beacon#27 (17 comments by @annevk, @domenic, @igrigorik, @toddreifsteck)
-
TR publications
-
31 documents published.
-
Beacon published 6 times as a Working Draft. History of Beacon
-
Cooperative Scheduling of Background Tasks published twice as a Working Draft. History of Cooperative Scheduling of Background Tasks
-
Frame Timing published as a Working Draft. History of Frame Timing
-
High Resolution Time Level 2 published 4 times 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
-
Network Error Logging published twice as a Working Draft. History of Network Error Logging
-
Performance Timeline Level 2 published as a Working Draft. History of Performance Timeline Level 2
-
Preload published 7 times as a Working Draft. History of Preload
-
Resource Hints published 4 times as a Working Draft. History of Resource Hints
-
Resource Timing published twice as a Working Draft. History of Resource Timing
-
Participants
-
1 participant joined.
-
Nick Doty (W3C Invited Experts) joined.
-
GitHub
w3c/resource-timing
-
1 issue opened.
-
Return value for domainLookupStart if same origin w3c/resource-timing#50, by @plehegar.
-
-
1 issue closed.
-
Return value for domainLookupStart if same origin w3c/resource-timing#50.
-
-
2 issues received 3 new comments.
-
Contribute tests for resource timing w3c/resource-timing#46 (2 comments by @igrigorik, @toddreifsteck)
-
-
1 pull request opened.
-
Continuous idl w3c/resource-timing#51, by @plehegar.
-
w3c/navigation-timing
-
1 issue received 2 new comments.
-
Contribute tests for navigation timing w3c/navigation-timing#39 (2 comments by @igrigorik, @toddreifsteck)
-
-
2 pull requests opened.
-
Please, ignore this w3c/navigation-timing#42, by @plehegar.
-
Use continuous IDL. Cleanup prerender further. w3c/navigation-timing#41, by @plehegar.
-
-
1 pull request closed.
-
Please, ignore this w3c/navigation-timing#42.
-
-
2 pull requests received 4 new comments.
-
Use continuous IDL. Cleanup prerender further. w3c/navigation-timing#41 (3 comments by @plehegar, @toddreifsteck)
-
w3c/beacon
-
2 issues closed.
-
privacy considerations w3c/beacon#17.
-
normativity of language in Privacy and Security section w3c/beacon#25.
-
-
2 issues received 3 new comments.
-
3 pull requests opened.
-
Fix a typo w3c/beacon#28, by @prayagverma.
-
Add method to sendBeacon w3c/beacon#27, by @toddreifsteck.
-
Privacy + security cleanup w3c/beacon#26, by @igrigorik.
-
-
2 pull requests merged.
-
Fix a typo w3c/beacon#28.
-
Privacy + security cleanup w3c/beacon#26.
-
-
3 pull requests received 33 new comments.
-
Add method to sendBeacon w3c/beacon#27 (27 comments by @annevk, @DigiTec, @igrigorik, @plehegar, @toddreifsteck, @travisleithead)
-
Privacy + security cleanup w3c/beacon#26 (5 comments by @igrigorik, @npdoty, @plehegar, @toddreifsteck)
-
w3c/hr-time
-
2 issues opened.
-
Warning against differentiation w3c/hr-time#24, by @plehegar.
-
1 issue closed.
-
Warning against differentiation w3c/hr-time#24.
-
-
2 issues received 14 new comments.
-
Discussion of privacy issue mitigations for possible transferal of timestamps across contexts w3c/hr-time#26 (7 comments by @igrigorik, @sicking, @toddreifsteck)
-
Warning against differentiation w3c/hr-time#24 (7 comments by @eliperelman, @igrigorik, @plehegar, @yoavweiss)
-
-
1 pull request opened.
-
1 pull request received 5 new comments.
-
Define performance.transferable + TransferableDOMHighResTimeStamp interface w3c/hr-time#25 (5 comments by @igrigorik, @toddreifsteck)
-
w3c/reporting
-
1 pull request opened.
-
fixing typos w3c/reporting#1, by @dret.
-
-
1 pull request merged.
-
fixing typos w3c/reporting#1.
-
-
1 pull request received 1 new comment.
TR publications
-
10 documents published.
-
Preload published 7 times as a Working Draft. History of Preload
-
Resource Hints published as a Working Draft. History of Resource Hints
-
Beacon published as a Working Draft. History of Beacon
-
Resource Timing published as a Working Draft. History of Resource Timing
-
GitHub
w3c/beacon
-
2 issues opened.
-
normativity of language in Privacy and Security section w3c/beacon#25, by @npdoty.
-
Should sendBeacon support GET? w3c/beacon#22, by @toddreifsteck.
-
-
4 issues closed.
-
Is "ensuring" correct? w3c/beacon#21.
-
Clarify interaction with CORS (preflight requests) w3c/beacon#10.
-
security considerations and CORS w3c/beacon#16.
-
Skip body processing w3c/beacon#15.
-
-
6 issues received 32 new comments.
-
Clarify interaction with CORS (preflight requests) w3c/beacon#10 (6 comments by @annevk, @igrigorik, @yoavweiss)
-
Should sendBeacon support GET? w3c/beacon#22 (5 comments by @annevk, @igrigorik, @sicking, @toddreifsteck, @yoavweiss)
-
2 pull requests opened.
-
Without trailing slash you get http w3c/beacon#24, by @annevk.
-
Cleanup processing and security & privacy w3c/beacon#23, by @igrigorik.
-
-
2 pull requests merged.
-
Cleanup processing and security & privacy w3c/beacon#23.
-
Without trailing slash you get http w3c/beacon#24.
-
-
2 pull requests received 5 new comments.
-
Cleanup processing and security & privacy w3c/beacon#23 (4 comments by @annevk, @igrigorik, @toddreifsteck)
-
w3c/hr-time
-
4 issues received 17 new comments.
-
Translating high resolution timestamps between globals w3c/hr-time#22 (10 comments by @bzbarsky, @igrigorik, @toddreifsteck)
-
Should time origin be defined in terms of a monotonic clock? w3c/hr-time#21 (2 comments by @bzbarsky, @igrigorik)
-