Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/performance-timeline (+3/-0/💬25)
  3 issues created:
  - Relevant global object for 'relevant performance entry buffer' (by npm1)
    https://github.com/w3c/performance-timeline/issues/122 
  - WebIDL spec does not allow required dictionary argument with no required members (by whh8b)
    https://github.com/w3c/performance-timeline/issues/119 
  - supportedEntryTypes API has some issues (by bzbarsky)
    https://github.com/w3c/performance-timeline/issues/117 

  4 issues received 25 new comments:
  - #117 supportedEntryTypes API has some issues (14 by annevk, npm1, bzbarsky)
    https://github.com/w3c/performance-timeline/issues/117 
  - #77 Add entryTypes method to enumerate type of entries observable via PerformanceObserver (7 by npm1, bzbarsky)
    https://github.com/w3c/performance-timeline/issues/77 [enhancement] 
  - #119 WebIDL spec does not allow required dictionary argument with no required members (3 by rniwa, whh8b, npm1)
    https://github.com/w3c/performance-timeline/issues/119 
  - #100 Ensure tests are clean (1 by whh8b)
    https://github.com/w3c/performance-timeline/issues/100 

* w3c/resource-timing (+2/-0/💬9)
  2 issues created:
  - Resource Timing and range requests (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/205 
  - Add tests for not-same-site nested contexts (by yoavweiss)
    https://github.com/w3c/resource-timing/issues/204 

  2 issues received 9 new comments:
  - #201 Specify TAO check for 304 responses (8 by rniwa, annevk, npm1, yoavweiss)
    https://github.com/w3c/resource-timing/issues/201 
  - #200 Be a bit more explicit about which subresources are to be ignored from stylesheets (1 by yoavweiss)
    https://github.com/w3c/resource-timing/issues/200 

* w3c/beacon (+0/-0/💬5)
  1 issues received 5 new comments:
  - #22 Should sendBeacon support GET? (5 by igrigorik, annevk, emmett9001, yoavweiss)
    https://github.com/w3c/beacon/issues/22 

* w3c/resource-hints (+1/-0/💬0)
  1 issues created:
  - It's not clear how preconnect would be used for redirects (by mac9416)
    https://github.com/w3c/resource-hints/issues/87 



Pull requests
-------------
* w3c/performance-timeline (+3/-1/💬6)
  3 pull requests submitted:
  - supported entry types needs to be context aware (by cvazac)
    https://github.com/w3c/performance-timeline/pull/121 
  - Make observe() parameter an optional dictionary (by npm1)
    https://github.com/w3c/performance-timeline/pull/120 
  - supportedEntryTypes: cache the FrozenArray (by npm1)
    https://github.com/w3c/performance-timeline/pull/118 

  2 pull requests received 6 new comments:
  - #118 supportedEntryTypes: cache the FrozenArray (3 by npm1)
    https://github.com/w3c/performance-timeline/pull/118 
  - #120 Make observe() parameter an optional dictionary (3 by whh8b, npm1)
    https://github.com/w3c/performance-timeline/pull/120 

  1 pull requests merged:
  - Make observe() parameter an optional dictionary
    https://github.com/w3c/performance-timeline/pull/120 

* w3c/navigation-timing (+1/-0/💬0)
  1 pull requests submitted:
  - supported entry types needs to be context aware (by cvazac)
    https://github.com/w3c/navigation-timing/pull/105 

* w3c/beacon (+0/-0/💬1)
  1 pull requests received 1 new comments:
  - #27 Add method to sendBeacon (1 by emmett9001)
    https://github.com/w3c/beacon/pull/27 


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