18:07:54 RRSAgent has joined #webperf 18:07:54 logging to http://www.w3.org/2016/11/30-webperf-irc 18:08:13 _ one change we made is reporting a list of iframe attributes: name, id, source 18:08:48 _ security review: iterating on feedback, still an open discussion 18:09:21 _ attribution: plan is to show long scripts URLs 18:09:34 _ next steps: we'll update the explainer next week, ptal. 18:10:09 _ implementation: partial implementation in Canary behind experimental flag -- give it a try. 18:10:43 yoav: where are we with the spec? 18:11:52 shubhie: yeah, we'll work on expanding on explainer to cover processing / security, etc. 18:13:03 ... AI: everyone to review explainer, we'll discuss how and where to expand on next call 18:13:15 next up: Paint Timing API 18:15:05 NicJansma has joined #webperf 18:15:09 Todd: there are lots of scenarios where main thread can cause compositor to run slower -- e.g. combination of webgl/canvas/svg bogs down; or an image decode appears to be done on main thread, but image shows up way later 18:16:09 Shubhie: do we have a sense for how common that is? 18:16:18 Todd: this is probably the long tail.. 18:17:19 Todd: we should probably think about this entire process as a two phase process: main thread > compositor 18:17:46 _ this is implementation specific, but at the same time, this is a common pattern for most browsers 18:19:34 yoav: what's the point of providing both.. the developer only cares about the longer time? 18:20:53 Todd/Shubhie: having two provides a good hint for where the problem may be 18:23:31 AI: let's document alternative models on GitHub and iterate there 18:25:50 n8s has joined #webperf 18:28:19 Yoav: we need to start a thread WICG thread and we can transfer the repo 18:28:41 https://github.com/w3c/resource-timing/pull/80 18:30:11 https://github.com/w3c/resource-timing/pull/81 18:31:58 AI: Todd will review 18:32:49 https://github.com/w3c/resource-timing/pull/79 18:33:06 n8s has joined #webperf 18:39:27 Todd: agree that we can't specify a MUST because we have different implementations; we can add a note in the spec, as in PR 18:40:47 _ there is a separate issue: we should gather some telemetry.. how often is this used? if we find that everyone relies on this, then perhaps we ought go back and change to MUST 18:42:14 igrigorik: we should also write some tests to figure out interop between existing implementations 18:43:59 AI: update note with a disclaimer, and in parallel we should open an issue to investigate current implementations and use in the wild 18:44:28 https://github.com/w3c/resource-timing/issues/63 18:49:34 Todd: if we want to make a difference between first byte vs header complete vs ... those should be different attributes 18:52:22 _ if we want to break apart first byte, we're better of with different measurements 18:55:30 AI: update to align with receipt of first byte by the HTTP parser 18:56:24 ... NT2 ... 18:57:05 Todd: it's helpful to be able to tell the tests apart; having a prefix would be helpful 18:57:20 plh: we're ok with the idea, but we do have tests that apply to both 18:57:29 _ it's ok to have tests that don't have a version number 18:58:57 Shubhie: do we duplicate tests? 18:59:22 Todd: implementations that don't have NT1 would want those 19:03:39 https://github.com/w3c/navigation-timing/pull/52 19:04:04 .. we'll merge the extended diagram, as we want to optimize for those reading the spec 19:04:36 ... and, looks like Todd beat us to the punch :) 19:04:44 thanks all! 19:04:48 present+ igrigorik, Todd, Shubhie, plh, NicJansma, yoav, xiaoqian 19:04:53 RRSAgent, make minutes 19:04:53 I have made the request to generate http://www.w3.org/2016/11/30-webperf-minutes.html xiaoqian 19:05:34 RRSAgent, make log public 20:11:53 yoav_ has joined #webperf 21:22:31 Zakim has left #webperf 22:21:10 yoav has joined #webperf 23:12:31 smaug has joined #webperf