- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 22 Oct 2019 17:01:37 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1iMxXN-0001bQ-NH@uranus.w3.org>
Issues
------
* w3c/hr-time (+0/-1/💬0)
1 issues closed:
- How to cite "timeOrigin" and "now()"? https://github.com/w3c/hr-time/issues/83 [editorial]
* w3c/performance-timeline (+1/-1/💬1)
1 issues created:
- DOMHighResTimeStamp not found in level2 (by npm1)
https://github.com/w3c/performance-timeline/issues/153
1 issues received 1 new comments:
- #153 DOMHighResTimeStamp not found in level2 (1 by npm1)
https://github.com/w3c/performance-timeline/issues/153
1 issues closed:
- DOMHighResTimeStamp not found in level2 https://github.com/w3c/performance-timeline/issues/153
* w3c/resource-timing (+0/-1/💬3)
3 issues received 3 new comments:
- #216 Use "cross-origin-resource-policy: cross-origin" for timing-allow-origin (1 by yutakahirano)
https://github.com/w3c/resource-timing/issues/216
- #210 Cross-origin IFRAME opting-in to sharing ResourceTiming data (1 by thebengeu)
https://github.com/w3c/resource-timing/issues/210
- #199 Handling of 0-RTT interactions (1 by davidben)
https://github.com/w3c/resource-timing/issues/199
1 issues closed:
- Use "cross-origin-resource-policy: cross-origin" for timing-allow-origin https://github.com/w3c/resource-timing/issues/216
* w3c/navigation-timing (+1/-0/💬1)
1 issues created:
- Add a new entry type for navigations from the BFCache (by philipwalton)
https://github.com/w3c/navigation-timing/issues/118
1 issues received 1 new comments:
- #115 Definition of "back_forward" navigation type does not make sense (1 by rniwa)
https://github.com/w3c/navigation-timing/issues/115
* w3c/page-visibility (+0/-0/💬1)
1 issues received 1 new comments:
- #51 Unexpected HTML things to check (1 by toddreifsteck)
https://github.com/w3c/page-visibility/issues/51
* w3c/paint-timing (+1/-0/💬2)
1 issues created:
- The code example incorrectly mentions observing "long tasks" (by philipwalton)
https://github.com/w3c/paint-timing/issues/46
1 issues received 2 new comments:
- #46 The code example incorrectly mentions observing "long tasks" (2 by npm1, yoavweiss)
https://github.com/w3c/paint-timing/issues/46
Pull requests
-------------
* w3c/hr-time (+1/-1/💬1)
1 pull requests submitted:
- chore: xref fixes (by marcoscaceres)
https://github.com/w3c/hr-time/pull/84
1 pull requests received 1 new comments:
- #82 Some minor editorial changes (1 by yoavweiss)
https://github.com/w3c/hr-time/pull/82
1 pull requests merged:
- chore: xref fixes
https://github.com/w3c/hr-time/pull/84
* w3c/performance-timeline (+2/-2/💬2)
2 pull requests submitted:
- Level2: more ReSpec fixes (by npm1)
https://github.com/w3c/performance-timeline/pull/155
- chore: fixup some xrefs (by marcoscaceres)
https://github.com/w3c/performance-timeline/pull/154
1 pull requests received 2 new comments:
- #154 chore: fixup some xrefs (2 by marcoscaceres, npm1)
https://github.com/w3c/performance-timeline/pull/154
2 pull requests merged:
- Level2: more ReSpec fixes
https://github.com/w3c/performance-timeline/pull/155
- chore: fixup some xrefs
https://github.com/w3c/performance-timeline/pull/154
* w3c/paint-timing (+1/-1/💬0)
1 pull requests submitted:
- Editorial: use camelCase for vars (by npm1)
https://github.com/w3c/paint-timing/pull/47
1 pull requests merged:
- Editorial: use camelCase for vars
https://github.com/w3c/paint-timing/pull/47
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, 22 October 2019 17:01:40 UTC