[minutes] Web Performance 20150923

Available at
  http://www.w3.org/2015/09/23-webperf-minutes.html

Text version:

                             Web Performance

23 Sep 2015

    See also: [2]IRC log

       [2] http://www.w3.org/2015/09/23-webperf-irc

Attendees

    Present
           plh, yoav, todd, ilya

    Regrets
           Eli

    Chair
           Ilya

    Scribe
           ToddReifsteck

Contents

      * [3]Topics
          1. [4]Resource timing as base (for Nav Timing)
          2. [5]Slow-only frames, no composite, processing
             improvements (Frame Timing)
          3. [6]Future-proof the rIC API and make it extensible
          4. [7]call Fetch to extract byte stream and content type
             (Beacon)
          5. [8]Size attributes: switch to unsigned long long and
             clarify TAO restrictions (Resource Timing)
          6. [9]Improve "initiator" reporting (Resource Timing)
          7. [10]set visibilityState when prerendering (Resource
             Hints)
          8. [11]Clarify perf observer registration process
             (Performance Timeline)
      * [12]Summary of Action Items
      __________________________________________________________

Resource timing as base (for Nav Timing)

    <plh> [13]https://github.com/w3c/navigation-timing/pull/36

      [13] https://github.com/w3c/navigation-timing/pull/36

    <plh>
    [14]https://w3c.github.io/navigation-timing/#sec-performance-na
    vigation-types

      [14] 
https://w3c.github.io/navigation-timing/#sec-performance-navigation-types

    plh: what should initiatorType returns for NT? null, empty
    string, something else?
    ... I'll keep it as an issue in the spec for now.

Slow-only frames, no composite, processing improvements (Frame
Timing)

    <ilya> [15]https://github.com/w3c/frame-timing/pull/48

      [15] https://github.com/w3c/frame-timing/pull/48

    Ilya: I rewrote frame timing to only report slow frames

Future-proof the rIC API and make it extensible

    <plh> [16]https://github.com/w3c/requestidlecallback/issues/21

      [16] https://github.com/w3c/requestidlecallback/issues/21

call Fetch to extract byte stream and content type (Beacon)

    [17]https://github.com/w3c/beacon/pull/11

      [17] https://github.com/w3c/beacon/pull/11

    <plh> " Specifications SHOULD only use USVString for APIs that
    perform text processing and need a string of Unicode scalar
    values to operate on. Most APIs that use strings should instead
    be using DOMString, which does not make any interpretations of
    the code units in the string. When in doubt, use DOMString. "

Size attributes: switch to unsigned long long and clarify TAO
restrictions (Resource Timing)

    -- [18]https://github.com/w3c/resource-timing/pull/33

      [18] https://github.com/w3c/resource-timing/pull/33

    <plh> [19]http://www.w3.org/TR/resource-timing/

      [19] http://www.w3.org/TR/resource-timing/

Improve "initiator" reporting (Resource Timing)

    -- [20]https://github.com/w3c/resource-timing/issues/8

      [20] https://github.com/w3c/resource-timing/issues/8

    <plh>
    [21]http://www.w3.org/TR/2015/WD-resource-timing-20150923/

      [21] http://www.w3.org/TR/2015/WD-resource-timing-20150923/

    <igrigorik> ai: add "preflight" and "fetch" to initiatorType

set visibilityState when prerendering (Resource Hints)

    -- [22]https://github.com/w3c/resource-hints/pull/42

      [22] https://github.com/w3c/resource-hints/pull/42

Clarify perf observer registration process (Performance Timeline)

    -- [23]https://github.com/w3c/performance-timeline/pull/47

      [23] https://github.com/w3c/performance-timeline/pull/47

Summary of Action Items

    [End of minutes]

Received on Wednesday, 21 October 2015 17:11:04 UTC