- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 29 Sep 2020 17:00:48 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1kNIzg-0003Iy-AN@uranus.w3.org>
Issues
------
* w3c/hr-time (+0/-0/💬1)
1 issues received 1 new comments:
- #96 Comments on "Define 'relative high resolution time'" (1 by annevk)
https://github.com/w3c/hr-time/issues/96
* w3c/resource-timing (+1/-0/💬1)
1 issues created:
- Point "current time" definition to hr-time "current high resolution time" algorithm (by igneel64)
https://github.com/w3c/resource-timing/issues/235
1 issues received 1 new comments:
- #119 spec what requestStart, responseStart, and responseEnd should represent when service worker is involved (1 by yoavweiss)
https://github.com/w3c/resource-timing/issues/119 [Clarification] [needs tests] [requires Fetch integration]
* w3c/page-visibility (+1/-1/💬4)
1 issues created:
- visibilitychange should fire after pagehide (not before) (by sideshowbarker)
https://github.com/w3c/page-visibility/issues/67
2 issues received 4 new comments:
- #67 visibilitychange should fire after pagehide (not before) (1 by sideshowbarker)
https://github.com/w3c/page-visibility/issues/67
- #39 Why does visibilitychange fire after pagehide in the unload flow? (3 by rakina, sideshowbarker)
https://github.com/w3c/page-visibility/issues/39
1 issues closed:
- visibilitychange should fire after pagehide (not before) https://github.com/w3c/page-visibility/issues/67
* w3c/resource-hints (+1/-0/💬0)
1 issues created:
- "prerender" visibility state is not defined (by nhiroki)
https://github.com/w3c/resource-hints/issues/94
Pull requests
-------------
* w3c/hr-time (+0/-0/💬6)
1 pull requests received 6 new comments:
- #93 Limit the timer resolution in non-isolated contexts (6 by annevk, domenic, yoavweiss, yutakahirano)
https://github.com/w3c/hr-time/pull/93 [hackathon_15_09_20]
* w3c/resource-timing (+1/-0/💬0)
1 pull requests submitted:
- Conform 'current time' definition to the current hr-time spec (by igneel64)
https://github.com/w3c/resource-timing/pull/236
* w3c/navigation-timing (+0/-0/💬8)
1 pull requests received 8 new comments:
- #131 workerStart and redirects (8 by nicjansma, npm1, toddreifsteck)
https://github.com/w3c/navigation-timing/pull/131 [hackathon_15_09_20]
* w3c/longtasks (+1/-0/💬0)
1 pull requests submitted:
- Add dfn for event loop and browsing context (by npm1)
https://github.com/w3c/longtasks/pull/86
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, 29 September 2020 17:00:50 UTC