17:54:36 <RRSAgent> RRSAgent has joined #webperf
17:54:36 <RRSAgent> logging to http://www.w3.org/2016/11/17-webperf-irc
17:54:43 <xiaoqian> zakim, clear agenda
17:54:43 <Zakim> agenda cleared
17:57:40 <igrigorik> hello!
18:01:26 <n8s> n8s has joined #webperf
18:03:58 <NicJansma> NicJansma has joined #WebPerf
18:04:23 <n8s> n8s has joined #webperf
18:06:40 <igrigorik> first up, Perf timeline L2: https://github.com/w3c/performance-timeline/issues/62
18:06:44 <yoav> yoav has joined #webperf
18:07:50 <igrigorik> todd: I agree.
18:08:03 <igrigorik> resolution: push L2 to CR
18:09:34 <igrigorik> next up, User Timing L2: I believe we're good to push to CR, xiaoqian or plh to push it forward
18:10:21 <igrigorik> Page Visibility: https://github.com/w3c/page-visibility/pull/27
18:11:04 <igrigorik> next up, Resource Timing L2 issues
18:11:08 <igrigorik> nexthopprotocol:  https://github.com/w3c/resource-timing/pull/78
18:14:59 <igrigorik> 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
18:17:03 <igrigorik> Yoav/Shubhie: there is an intent thread on Blink which has privacy/security feedback and questions.
18:17:45 <igrigorik> Nic: we have lots of customers that don't know which protocol is being used, they're really excited about nextHopProtocol.
18:18:16 <igrigorik> Yoav: it would be useful to have "customer use cases" doc to help motivate this
18:23:37 <igrigorik> scheduling of add/queue: https://github.com/w3c/resource-timing/pull/79
18:25:12 <igrigorik> Yoav: one of the tests in webkti implementation was testing whether resource is available at onload. After investigating it, implementations didn't agree...
18:27:35 <igrigorik> _ could live either way, but current state of different implementations, is a mess
18:30:06 <igrigorik> Todd: "should" is a little weak, ideally we'd have MUST
18:33:55 <igrigorik> Todd: "after onload" might be tricky to implement
18:34:45 <igrigorik> Yoav: with regards to images and onload, I believe onload is a microtask.. which means that onload can fire before image is visible.
18:35:46 <igrigorik> Todd: I'd like to check-in with our guys about what the implications of running add step after onload
18:43:53 <igrigorik> definition of responsestart: https://github.com/w3c/resource-timing/issues/63
18:45:05 <igrigorik> initiatorType: https://github.com/w3c/resource-timing/issues/69
18:46:47 <igrigorik> we don't define fallback value: FF says "other", Chrome reports empty string.
18:50:16 <igrigorik> https://w3c.github.io/resource-timing/#dom-performanceresourcetiming-initiatortype
18:53:27 <igrigorik> NicJansma: we collapse "other" and "" into same bucket, collapsing in either direction is fine.
18:54:14 <igrigorik> plh: "other" seems better as empty string
18:55:23 <igrigorik> Todd: our plan was to use "fetch" for fetch and "sendBeacon" for beacon.
19:00:04 <igrigorik> rough consensus: "other", add sendbeacon and fetch. AI: investigate custom elements.
19:00:58 <igrigorik> For navigation timing, use "navigation".
19:05:46 <xiaoqian> present+ igrigorik, John, Todd, Nolan, Yoav, Xiaoqian, n8s, NicJansma, Shubhie, plh
19:05:51 <xiaoqian> RRSAgent, make minutes
19:05:51 <RRSAgent> I have made the request to generate http://www.w3.org/2016/11/17-webperf-minutes.html xiaoqian
19:06:46 <xiaoqian> RRSAgent, make log public
19:11:44 <plh_> plh_ has joined #webperf
19:21:54 <n8s> n8s has joined #webperf
19:24:16 <yoav> yoav has joined #webperf
19:29:03 <yoav> yoav has joined #webperf
19:32:21 <n8s> n8s has joined #webperf
19:42:09 <n8s> n8s has joined #webperf
20:04:23 <n8s> n8s has joined #webperf
20:05:51 <yoav> yoav has joined #webperf
20:46:43 <yoav> yoav has joined #webperf
21:20:40 <yoav> yoav has joined #webperf
21:33:17 <yoav> yoav has joined #webperf
21:34:10 <Zakim> Zakim has left #webperf