- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 28 May 2019 17:00:55 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1hVfT5-0001oE-JX@uranus.w3.org>
Issues
------
* w3c/performance-timeline (+1/-1/💬2)
1 issues created:
- PerformanceObserver is unable to measure some timing attributes (by SemihGk)
https://github.com/w3c/performance-timeline/issues/131
2 issues received 2 new comments:
- #131 PerformanceObserver is unable to measure some timing attributes (1 by SemihGk)
https://github.com/w3c/performance-timeline/issues/131
- #117 supportedEntryTypes API has some issues (1 by rniwa)
https://github.com/w3c/performance-timeline/issues/117
1 issues closed:
- PerformanceObserver is unable to measure some timing attributes https://github.com/w3c/performance-timeline/issues/131
* w3c/user-timing (+1/-0/💬0)
1 issues created:
- StructuredDeserialize should be used; serialization records cannot be returned from IDL getters (by jeremyroman)
https://github.com/w3c/user-timing/issues/59
Pull requests
-------------
* w3c/performance-timeline (+0/-0/💬2)
1 pull requests received 2 new comments:
- #118 supportedEntryTypes: cache the FrozenArray (2 by rniwa, npm1)
https://github.com/w3c/performance-timeline/pull/118
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, 28 May 2019 17:00:56 UTC