Next call: November 27th @ 11AM PST (Triage/Design)

Hey folks,

Please join us on the call next week. We'll have a new hangout link
<https://hangouts.google.com/hangouts/_/chromium.org/webperfwg> for the
call, which will hopefully be smooth to connect to. If you'd add your name
and email to the list
<https://docs.google.com/spreadsheets/d/1j7uyLfYoNqJkBF8MHfh48wjZ6PApz4GylxhHLqoTP_s/edit?usp=sharing>
I'll send you a calendar invite with that link, which will hopefully make
it easier to join the calls (as you will not need someone to click you
through).

See y'all there!
Tentative agenda below, but please add to it if you want to discuss
something else:

   -

   Resource Timing
   -

      Make TAO a subset of CORS
      <https://github.com/w3c/resource-timing/issues/178>
      -

      Allow semi-wildcard `Timing-Allow-Origin` values (for subdomains)
      <https://github.com/w3c/resource-timing/issues/175>
      -

      Should 404 codes by considered aborts?
      <https://github.com/w3c/resource-timing/issues/165>
      -

   Navigation Timing
   -

      Unload event TAO check should be for all redirects
      <https://github.com/w3c/navigation-timing/issues/95>
      -

      Define attribute behavior only once
      <https://github.com/w3c/navigation-timing/issues/97>
      -

   User Timing
   -

      Update on current usage, based on Chrome Canary data.
      -

         Of calls to performance.measure:
         -

            For the start parameter and the end parameter.
            -

               A number is passed < 0.0001% of the time.
               -

               Null or undefined are passed < 0.0001% of the time.
               -

   Event/Element Timing - proposed changes


Cheers :)
Yoav