Weekly github digest (Web Performance WG specs)

Issues
------
* w3c/performance-timeline (+1/-0/💬0)
  1 issues created:
  - Queue the entry should require a global object as input (by npm1)
    https://github.com/w3c/performance-timeline/issues/162 

* w3c/navigation-timing (+2/-0/💬1)
  2 issues created:
  - What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? (by abhishekcghosh)
    https://github.com/w3c/navigation-timing/issues/124 
  - Surface chunk network timing details (by jtedesco)
    https://github.com/w3c/navigation-timing/issues/123 

  1 issues received 1 new comments:
  - #123 Surface chunk network timing details (1 by nhelfman)
    https://github.com/w3c/navigation-timing/issues/123 

* w3c/user-timing (+0/-0/💬1)
  1 issues received 1 new comments:
  - #69 Allow performance.measure() to specify optional color parameter, to be used by perf visualizations in devtools (1 by fshort)
    https://github.com/w3c/user-timing/issues/69 

* w3c/paint-timing (+3/-8/💬92)
  3 issues created:
  - Timestamps should be specified in an interoperative way (by smfr)
    https://github.com/w3c/paint-timing/issues/62 
  - Clarify: are gradients considered contentful? (by noamr)
    https://github.com/w3c/paint-timing/issues/61 
  - Clarify whether First Contentful Paint considers content outside the viewport (by smfr)
    https://github.com/w3c/paint-timing/issues/58 

  17 issues received 92 new comments:
  - #62 Timestamps should be specified in an interoperative way (5 by npm1, rniwa)
    https://github.com/w3c/paint-timing/issues/62 
  - #61 Clarify: are gradients considered contentful? (3 by noamr, npm1, rniwa)
    https://github.com/w3c/paint-timing/issues/61 
  - #58 Clarify whether First Contentful Paint considers content outside the viewport (34 by anniesullie, noamr, npm1, othermaciej, rniwa, smfr, yoavweiss)
    https://github.com/w3c/paint-timing/issues/58 
  - #57 Allow optional implementation of first-paint (8 by anniesullie, bdekoz, noamr, rniwa)
    https://github.com/w3c/paint-timing/issues/57 
  - #56 Clarify contentful state regarding images that are not foreground/background (1 by noamr)
    https://github.com/w3c/paint-timing/issues/56 
  - #55 Combination of paint timing and long tasks can expose precise paint timing (1 by rniwa)
    https://github.com/w3c/paint-timing/issues/55 
  - #54 Clarify what happens to a page which consists of just an iframe (12 by noamr, npm1, rniwa)
    https://github.com/w3c/paint-timing/issues/54 
  - #53 Clarify whether "first paint" or "first contentful paint" ever happens to a blank page (6 by noamr, npm1, rniwa)
    https://github.com/w3c/paint-timing/issues/53 
  - #52 Consider taking form controls into account for first contentful paint (1 by rniwa)
    https://github.com/w3c/paint-timing/issues/52 
  - #51 First contentful paint should take the poster image / first frame of video into account (1 by rniwa)
    https://github.com/w3c/paint-timing/issues/51 
  - #50 Wording about canvas/svg is a bit inaccurate (14 by annevk, noamr, npm1, rniwa)
    https://github.com/w3c/paint-timing/issues/50 
  - #37 supported entry types needs to be context aware (1 by npm1)
    https://github.com/w3c/paint-timing/issues/37 
  - #29 Clarify invisible text (1 by npm1)
    https://github.com/w3c/paint-timing/issues/29 [should discuss] 
  - #20 Define whether clipped contents should be included in first contextual paint (1 by npm1)
    https://github.com/w3c/paint-timing/issues/20 [should discuss] 
  - #19 The exact timing of navigation should be defined (1 by npm1)
    https://github.com/w3c/paint-timing/issues/19 [should discuss] 
  - #14 Headings should be sentence case, not titlecase (1 by npm1)
    https://github.com/w3c/paint-timing/issues/14 [editorial] 
  - #11 Nit: heading style for Paint timing (1 by npm1)
    https://github.com/w3c/paint-timing/issues/11 [editorial] 

  8 issues closed:
  - supported entry types needs to be context aware https://github.com/w3c/paint-timing/issues/37 
  - Headings should be sentence case, not titlecase https://github.com/w3c/paint-timing/issues/14 [editorial] 
  - Nits in "PerformancePaintTiming interface" https://github.com/w3c/paint-timing/issues/12 [editorial] 
  - Clarify whether First Contentful Paint considers content outside the viewport https://github.com/w3c/paint-timing/issues/58 
  - Nit: heading style for Paint timing https://github.com/w3c/paint-timing/issues/11 [editorial] 
  - Cross-link to update the rendering https://github.com/w3c/paint-timing/issues/10 [editorial] 
  - Clarify whether First Contentful Paint considers content outside the viewport https://github.com/w3c/paint-timing/issues/58 
  - Combination of paint timing and long tasks can expose precise paint timing https://github.com/w3c/paint-timing/issues/55 

* w3c/longtasks (+1/-0/💬0)
  1 issues created:
  - Combination of paint timing and long tasks can expose precise paint timing (by rniwa)
    https://github.com/w3c/longtasks/issues/80 



Pull requests
-------------
* w3c/paint-timing (+7/-5/💬7)
  7 pull requests submitted:
  - Pass document as input to paint timing algorithms (by npm1)
    https://github.com/w3c/paint-timing/pull/67 
  - Clarify what 'contentful' means (by noamr)
    https://github.com/w3c/paint-timing/pull/66 
  - Add link to viewport (by npm1)
    https://github.com/w3c/paint-timing/pull/65 
  - Editorial fixes (by npm1)
    https://github.com/w3c/paint-timing/pull/64 
  - Editorial: update the rendering link fix (by npm1)
    https://github.com/w3c/paint-timing/pull/63 
  - Allow mask images to be contentful (by npm1)
    https://github.com/w3c/paint-timing/pull/60 
  - Clarify paints outside viewport (by npm1)
    https://github.com/w3c/paint-timing/pull/59 

  3 pull requests received 7 new comments:
  - #67 Pass document as input to paint timing algorithms (1 by rniwa)
    https://github.com/w3c/paint-timing/pull/67 
  - #60 Allow mask images to be contentful (4 by noamr, npm1)
    https://github.com/w3c/paint-timing/pull/60 
  - #59 Clarify paints outside viewport (2 by npm1, smfr)
    https://github.com/w3c/paint-timing/pull/59 

  5 pull requests merged:
  - Pass document as input to paint timing algorithms
    https://github.com/w3c/paint-timing/pull/67 
  - Editorial fixes
    https://github.com/w3c/paint-timing/pull/64 
  - Add link to viewport
    https://github.com/w3c/paint-timing/pull/65 
  - Editorial: update the rendering link fix
    https://github.com/w3c/paint-timing/pull/63 
  - Clarify paints outside viewport
    https://github.com/w3c/paint-timing/pull/59 

* w3c/longtasks (+0/-1/💬1)
  1 pull requests received 1 new comments:
  - #79 Fix typo (1 by npm1)
    https://github.com/w3c/longtasks/pull/79 

  1 pull requests merged:
  - Fix typo
    https://github.com/w3c/longtasks/pull/79 


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