IRC log of webperf on 2013-02-13

Timestamps are in UTC.

18:05:34 [RRSAgent]
RRSAgent has joined #webperf
18:05:34 [RRSAgent]
logging to http://www.w3.org/2013/02/13-webperf-irc
18:05:41 [plh]
rrsagent, make logs public-visible
18:06:10 [plh]
Present+ Arvind
18:06:14 [plh]
Present+ Philippe
18:06:16 [ganesh]
ganesh has joined #webperf
18:06:19 [plh]
Present+ Ganesh
18:06:22 [plh]
Present+ Alois
18:06:25 [plh]
Present+ Daniel
18:06:33 [simonjam]
and James
18:06:38 [plh]
Meeting: Web Performance
18:06:49 [plh]
Present+ James
18:06:56 [JatinderMann]
JatinderMann has joined #webperf
18:07:00 [plh]
Present+ Jatinder
18:07:19 [plh]
Chair: Jatinder
18:07:29 [plh]
rrsagent, generate minutes
18:07:29 [RRSAgent]
I have made the request to generate http://www.w3.org/2013/02/13-webperf-minutes.html plh
18:08:18 [plh]
Topic: Testing of User Timing
18:08:39 [plh]
Jatinder: I recommend we move the tests from Intel to approved
18:08:58 [plh]
... I'll look at the resource timing tests later
18:09:08 [plh]
... I'll move the user timing tests
18:09:43 [plh]
Topic: Resource Timing cross origin redirect
18:10:29 [plh]
Jatinder: I'll respond to Pan on that. Didn't close on what to do yet. I think he has a point on per resource point
18:10:42 [plh]
Topic: Navigation Timing 2
18:10:58 [plh]
Jatinder: one of the goal is perceive latency and with pre-render, the latency changes
18:11:15 [plh]
... should we add an attribute preRenderSwitch to NV2?
18:11:55 [plh]
... today, we get duration. would be interesting to have the delta between loadEvent and preRenderSwitch
18:12:07 [plh]
... it seems logical to me at least
18:12:24 [plh]
James: sounds good to me. it ties into page visibility as well
18:12:48 [plh]
Jatinder: we should make it clear that this is not real time performance but rather data to understand page load performance
18:12:54 [Zakim]
Zakim-bot will be restarted in 3 minutes to recover caller state; please save your agenda status. Apologies for the inconvenience
18:13:12 [plh]
... I'll follow up by mail
18:13:25 [plh]
... we'll have to be careful on how preRenderSwitch will come off
18:13:39 [plh]
Topic: Beacon API
18:13:52 [plh]
Jatinder: sent mail about this regarding the relationship with XHR
18:14:11 [plh]
... so we don't have to reinvent everything
18:14:23 [plh]
... seems like there is interest
18:14:41 [plh]
... I was hoping we can continue exploring, so let's not cut it from our list
18:14:53 [plh]
... in a perfect world, I would love to have XHR take it on
18:15:15 [plh]
Alois: yes, this would require some input from our side. let's try to reuse here
18:15:25 [plh]
... hopefully it will get into XHR
18:16:38 [plh]
Jatinder: it seems we'll need to provide guidance to them
18:16:45 [plh]
... we'll send them a proposal
18:17:07 [plh]
Topic: Prerender
18:17:15 [plh]
Arvind: I started to write it
18:17:39 [plh]
Jatinder: I have a bunch of questions and will hold until you come up with something
18:19:26 [plh]
Arvind: two ways, link tag and when the browser does it (like typing in the address bar)
18:19:37 [plh]
... I'm focusing with the link tag
18:19:52 [plh]
Jatinder: yes, I don't think we should define heuristic indeeed
18:20:08 [plh]
... should we say that "user agents can use heuristics" ?
18:20:28 [plh]
... should we say something about prerendering https?
18:20:39 [plh]
Arvind: we waited to avoid side effect
18:20:54 [plh]
Daniel: do we have data on side effects?
18:21:03 [plh]
Arvind: not really, I'll follow up
18:21:24 [plh]
Jatinder: should we leave the spec open or not?
18:22:01 [plh]
... also a performance impact. Should we put limits?
18:22:24 [plh]
... it seems logical to one, rather than the whole result page
18:22:42 [plh]
Arvind: ok, I'll keep working on it
18:23:28 [plh]
Jatinder: if you can share the documentation you have, that would be nice
18:23:36 [Zakim]
Zakim has joined #webperf
18:23:39 [plh]
Topic: other specs
18:23:41 [plh]
Jatinder: resource priorities, diagnostic
18:26:14 [plh]
Topic: Page Visibility, RAF
18:26:18 [plh]
Plh: we're on track
18:31:10 [plh]
Topic: Milestones
18:31:20 [plh]
Plh: are the milestones correct?
18:31:25 [plh]
Arvind, Jatinder: yes
18:31:47 [plh]
Topic: bandwidth testing issue
18:32:27 [plh]
Jatinder: the nav timing is post processing, while bandwidth is for real time decision
18:32:39 [plh]
... nav timing isn't a real time api
18:32:58 [plh]
Daniel: I've been writing some thoughts and will send them along
18:33:30 [plh]
Plh: should it go into XHR?
18:33:40 [plh]
Daniel: up for discussion.
18:34:21 [plh]
[adjourned]
18:34:37 [plh]
rrsagent, generate minutes
18:34:37 [RRSAgent]
I have made the request to generate http://www.w3.org/2013/02/13-webperf-minutes.html plh
20:29:24 [jeffh]
jeffh has joined #webperf
21:42:31 [Zakim]
Zakim has left #webperf