W3C home > Mailing lists > Public > public-web-perf@w3.org > March 2019

Weekly github digest (Web Performance WG specs)

From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
Date: Tue, 19 Mar 2019 17:01:14 +0000
To: public-web-perf@w3.org
Message-Id: <E1h6I70-0003Mq-B6@uranus.w3.org>



Issues
------
* w3c/hr-time (+0/-0/💬3)
  1 issues received 3 new comments:
  - #64 Gate Timestamps behind existing permission prompts (3 by tomrittervg, noncombatant, psnyde2)
    https://github.com/w3c/hr-time/issues/64 

* w3c/performance-timeline (+0/-0/💬3)
  3 issues received 3 new comments:
  - #113 supported entry types needs to be context aware (1 by npm1)
    https://github.com/w3c/performance-timeline/issues/113 
  - #100 Ensure tests are clean (1 by npm1)
    https://github.com/w3c/performance-timeline/issues/100 
  - #110 Broken link to non-existent anchor in WebIDL spec (1 by npm1)
    https://github.com/w3c/performance-timeline/issues/110 

* w3c/resource-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #203 Include Content Type (1 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/203 

* w3c/user-timing (+0/-1/💬6)
  3 issues received 6 new comments:
  - #17 Declarative marks (4 by igrigorik, tdresser, npm1, yoavweiss)
    https://github.com/w3c/user-timing/issues/17 [whiteboard] 
  - #37 Update the introductory text to explain how this API differs from performance.now() (1 by igrigorik)
    https://github.com/w3c/user-timing/issues/37 
  - #25 Provide a way to associate warnings with measurements (1 by igrigorik)
    https://github.com/w3c/user-timing/issues/25 [whiteboard] 

  1 issues closed:
  - Declarative marks https://github.com/w3c/user-timing/issues/17 [whiteboard] 

* w3c/preload (+0/-1/💬0)
  1 issues closed:
  - `srcset`/`sizes` attributes for selectively preloading images https://github.com/w3c/preload/issues/120 [discuss] 

* w3c/resource-hints (+1/-0/💬13)
  1 issues created:
  - Specify processing model in terms of Fetch (by annevk)
    https://github.com/w3c/resource-hints/issues/86 

  3 issues received 13 new comments:
  - #74 Sending a `Purpose: prefetch` header for prefetched resources (11 by toyoshim, annevk, kinu, yoavweiss)
    https://github.com/w3c/resource-hints/issues/74 [Prefetch] 
  - #86 Specify processing model in terms of Fetch (1 by jyasskin)
    https://github.com/w3c/resource-hints/issues/86 
  - #78 Prefetch vs Service Workers (1 by horo-t)
    https://github.com/w3c/resource-hints/issues/78 [Prefetch] 



Pull requests
-------------
* w3c/performance-timeline (+1/-1/💬0)
  1 pull requests submitted:
  - L2: Remove buffered flag (by npm1)
    https://github.com/w3c/performance-timeline/pull/114 

  1 pull requests merged:
  - L2: Remove buffered flag
    https://github.com/w3c/performance-timeline/pull/114 


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, 19 March 2019 17:01:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 19 March 2019 17:01:18 UTC