Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/hr-time (+1/-1/💬3)
  1 issues created:
  - Time origin of event timestamps across iframes (by querymetrics)
    https://github.com/w3c/hr-time/issues/81 

  1 issues received 3 new comments:
  - #81 Time origin of event timestamps across iframes (3 by rniwa, toddreifsteck)
    https://github.com/w3c/hr-time/issues/81 

  1 issues closed:
  - Time origin of event timestamps across iframes https://github.com/w3c/hr-time/issues/81 

* w3c/resource-timing (+0/-0/💬2)
  2 issues received 2 new comments:
  - #200 Be a bit more explicit about which subresources are to be ignored from stylesheets (1 by toddreifsteck)
    https://github.com/w3c/resource-timing/issues/200 
  - #207 Clarify that TAO needs to be set even on same origin resource after cross-origin redirects (1 by toddreifsteck)
    https://github.com/w3c/resource-timing/issues/207 

* w3c/navigation-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #114 Spec for PerformanceNavigationTiming.type does not match any implementations (1 by toddreifsteck)
    https://github.com/w3c/navigation-timing/issues/114 

* w3c/page-visibility (+1/-0/💬1)
  1 issues created:
  - Republish editorial PR  (by marcoscaceres)
    https://github.com/w3c/page-visibility/issues/53 

  1 issues received 1 new comments:
  - #51 Unexpected HTML things to check (1 by toddreifsteck)
    https://github.com/w3c/page-visibility/issues/51 

* w3c/preload (+0/-0/💬4)
  1 issues received 4 new comments:
  - #139 Specifying Range in Link preload header for HTTP/2 Push (4 by roger-on-github, yoavweiss)
    https://github.com/w3c/preload/issues/139 

* w3c/resource-hints (+0/-0/💬3)
  1 issues received 3 new comments:
  - #82 Prefetch and double-key caching (3 by yutakahirano, domfarolino, youennf)
    https://github.com/w3c/resource-hints/issues/82 [Prefetch] 

* w3c/requestidlecallback (+0/-1/💬1)
  1 issues received 1 new comments:
  - #77 The timeRemaining language is confusing (1 by yoavweiss)
    https://github.com/w3c/requestidlecallback/issues/77 

  1 issues closed:
  - The timeRemaining language is confusing https://github.com/w3c/requestidlecallback/issues/77 

* w3c/longtasks (+0/-1/💬5)
  4 issues received 5 new comments:
  - #57 supported entry types needs to be context aware (2 by yoavweiss, toddreifsteck)
    https://github.com/w3c/longtasks/issues/57 
  - #64 containerSrc could be long (a data URI) (1 by toddreifsteck)
    https://github.com/w3c/longtasks/issues/64 
  - #41 Should PerformanceObserver.observe(... buffered=true}) work for LongTasks? (1 by toddreifsteck)
    https://github.com/w3c/longtasks/issues/41 [requires-discussion] 
  - #67 "multiple-contexts" doesn't seem useful (1 by toddreifsteck)
    https://github.com/w3c/longtasks/issues/67 

  1 issues closed:
  - supported entry types needs to be context aware https://github.com/w3c/longtasks/issues/57 



Pull requests
-------------
* w3c/page-visibility (+1/-1/💬1)
  1 pull requests submitted:
  - chore: fix some xref issues (by marcoscaceres)
    https://github.com/w3c/page-visibility/pull/52 

  1 pull requests received 1 new comments:
  - #52 chore: fix some xref issues (1 by yoavweiss)
    https://github.com/w3c/page-visibility/pull/52 

  1 pull requests merged:
  - chore: fix some xref issues
    https://github.com/w3c/page-visibility/pull/52 


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, 6 August 2019 17:00:45 UTC