- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 26 May 2020 17:00:41 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1jdcwT-00033l-Jg@uranus.w3.org>
Issues ------ * w3c/navigation-timing (+0/-1/💬2) 1 issues received 2 new comments: - #126 Possibility to get the HTTP status code from the Response Header ? (2 by bripkens, nicjansma) https://github.com/w3c/navigation-timing/issues/126 1 issues closed: - Possibility to get the HTTP status code from the Response Header ? https://github.com/w3c/navigation-timing/issues/126 Pull requests ------------- * w3c/page-visibility (+0/-1/💬4) 1 pull requests received 4 new comments: - #54 Chore: export definitions (4 by marcoscaceres, plehegar, siusin, yoavweiss) https://github.com/w3c/page-visibility/pull/54 1 pull requests merged: - Chore: export definitions https://github.com/w3c/page-visibility/pull/54 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, 26 May 2020 17:00:43 UTC