- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 18 Jan 2022 17:00:56 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1n9rqq-00068h-Mu@uranus.w3.org>
Issues
------
* w3c/performance-timeline (+1/-0/💬0)
1 issues created:
- `performance entry buffer` should be exported (by yoavweiss)
https://github.com/w3c/performance-timeline/issues/196
* w3c/resource-timing (+0/-3/💬4)
3 issues received 4 new comments:
- #286 Missing tests following the Fetch integration (1 by noamr)
https://github.com/w3c/resource-timing/issues/286
- #249 "Queue a task to run fire a buffer full event" needs to have a task queue (2 by noamr, yoavweiss)
https://github.com/w3c/resource-timing/issues/249 [fetch-integration]
- #119 spec what requestStart, responseStart, and responseEnd should represent when service worker is involved (1 by noamr)
https://github.com/w3c/resource-timing/issues/119 [needs tests] [Clarification] [requires Fetch integration]
3 issues closed:
- Missing tests following the Fetch integration https://github.com/w3c/resource-timing/issues/286
- Should favicon loading times be exposed to the document? https://github.com/w3c/resource-timing/issues/299
- "Queue a task to run fire a buffer full event" needs to have a task queue https://github.com/w3c/resource-timing/issues/249 [fetch-integration]
* w3c/navigation-timing (+1/-4/💬7)
1 issues created:
- ToT spec has a bunch of respec warnings and errors (by yoavweiss)
https://github.com/w3c/navigation-timing/issues/167
4 issues received 7 new comments:
- #167 ToT spec has a bunch of respec warnings and errors (1 by noamr)
https://github.com/w3c/navigation-timing/issues/167
- #155 Should about:blank have a PerformanceNavigationTiming? (1 by noamr)
https://github.com/w3c/navigation-timing/issues/155
- #101 Load event timings are not well-defined (4 by bzbarsky, noamr)
https://github.com/w3c/navigation-timing/issues/101 [clarification]
- #100 workerStart should be clearly defined as applicable to the last SW (1 by noamr)
https://github.com/w3c/navigation-timing/issues/100 [needs tests] [WPT] [clarification]
4 issues closed:
- workerStart should be clearly defined as applicable to the last SW https://github.com/w3c/navigation-timing/issues/100 [needs tests] [WPT] [clarification]
- Load event timings are not well-defined https://github.com/w3c/navigation-timing/issues/101 [clarification]
- Should about:blank have a PerformanceNavigationTiming? https://github.com/w3c/navigation-timing/issues/155
- ToT spec has a bunch of respec warnings and errors https://github.com/w3c/navigation-timing/issues/167
* w3c/requestidlecallback (+0/-3/💬3)
3 issues received 3 new comments:
- #87 timeRemaining() step 4 should define what it means to have a "time-critical task pending" (1 by noamr)
https://github.com/w3c/requestidlecallback/issues/87 [requires-discussion]
- #86 6.2. invoke idle callbacks algorithm step 1 should be defined in terms of task sources having tasks enqueued (1 by noamr)
https://github.com/w3c/requestidlecallback/issues/86 [requires-discussion]
- #82 The order of idle callbacks across windows is inconsistent between spec & UAs (1 by noamr)
https://github.com/w3c/requestidlecallback/issues/82 [requires-discussion]
3 issues closed:
- The order of idle callbacks across windows is inconsistent between spec & UAs https://github.com/w3c/requestidlecallback/issues/82 [requires-discussion]
- timeRemaining() step 4 should define what it means to have a "time-critical task pending" https://github.com/w3c/requestidlecallback/issues/87 [requires-discussion]
- 6.2. invoke idle callbacks algorithm step 1 should be defined in terms of task sources having tasks enqueued https://github.com/w3c/requestidlecallback/issues/86 [requires-discussion]
Pull requests
-------------
* w3c/hr-time (+2/-2/💬2)
2 pull requests submitted:
- Tidy document using tidy-html5 (by github-actions)
https://github.com/w3c/hr-time/pull/135
- Add a privacy section (by noamr)
https://github.com/w3c/hr-time/pull/134
2 pull requests received 2 new comments:
- #135 Tidy document using tidy-html5 (1 by w3cbot)
https://github.com/w3c/hr-time/pull/135
- #130 Expose everywhere (1 by Ms2ger)
https://github.com/w3c/hr-time/pull/130
2 pull requests merged:
- Tidy document using tidy-html5
https://github.com/w3c/hr-time/pull/135
- Add a privacy section
https://github.com/w3c/hr-time/pull/134
* w3c/performance-timeline (+0/-0/💬1)
1 pull requests received 1 new comments:
- #193 Expose everywhere (1 by Ms2ger)
https://github.com/w3c/performance-timeline/pull/193
* w3c/resource-timing (+5/-6/💬4)
5 pull requests submitted:
- Override spec status for auto-publishing (by yoavweiss)
https://github.com/w3c/resource-timing/pull/315
- Tidied up document using tidy-html5 (by github-actions)
https://github.com/w3c/resource-timing/pull/314
- Tidied up document using tidy-html5 (by github-actions)
https://github.com/w3c/resource-timing/pull/313
- Fix up a missing section (by yoavweiss)
https://github.com/w3c/resource-timing/pull/312
- List all the attributes that will get masked when TAO fails (by tommckee1)
https://github.com/w3c/resource-timing/pull/311
4 pull requests received 4 new comments:
- #315 Override spec status for auto-publishing (1 by caribouW3)
https://github.com/w3c/resource-timing/pull/315
- #314 Tidied up document using tidy-html5 (1 by w3cbot)
https://github.com/w3c/resource-timing/pull/314
- #313 Tidied up document using tidy-html5 (1 by w3cbot)
https://github.com/w3c/resource-timing/pull/313
- #311 List all the attributes that will get masked when TAO fails (1 by yoavweiss)
https://github.com/w3c/resource-timing/pull/311
6 pull requests merged:
- Override spec status for auto-publishing
https://github.com/w3c/resource-timing/pull/315
- Tidied up document using tidy-html5
https://github.com/w3c/resource-timing/pull/314
- List all the attributes that will get masked when TAO fails
https://github.com/w3c/resource-timing/pull/311
- Tidied up document using tidy-html5
https://github.com/w3c/resource-timing/pull/313
- Fix up a missing section
https://github.com/w3c/resource-timing/pull/312
- Clean up unused definitions and other respec errors
https://github.com/w3c/resource-timing/pull/310
* w3c/navigation-timing (+1/-1/💬1)
1 pull requests submitted:
- Fix multiple lint warnings: (by noamr)
https://github.com/w3c/navigation-timing/pull/168
1 pull requests received 1 new comments:
- #168 Fix multiple lint warnings: (1 by noamr)
https://github.com/w3c/navigation-timing/pull/168
1 pull requests merged:
- Fix multiple lint warnings:
https://github.com/w3c/navigation-timing/pull/168
* w3c/requestidlecallback (+1/-1/💬0)
1 pull requests submitted:
- Fix lint warnings (by noamr)
https://github.com/w3c/requestidlecallback/pull/99
1 pull requests merged:
- Fix lint warnings
https://github.com/w3c/requestidlecallback/pull/99
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, 18 January 2022 17:00:59 UTC