- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 23 Oct 2018 17:00:40 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1gF02q-0006Nb-LM@uranus.w3.org>
Issues
------
* w3c/performance-timeline (+0/-0/💬12)
2 issues received 12 new comments:
- #105 PerformanceEntries are affected by backgrounded status (11 by igrigorik, tdresser, gi11es, yoavweiss, Zizzamia, npm1)
https://github.com/w3c/performance-timeline/issues/105
- #81 Define buffering behaviors & hooks for queued (PerformanceObserver) entries (1 by igrigorik)
https://github.com/w3c/performance-timeline/issues/81 [enhancement]
* w3c/resource-timing (+0/-0/💬1)
1 issues received 1 new comments:
- #173 Clarify cross-origin resources (1 by alanwaketan)
https://github.com/w3c/resource-timing/issues/173
* w3c/navigation-timing (+1/-0/💬0)
1 issues created:
- Inconsistent implementations of navigation type in "reload the page through navigation to the same URL" scenario (by jakub-g)
https://github.com/w3c/navigation-timing/issues/87
* w3c/preload (+0/-0/💬2)
2 issues received 2 new comments:
- #121 can the browser place limits on the preload cache? (1 by yoavweiss)
https://github.com/w3c/preload/issues/121
- #118 variable fonts (1 by yoavweiss)
https://github.com/w3c/preload/issues/118 [external-dependency]
* w3c/resource-hints (+0/-1/💬3)
1 issues received 3 new comments:
- #82 Prefetch and double-key caching (3 by igrigorik, yoavweiss)
https://github.com/w3c/resource-hints/issues/82 [Prefetch]
1 issues closed:
- Why is prefetching ignoring CSP and allowing connections to 3rd party destinations? https://github.com/w3c/resource-hints/issues/73
* w3c/requestidlecallback (+0/-2/💬4)
4 issues received 4 new comments:
- #72 Spec should allow setting timeRemaining to 0 early (1 by yoavweiss)
https://github.com/w3c/requestidlecallback/issues/72 [triage]
- #73 Should pending idle callbacks in the queue be run when the page is unloaded/backgrounded? (1 by philipwalton)
https://github.com/w3c/requestidlecallback/issues/73 [triage]
- #70 Missing definition for "idle time" (1 by rmcilroy)
https://github.com/w3c/requestidlecallback/issues/70 [bug] [enhancement]
- #71 "deadline" in the "start an idle period algorithm" should be defined in terms of event loop (1 by yoavweiss)
https://github.com/w3c/requestidlecallback/issues/71
2 issues closed:
- Spec should allow setting timeRemaining to 0 early https://github.com/w3c/requestidlecallback/issues/72 [triage]
- Should pending idle callbacks in the queue be run when the page is unloaded/backgrounded? https://github.com/w3c/requestidlecallback/issues/73 [triage]
* w3c/device-memory (+1/-0/💬4)
1 issues created:
- Upper and lower bound should be UA opiniated decision, in entire text. (by GrosSacASac)
https://github.com/w3c/device-memory/issues/23
3 issues received 4 new comments:
- #15 Expose CPU clock speed and GPU info in the same manner as device memory (2 by n8schloss, yoavweiss)
https://github.com/w3c/device-memory/issues/15 [feature request]
- #13 Should device memory be limited to what the UA can access? (1 by yoavweiss)
https://github.com/w3c/device-memory/issues/13
- #23 Upper and lower bound should be UA opiniated decision, in entire text. (1 by GrosSacASac)
https://github.com/w3c/device-memory/issues/23
* w3c/paint-timing (+0/-1/💬6)
2 issues received 6 new comments:
- #26 Eliminate "4.1. Modifications to other specifications" (4 by tdresser, npm1, yoavweiss)
https://github.com/w3c/paint-timing/issues/26
- #31 What is the scope of timings? (2 by npm1, yoavweiss)
https://github.com/w3c/paint-timing/issues/31
1 issues closed:
- Eliminate "4.1. Modifications to other specifications" https://github.com/w3c/paint-timing/issues/26
* w3c/longtasks (+0/-0/💬5)
1 issues received 5 new comments:
- #41 Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? (5 by igrigorik, npm1, philipwalton)
https://github.com/w3c/longtasks/issues/41 [requires-discussion]
* w3c/server-timing (+0/-3/💬3)
3 issues received 3 new comments:
- #56 Server-Timing header and opaque responses (1 by yoavweiss)
https://github.com/w3c/server-timing/issues/56
- #58 Relax (or remove) trailer processing requirement (1 by cvazac)
https://github.com/w3c/server-timing/issues/58
- #54 Limiting sever timing to secure origins (1 by cvazac)
https://github.com/w3c/server-timing/issues/54
3 issues closed:
- Limiting sever timing to secure origins https://github.com/w3c/server-timing/issues/54
- Relax (or remove) trailer processing requirement https://github.com/w3c/server-timing/issues/58
- Server-Timing header and opaque responses https://github.com/w3c/server-timing/issues/56
Pull requests
-------------
* w3c/resource-timing (+0/-0/💬1)
1 pull requests received 1 new comments:
- #168 Fire `resourcetimingbufferfull` asynchronously - alternative approach (1 by igrigorik)
https://github.com/w3c/resource-timing/pull/168
* w3c/requestidlecallback (+2/-1/💬1)
2 pull requests submitted:
- Hook into HTML spec. (by rmcilroy)
https://github.com/w3c/requestidlecallback/pull/75
- Allow UAs to set timeRemaining to zero if a time critical task is pending (by rmcilroy)
https://github.com/w3c/requestidlecallback/pull/74
1 pull requests received 1 new comments:
- #74 Allow UAs to set timeRemaining to zero if a time critical task is pending (1 by rmcilroy)
https://github.com/w3c/requestidlecallback/pull/74
1 pull requests merged:
- Allow UAs to set timeRemaining to zero if a time critical task is pending
https://github.com/w3c/requestidlecallback/pull/74
* w3c/server-timing (+2/-2/💬0)
2 pull requests submitted:
- Trailer processing should be optional (by cvazac)
https://github.com/w3c/server-timing/pull/60
- Specify behavior for user-agents who only support secure contexts (by cvazac)
https://github.com/w3c/server-timing/pull/59
2 pull requests merged:
- Specify behavior for user-agents who only support secure contexts
https://github.com/w3c/server-timing/pull/59
- Trailer processing should be optional
https://github.com/w3c/server-timing/pull/60
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/hr-time
* https://github.com/w3c/performance-timeline
* https://github.com/w3c/resource-timing
* https://github.com/w3c/navigation-timing
* https://github.com/w3c/user-timing
* https://github.com/w3c/beacon
* https://github.com/w3c/page-visibility
* https://github.com/w3c/preload
* https://github.com/w3c/resource-hints
* https://github.com/w3c/requestidlecallback
* https://github.com/w3c/device-memory
* https://github.com/w3c/paint-timing
* https://github.com/w3c/longtasks
* https://github.com/w3c/server-timing
Received on Tuesday, 23 October 2018 17:00:42 UTC