See also: IRC log
first up, Perf timeline L2: https://github.com/w3c/performance-timeline/issues/62
todd: I agree.
RESOLUTION: push L2 to CR
next up, User Timing L2: I believe we're good to push to CR, xiaoqian or plh to push it forward
Page Visibility: https://github.com/w3c/page-visibility/pull/27
next up, Resource Timing L2 issues
nexthopprotocol: https://github.com/w3c/resource-timing/pull/78
Todd: there is a use case for devs that want to know what types of caches (e.g. serviceworker); ALPN is, on the other hand, is already crisply defined.. so this may not be the right place
Yoav/Shubhie: there is an intent thread on Blink which has privacy/security feedback and questions.
Nic: we have lots of customers that don't know which protocol is being used, they're really excited about nextHopProtocol.
Yoav: it would be useful to have "customer use cases" doc to help motivate this
scheduling of add/queue: https://github.com/w3c/resource-timing/pull/79
Yoav: one of the tests in webkti implementation was testing whether resource is available at onload. After investigating it, implementations didn't agree...
_ could live either way, but current state of different implementations, is a mess
Todd: "should" is a little weak,
ideally we'd have MUST
... "after onload" might be tricky to implement
Yoav: with regards to images and onload, I believe onload is a microtask.. which means that onload can fire before image is visible.
Todd: I'd like to check-in with our guys about what the implications of running add step after onload
definition of responsestart: https://github.com/w3c/resource-timing/issues/63
initiatorType: https://github.com/w3c/resource-timing/issues/69
we don't define fallback value: FF says "other", Chrome reports empty string.
https://w3c.github.io/resource-timing/#dom-performanceresourcetiming-initiatortype
NicJansma: we collapse "other" and "" into same bucket, collapsing in either direction is fine.
plh: "other" seems better as empty string
Todd: our plan was to use "fetch" for fetch and "sendBeacon" for beacon.
rough consensus: "other", add sendbeacon and fetch. AI: investigate custom elements.
For navigation timing, use "navigation".
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. Present: igrigorik John Todd Nolan Yoav Xiaoqian n8s NicJansma Shubhie plh 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: 17 Nov 2016 Guessing minutes URL: http://www.w3.org/2016/11/17-webperf-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. 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[End of scribe.perl diagnostic output]