Nav Timing

https://github.com/w3c/navigation-timing/issues/50#issuecomment-268919388

shubhie: we want to ship in M58, should we make the change?

n8s: yeah, this is critical for us

todd: we do the proposed approach for NT2, not RT2

yoav: for RT2 it could break some tests?
... let's separate the discussions

todd: NT2 already functions this way in IE11/Edge. lgtm

yoav, n8s, shubhie: lgtm

for RT2, can we make the same update?

yoav: practical concerns around non RT tests that may break? We need to change the code and see what breaks (if anything)
... also, could code rely on entry being added at resource onload?

we'll draft PR for RT2 and discuss implications.. e.g. do we need a new attribute to indicate done?

https://github.com/w3c/navigation-timing/issues/59

todd: conceptually makes sense... concern is if there is any existing code querying for "document". Question: is it worth breaking a legacy browser to add name in URL field.. to support the future?
... we could add new field, as an option

yoav: do we have any data? todd: nothign on this particular string
... only use case I can think of is "getEntriesByName('document')"

n8s: it would be useful to have the URL

todd: let's check w/ Soasta and other folks about use of name field + checking value "document"

AI: get feedback, revisit on the next call.

Performance Timeline

https://github.com/w3c/performance-timeline/issues/64

yoav: current implementation in Chrome throws an exception if you try to register an observer for unsupported types, whereas spec says ignore; for getEntries they're ignored in both spec and implementation

todd: ... this could be good time to change shape of PerfObserver, if we wanted
... is there a way to check if the type exists?
... if the type is around, browser supports it. perhaps it's already doable?

AI: Yoav, will update the issue.

Long Tasks V1 progress updates...

shubhie: iterating in Chrome, in good shape overall.
... 1ms clamping + 50ms floor on the task got positive feedback from security review
... Dominic is helping out with the spec

igrigorik: should we consider graduating LT from WICG to webperf

todd: sgtm, looking forward to implement.. need to review latest updates.
... I'll review later today on WICG.

xiaoqian: as long as our charter is good, we don't need to recharter

AI: check-in with plh@ on charter + process

shubie: we got good feedback from ads folks.. who found it useful.
... also, YouTube and FB are playgn with it
... attribution is of interest to everyone.

-- FP + FCP update --

https://docs.google.com/document/d/1XVP9jaZT7acQtK5O6vO-mIz31i5iB-pZn1S41_YP6p0/edit#

shubhie: should capture all the phases between main thread vs compositor, etc.
... looking at higher percentiles, we should consider up to the second step (time to composite + rasterization), ignore the rest. GPU stuff is unspeccable and too small to justify the effort.

todd: this matches my intuition for what I expect to see in Edge

shubhie: unclear on how to spec.. as HTML does not even talk about compositor.

todd: exposing two numbers could expose differences between structure of graphics/layers vs blocking main thread

yoav: that would be interesting in ~frame-timing case, but for first paint vs first-contentful-paint .. maybe not so much?

duration should be the most accurate, we could expose additional attributes

AI: update spec with non-normative note recommending the point in time we want to capture

This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: igrigorik
Inferring Scribes: igrigorik

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: AI cristi https igrigorik n8s shubhie shubie todd xiaoqian yoav
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

        <amy> Present+


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 18 Jan 2017
Guessing minutes URL: http://www.w3.org/2017/01/18-webperf-minutes.html
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report