- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 12 Apr 2022 17:00:52 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1neJsq-0004rS-7c@uranus.w3.org>
Issues
------
* w3c/resource-timing (+0/-1/💬17)
5 issues received 17 new comments:
- #303 Reflect preload information (in ResourceTiming?) (12 by andydavies, nicjansma, noamr)
https://github.com/w3c/resource-timing/issues/303 [enhancement]
- #220 Provide a TAO-bypass for Navigation timing (2 by noamr)
https://github.com/w3c/resource-timing/issues/220 [Clarification] [editorial] [requires Fetch integration] [hackathon_15_09_20] [hackathon_2020]
- #204 Add tests for not-same-site nested contexts (1 by noamr)
https://github.com/w3c/resource-timing/issues/204 [test:missing-coverage]
- #142 `InitiatorType` should not single out XHR (1 by noamr)
https://github.com/w3c/resource-timing/issues/142 [Clarification]
- #54 initiatorType definition doesn't define initiator in multiple element scenarios (1 by noamr)
https://github.com/w3c/resource-timing/issues/54 [whiteboard] [Clarification]
1 issues closed:
- Clarify what constitutes a "downloadable resource" https://github.com/w3c/resource-timing/issues/100 [needs tests] [Clarification] [requires Fetch integration]
* w3c/navigation-timing (+0/-7/💬14)
9 issues received 14 new comments:
- #165 Using "connectStart", "secureConnectionStart" and "connectEnd" with HTTP/3 flows (1 by annevk)
https://github.com/w3c/navigation-timing/issues/165
- #163 How should prefetch be exposed? (1 by nicjansma)
https://github.com/w3c/navigation-timing/issues/163
- #160 Using navigationStart as a baseline may expose cross-origin timing information (2 by noamr)
https://github.com/w3c/navigation-timing/issues/160
- #146 A scenario where transferSize is 0 for non cached loads (or may be not) (1 by yoavweiss)
https://github.com/w3c/navigation-timing/issues/146
- #144 Clarify security context for PerformanceNavigationTiming (2 by noamr, yoavweiss)
https://github.com/w3c/navigation-timing/issues/144
- #114 Spec for PerformanceNavigationTiming.type does not match any implementations (2 by noamr, yoavweiss)
https://github.com/w3c/navigation-timing/issues/114 [needs tests] [WPT] [clarification]
- #85 Should navigationEntry's navigationType be updated according to the parent page ? (2 by noamr)
https://github.com/w3c/navigation-timing/issues/85 [test:missing-coverage] [discuss] [WPT] [clarification]
- #83 should unloaded iframes be included in their parent document's unload duration? (2 by noamr, yoavweiss)
https://github.com/w3c/navigation-timing/issues/83 [test:missing-coverage] [discuss] [WPT] [clarification]
- #49 Transition Level 2 to CR (1 by yoavweiss)
https://github.com/w3c/navigation-timing/issues/49 [w3c]
7 issues closed:
- should unloaded iframes be included in their parent document's unload duration? https://github.com/w3c/navigation-timing/issues/83 [test:missing-coverage] [discuss] [WPT] [clarification]
- Should navigationEntry's navigationType be updated according to the parent page ? https://github.com/w3c/navigation-timing/issues/85 [test:missing-coverage] [discuss] [WPT] [clarification]
- Spec for PerformanceNavigationTiming.type does not match any implementations https://github.com/w3c/navigation-timing/issues/114 [needs tests] [WPT] [clarification]
- Clarify security context for PerformanceNavigationTiming https://github.com/w3c/navigation-timing/issues/144
- A scenario where transferSize is 0 for non cached loads (or may be not) https://github.com/w3c/navigation-timing/issues/146
- Using "connectStart", "secureConnectionStart" and "connectEnd" with HTTP/3 flows https://github.com/w3c/navigation-timing/issues/165
- Transition Level 2 to CR https://github.com/w3c/navigation-timing/issues/49 [w3c]
* w3c/preload (+0/-2/💬3)
2 issues received 3 new comments:
- #130 Putting an upper limit on preload/prefetch chains (1 by noamr)
https://github.com/w3c/preload/issues/130 [HTML integration] [prose]
- #129 Preloads triggered by speculative fetches should be speculative (2 by noamr, yoavweiss)
https://github.com/w3c/preload/issues/129 [HTML integration] [prose]
2 issues closed:
- Header preload and CSS / JavaScript https://github.com/w3c/preload/issues/116 [HTML integration] [editorial]
- Preloads triggered by speculative fetches should be speculative https://github.com/w3c/preload/issues/129 [HTML integration] [prose]
* w3c/resource-hints (+0/-1/💬6)
4 issues received 6 new comments:
- #86 Specify processing model in terms of Fetch (1 by yoavweiss)
https://github.com/w3c/resource-hints/issues/86 [definition] [discussion] [Triaged]
- #78 Prefetch vs Service Workers (1 by noamr)
https://github.com/w3c/resource-hints/issues/78 [Prefetch] [Triaged]
- #66 Processing model for `as`? (3 by noamr, yoavweiss)
https://github.com/w3c/resource-hints/issues/66 [Prefetch] [definition] [Triaged]
- #57 If a resource is prefetched, what would `initiatorType` show up as in ResourceTiming entries? (1 by noamr)
https://github.com/w3c/resource-hints/issues/57 [Prefetch] [discussion] [Triaged]
1 issues closed:
- If a resource is prefetched, what would `initiatorType` show up as in ResourceTiming entries? https://github.com/w3c/resource-hints/issues/57 [Prefetch] [discussion] [Triaged]
* w3c/longtasks (+1/-0/💬4)
1 issues created:
- Task duration should be coarsened for each context (by noamr)
https://github.com/w3c/longtasks/issues/98
2 issues received 4 new comments:
- #98 Task duration should be coarsened for each context (2 by noamr, yoavweiss)
https://github.com/w3c/longtasks/issues/98
- #76 Event loop timing reporting seems to ignore reentrancy (2 by noamr, yoavweiss)
https://github.com/w3c/longtasks/issues/76
Pull requests
-------------
* w3c/resource-timing (+3/-2/💬3)
3 pull requests submitted:
- Tidied up document using tidy-html5 (by github-actions)
https://github.com/w3c/resource-timing/pull/325
- Clarify "downloadable" (by noamr)
https://github.com/w3c/resource-timing/pull/324
- Illustrate in diagram that timestamps are not necessarily consecutive (by noamr)
https://github.com/w3c/resource-timing/pull/323
2 pull requests received 3 new comments:
- #325 Tidied up document using tidy-html5 (1 by w3cbot)
https://github.com/w3c/resource-timing/pull/325
- #323 Illustrate in diagram that timestamps are not necessarily consecutive (2 by noamr, yoavweiss)
https://github.com/w3c/resource-timing/pull/323
2 pull requests merged:
- Tidied up document using tidy-html5
https://github.com/w3c/resource-timing/pull/325
- Clarify "downloadable"
https://github.com/w3c/resource-timing/pull/324
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
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 12 April 2022 17:00:54 UTC