- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Tue, 08 Aug 2017 17:00:10 +0000
- To: public-web-perf@w3.org
- Message-Id: <E1df7rW-0000Pw-I3@uranus.w3.org>
Issues ------ * w3c/performance-timeline (+1/-0/💬2) 1 issues created: - Would like a precise way to map PerformanceTimings to FetchEvent (by jakearchibald) https://github.com/w3c/performance-timeline/issues/85 2 issues received 2 new comments: - #66 Clarify disconnecting a PerformanceObserver that has observed entries (1 by birtles) https://github.com/w3c/performance-timeline/issues/66 - #85 Would like a precise way to map PerformanceTimings to FetchEvent (1 by jakearchibald) https://github.com/w3c/performance-timeline/issues/85 * w3c/beacon (+2/-3/💬20) 2 issues created: - Should sendBeacon set the FetchRequest's cacheMode to "no-cache"? (by cdumez) https://github.com/w3c/beacon/issues/48 - Editorial cleanup (by igrigorik) https://github.com/w3c/beacon/issues/47 6 issues received 20 new comments: - #40 ArrayBuffer uses "application/octet-stream" as default Content-Type in impl (12 by igrigorik, annevk, cdumez) https://github.com/w3c/beacon/issues/40 - #45 Should cross-origin beacons with an ArrayBuffer payload do a CORS preflight? (3 by cdumez, igrigorik) https://github.com/w3c/beacon/issues/45 - #47 Editorial cleanup (2 by igrigorik, siusin) https://github.com/w3c/beacon/issues/47 - #41 Tests for CORS and sendBeacon() (1 by igrigorik) https://github.com/w3c/beacon/issues/41 - #46 Complete PR for testing beacon (1 by igrigorik) https://github.com/w3c/beacon/issues/46 - #48 Should sendBeacon set the FetchRequest's cacheMode to "no-cache"? (1 by igrigorik) https://github.com/w3c/beacon/issues/48 3 issues closed: - Complete PR for testing beacon https://github.com/w3c/beacon/issues/46 - ArrayBuffer uses "application/octet-stream" as default Content-Type in impl https://github.com/w3c/beacon/issues/40 - Should cross-origin beacons with an ArrayBuffer payload do a CORS preflight? https://github.com/w3c/beacon/issues/45 * w3c/requestidlecallback (+1/-1/💬5) 1 issues created: - Define IdleDeadline internal layout part 2 (by annevk) https://github.com/w3c/requestidlecallback/issues/61 2 issues received 5 new comments: - #61 Define IdleDeadline internal layout part 2 (4 by igrigorik, annevk, rmcilroy) https://github.com/w3c/requestidlecallback/issues/61 - #57 Don't monkey patch the event loop algorithm (1 by igrigorik) https://github.com/w3c/requestidlecallback/issues/57 1 issues closed: - Don't monkey patch the event loop algorithm https://github.com/w3c/requestidlecallback/issues/57 Pull requests ------------- * w3c/hr-time (+0/-0/💬1) 1 pull requests received 1 new comments: - #39 Improve latest version headers (1 by igrigorik) https://github.com/w3c/hr-time/pull/39 * w3c/requestidlecallback (+0/-1/💬9) 1 pull requests received 9 new comments: - #60 Change start idle period algorithm to avoid monkey patching event loop. (9 by igrigorik, annevk, rmcilroy) https://github.com/w3c/requestidlecallback/pull/60 1 pull requests merged: - Change start idle period algorithm to avoid monkey patching event loop. https://github.com/w3c/requestidlecallback/pull/60 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, 8 August 2017 17:00:10 UTC