WebPerf WG triage call - March 28th @ 11am PT

Hey all!

Let's solve some issues!! As discussed, this week the call would on Friday
March 28th. The tentative agenda
<https://docs.google.com/document/d/10dz_7QM5XCNsGeI63R864lF9gFqlqQD37B4q8Q46LMM/edit?pli=1#heading=h.yo5h5e71az08>
is
currently:

   -

   Process improvements
   -

   Performance Timeline
   -

      WebIDL spec does not allow required dictionary argument with no
      required members
      <https://github.com/w3c/performance-timeline/issues/119>
      -

      supportedEntryTypes API has some issues
      <https://github.com/w3c/performance-timeline/issues/117>
      -

         supportedEntryTypes: cache the FrozenArray
         <https://github.com/w3c/performance-timeline/pull/118>
         -

   Resource Timing
   -

      4 non-triaged issues
      <https://github.com/w3c/resource-timing/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+no%3Amilestone>
      -

      Test status
      <https://github.com/w3c/resource-timing/issues/71#issuecomment-462167655>
      - wpt.fyi
      <https://wpt.fyi/results/resource-timing?label=master&product=chrome%5Bexperimental%5D&product=edge&product=firefox%5Bexperimental%5D&product=safari%5Bexperimental%5D&aligned>
      -

      Pending test - Test XO redirection sandwich with and without TAO
      <https://github.com/web-platform-tests/wpt/pull/13518>
      -

   Navigation Timing
   -

      Applying "timing allow check" to a document makes no sense
      <https://github.com/w3c/navigation-timing/issues/104>
      -

      supported entry types needs to be context aware
      <https://github.com/w3c/navigation-timing/issues/102>
      -

      workerStart should be clearly defined as applicable to the last SW
      <https://github.com/w3c/navigation-timing/issues/100>
      -

      workerStart should be gated on timing-allow check
      <https://github.com/w3c/navigation-timing/issues/99>
      -

      secureConnectionStart definition is inconsistent with ResourceTiming
      <https://github.com/w3c/navigation-timing/issues/84>



Feel free to add more issues you feel need to be discussed to that list.
The hangout link for this meeting is the usual one
<https://meet.google.com/nog-ttdz-myg?hs=122>.

See y'all tomorrow :)
Yoav