- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 25 Jul 2017 17:00:11 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1da3Br-0000F2-IZ@uranus.w3.org>
Issues
------
* w3c/hr-time (+0/-1/💬0)
1 issues closed:
- WebIDL serializer has been deprecated in favor of toJSON operation https://github.com/w3c/hr-time/issues/49
* w3c/performance-timeline (+0/-3/💬3)
3 issues received 3 new comments:
- #81 Define `performance entry buffer` interaction w/ existing buffers (1 by igrigorik)
https://github.com/w3c/performance-timeline/issues/81
- #78 Clarity on buffered-until-onload (and buffers, buffers, everywhere) (1 by igrigorik)
https://github.com/w3c/performance-timeline/issues/78
- #79 PerformanceObserver developer / RUM friendliness (1 by igrigorik)
https://github.com/w3c/performance-timeline/issues/79
3 issues closed:
- PerformanceObserver developer / RUM friendliness https://github.com/w3c/performance-timeline/issues/79
- Clarity on buffered-until-onload (and buffers, buffers, everywhere) https://github.com/w3c/performance-timeline/issues/78
- WebIDL serializer has been deprecated in favor of toJSON operation https://github.com/w3c/performance-timeline/issues/82
* w3c/resource-timing (+0/-0/💬1)
1 issues received 1 new comments:
- #53 Server pushed resources in ResourceTiming (1 by bluesmoon)
https://github.com/w3c/resource-timing/issues/53
* w3c/navigation-timing (+0/-1/💬1)
1 issues received 1 new comments:
- #73 Can't determine whether there were no redirects or redirect failed timing allow check (1 by igrigorik)
https://github.com/w3c/navigation-timing/issues/73
1 issues closed:
- Can't determine whether there were no redirects or redirect failed timing allow check https://github.com/w3c/navigation-timing/issues/73
* w3c/user-timing (+0/-0/💬1)
1 issues received 1 new comments:
- #20 Worker tests for User Timing (1 by igrigorik)
https://github.com/w3c/user-timing/issues/20
* w3c/page-visibility (+0/-0/💬5)
1 issues received 5 new comments:
- #29 Log if a page was ever visible (5 by n8schloss, igrigorik, spanicker)
https://github.com/w3c/page-visibility/issues/29
* w3c/preload (+0/-2/💬4)
4 issues received 4 new comments:
- #97 Define the "Preload Cache" (1 by igrigorik)
https://github.com/w3c/preload/issues/97
- #82 Define resource abortion when link element or `rel` are removed (1 by igrigorik)
https://github.com/w3c/preload/issues/82
- #83 Tighter definition of "load was successful" (1 by igrigorik)
https://github.com/w3c/preload/issues/83
- #85 Specifying or using preload twice (1 by igrigorik)
https://github.com/w3c/preload/issues/85
2 issues closed:
- Tighter definition of "load was successful" https://github.com/w3c/preload/issues/83
- Specifying or using preload twice https://github.com/w3c/preload/issues/85
Pull requests
-------------
* w3c/hr-time (+1/-0/💬1)
1 pull requests submitted:
- Define "current high resolution time" as primitive (by igrigorik)
https://github.com/w3c/hr-time/pull/50
1 pull requests received 1 new comments:
- #39 Improve latest version headers (1 by igrigorik)
https://github.com/w3c/hr-time/pull/39
* w3c/performance-timeline (+1/-0/💬5)
1 pull requests submitted:
- Fix auto-publish (by marcoscaceres)
https://github.com/w3c/performance-timeline/pull/84
1 pull requests received 5 new comments:
- #84 Fix auto-publish (5 by marcoscaceres, igrigorik, deniak, siusin)
https://github.com/w3c/performance-timeline/pull/84
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
Received on Tuesday, 25 July 2017 17:00:13 UTC