- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 12 Feb 2019 17:00:58 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1gtbQY-0005KU-RY@uranus.w3.org>
Issues
------
* w3c/performance-timeline (+0/-0/💬2)
2 issues received 2 new comments:
- #81 Define buffering behaviors & hooks for queued (PerformanceObserver) entries (1 by npm1)
https://github.com/w3c/performance-timeline/issues/81 [enhancement]
- #100 Ensure tests are clean (1 by npm1)
https://github.com/w3c/performance-timeline/issues/100
* w3c/resource-timing (+1/-1/💬10)
1 issues created:
- Timing-Allow-Origin check should be case-insensitive (by npm1)
https://github.com/w3c/resource-timing/issues/202
6 issues received 10 new comments:
- #202 Timing-Allow-Origin check should be case-insensitive (4 by annevk, yoavweiss)
https://github.com/w3c/resource-timing/issues/202
- #137 Proposal: API for exposing resource requests (2 by igrigorik, nicjansma)
https://github.com/w3c/resource-timing/issues/137
- #195 The spec uses the wrong Origin definition, and missing a note regarding TAO redirects (1 by yoavweiss)
https://github.com/w3c/resource-timing/issues/195
- #71 Transition Level 2 to CR (1 by yoavweiss)
https://github.com/w3c/resource-timing/issues/71 [w3c]
- #173 Clarify cross-origin resources (1 by yoavweiss)
https://github.com/w3c/resource-timing/issues/173 [requires Fetch integration]
- #190 Expose JavaScript code caching information in PerformanceResourceTiming (1 by arturjanc)
https://github.com/w3c/resource-timing/issues/190 [enhancement] [whiteboard]
1 issues closed:
- The spec uses the wrong Origin definition, and missing a note regarding TAO redirects https://github.com/w3c/resource-timing/issues/195
* w3c/preload (+1/-0/💬3)
1 issues created:
- Conflicting Link and <link> (by karlcow)
https://github.com/w3c/preload/issues/135
1 issues received 3 new comments:
- #135 Conflicting Link and <link> (3 by karlcow, domfarolino)
https://github.com/w3c/preload/issues/135
* w3c/resource-hints (+0/-1/💬1)
1 issues received 1 new comments:
- #85 Implementing rel="preconnect" (1 by yoavweiss)
https://github.com/w3c/resource-hints/issues/85
1 issues closed:
- Implementing rel="preconnect" https://github.com/w3c/resource-hints/issues/85
* w3c/paint-timing (+1/-0/💬3)
1 issues created:
- surprising (if not understandable) results for first-paint when `document.visibilityState === 'hidden'` (by mikesherov)
https://github.com/w3c/paint-timing/issues/40
1 issues received 3 new comments:
- #40 surprising (if not understandable) results for first-paint when `document.visibilityState === 'hidden'` (3 by mikesherov, tdresser)
https://github.com/w3c/paint-timing/issues/40
Pull requests
-------------
* w3c/resource-timing (+0/-1/💬0)
1 pull requests merged:
- Improve TAO definition
https://github.com/w3c/resource-timing/pull/197
* w3c/requestidlecallback (+2/-0/💬2)
2 pull requests submitted:
- Clarify timeRemaining() algorithm. (by rmcilroy)
https://github.com/w3c/requestidlecallback/pull/79
- Better define deadline (by yoavweiss)
https://github.com/w3c/requestidlecallback/pull/78
2 pull requests received 2 new comments:
- #78 Better define deadline (1 by yoavweiss)
https://github.com/w3c/requestidlecallback/pull/78
- #79 Clarify timeRemaining() algorithm. (1 by rmcilroy)
https://github.com/w3c/requestidlecallback/pull/79
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, 12 February 2019 17:01:01 UTC