18:01:04 <RRSAgent> RRSAgent has joined #webperf
18:01:04 <RRSAgent> logging to http://www.w3.org/2016/03/03-webperf-irc
18:01:05 <yoav> yoav has joined #webperf
18:01:06 <trackbot> RRSAgent, make logs world
18:01:08 <trackbot> Zakim, this will be web-per
18:01:08 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
18:01:09 <trackbot> Meeting: Web Performance Working Group Teleconference
18:01:09 <trackbot> Date: 03 March 2016
18:01:16 <plh> agenda+ Resource Timing
18:01:25 <plh> agenda+ Beacon
18:01:35 <plh> agenda+ Preload
18:01:40 <plh> agenda+ Reporting
18:01:45 <toddreifsteck> toddreifsteck has joined #webperf
18:01:48 <plh> agenda+ hr-time
18:01:53 <plh> agenda+ Velocity
18:01:57 <plh> agenda?
18:02:16 <plh> zakkim, drop agendum 2
18:02:22 <plh> zakkim, drop agendum 3
18:02:26 <plh> agenda?
18:02:32 <plh> zakim, close agendum 2
18:02:32 <Zakim> agendum 2, HRT and privacy issue, closed
18:02:33 <Zakim> I see 7 items remaining on the agenda; the next one is
18:02:33 <Zakim> 3. web perf observer [from plh]
18:02:33 <plh> zakim, close agendum 3
18:02:34 <Zakim> agendum 3, web perf observer, closed
18:02:34 <Zakim> I see 6 items remaining on the agenda; the next one is
18:02:34 <Zakim> 4. Resource Timing [from plh]
18:03:52 <yoav> present+ yoav
18:04:02 <plh> present+ plh
18:04:09 <plh> present+ todd
18:04:30 <plh> agenda?
18:04:56 <plh> zakim, move to next agendum
18:04:56 <Zakim> agendum 4. "Resource Timing" taken up [from plh]
18:05:06 <plh> https://github.com/w3c/resource-timing/pull/51
18:06:06 <igrigorik> preview: https://rawgit.com/w3c/resource-timing/continuous-idl/index.html
18:07:17 <plh> Ilya: looked an interesting approach
18:07:24 <plh> ... left some comments
18:12:11 <plh> Todd: *bodySize and nextHopProtocol doesn't seem to be implemented
18:12:44 <plh> Ilya: maybe in Firefox
18:13:15 <igrigorik> https://bugzilla.mozilla.org/show_bug.cgi?id=1154309
18:13:25 <plh> plh: stable is 44
18:13:30 <plh> Ilya: it's marked for 45
18:18:01 <plh> plh: cn we ship HRT, PT, RT, NT, and UT as a batch?
18:18:08 <plh> ... at least a subset of it
18:19:02 <plh> Todd: we'd like all UAs to implement the most recent RECs, but they'll implement whatever they can
18:22:38 <plh> plh: I'll make a proposal
18:22:47 <plh> zakim, move to next agendum
18:22:47 <Zakim> agendum 5. "Beacon" taken up [from plh]
18:23:00 <plh>  https://github.com/w3c/beacon/pull/27#issuecomment-187404075
18:23:35 <toddreifsteck> https://github.com/w3c/beacon/pull/27
18:23:58 <plh> Todd: I'm ok with fetchBeacon
18:24:22 <plh> Ilya: method = POST, body nil as default
18:24:29 <plh> ... headers?
18:25:05 <plh> ... make sense to have but still needs to think
18:25:43 <plh> ... fetchBeacon doesn't return anything...
18:25:47 <plh> ... return true/false
18:26:19 <plh> ... which indicates if it was queued
18:26:49 <plh> Todd: yes, would be exact same. we validate method/headers/body and return true if ok
18:27:18 <plh> Ilya: would developers expect a Promise, ie should we return a resolved Promise?
18:27:34 <plh> Todd: added async code on unload seems like a bad idea
18:29:24 <plh> Ilya: should we cc Domenic to look at this?
18:29:30 <plh> ... or Anne
18:30:17 <plh> ... we should consider aligning with Fetch on the return value
18:30:29 <plh> Todd: ok
18:31:07 <plh> Todd: re headers, should we keep it?
18:31:15 <plh> Ilya: I think it's fine
18:32:36 <plh> ... Fetch will set some of the headers for us
18:32:47 <plh> ... so should be optional
18:32:52 <plh> and we're passing it through
18:33:53 <plh> Todd: I'll sort it out later today
18:35:10 <plh> zakim, move to next agendum
18:35:10 <Zakim> agendum 6. "Preload" taken up [from plh]
18:35:23 <plh> https://github.com/w3c/preload/issues/32#issuecomment-190243646
18:36:02 <plh> Yoav: while implementing and testing preload, ran into fonts
18:36:21 <plh> ... crossorigin attribute got in the way
18:37:46 <plh> Ilya: you're trying to preload a font
18:38:18 <plh> ... link ref=preload crossorigin href=http://same-origin
18:38:30 <plh> ... crossorigin is meaningless here
18:38:46 <plh> Yoav: not sure about that
18:38:56 <plh> ... let's assume that for now
18:39:19 <plh> Ilya: if the browser issues a 3xxx to another origin
18:39:41 <plh> ... then the crossorigin becomes relevant
18:39:51 <plh> Yoav: agreed
18:40:02 <plh> ... for non-redirect, they should match
18:40:58 <plh> Ilya: if the rec is to always have crossorigin attribute and the response from same-origin
18:41:08 <plh> ... will that match my @font-face?
18:42:49 <plh> Yoav: asking to put crossorigin on same-origin is weird.
18:43:07 <plh> Ilya: this may trigger different cookies behaviors
18:45:10 <plh> Topic: s/type/as/ attribute
18:45:25 <igrigorik> https://github.com/w3c/preload/pull/59
18:46:32 <plh> Ilya: I got confused while trying to fix the spec and I'd like to restore the old logic and introduces as
18:47:20 <plh> Yoav: if you change from one image format to an other, should we trigger a new request?
18:47:30 <plh> ... because we're changing the client logic?
18:47:49 <plh> Ilya: ok. type only afects if it got triggers in the first place
18:48:14 <plh> Yoav: if you want to trgigger a different download, you should change something else, type won't be enough
18:48:48 <plh> ... if it was fetched type won't matter
18:48:59 <plh> Ilya: checking the html spec...
18:49:10 <plh> Yoav: I filed some bugs around that
18:49:32 <plh> Ilya: html has 2 items for type
18:49:39 <plh> ... and we're mirroring that
18:49:41 <igrigorik> https://html.spec.whatwg.org/#concept-link-obtain
18:50:04 <igrigorik> https://html.spec.whatwg.org/#link-type-stylesheet
18:52:12 <plh> Ilya: ok, will drop the first point from the PR
18:52:23 <plh> ... but we'll keep both type/as
18:52:56 <plh> Tp[oc: Reporting
18:53:01 <plh> Topic: Reporting
18:53:21 <plh> http://w3c.github.io/reporting/
18:55:33 <plh> Plh: I'll set up the repo for automatic bikeshed generation
18:55:51 <plh> ILya: new CSP spec is using it
18:56:01 <plh> ... I'd like to push out the first draft to get feedback
18:58:15 <plh> Todd: it's a subset of NEL
18:58:30 <plh> plh: are ok to adop and publish a FPWD?
18:58:39 <plh> Todd: looks fine
18:58:41 <plh> Yoav: fine
18:58:48 <plh> Resolved: publish as FPWD
18:59:17 <plh> Topic: hr-time
18:59:30 <plh> Todd: when you're up in Seattle and be around a whiteboard
18:59:36 <plh> Ilya: ok
18:59:45 <plh> Topic: Velocity
19:00:04 <plh> Ilya: we are currently scheduled for second day for keynote
19:00:10 <plh> ... looking to reschedule on first day
19:00:29 <plh> .. full day meetup thing seems unlikely
19:00:51 <plh> ... option: move keynote on first day and do a BOF in the evening
19:01:27 <plh> ... option 2: during lunch hour, they have office hours. we could do office hours after our keynote
19:01:35 <plh> ... but setup isn't the best
19:02:30 <plh> ... option 3: find a meeting room but we would compete with other scheduled meetings
19:02:56 <plh> yoav: 1 & 3 sounds reasonnable. 1 sounds the best
19:03:11 <plh> ... 2 doesn't sound productive
19:03:43 <plh> Todd: +1 to Yoav
19:04:09 <plh> Plh: ditto
19:04:38 <plh> ok, preference is 1, 3, 2
19:07:47 <plh> Topic: Next meeting
19:07:56 <plh> March 23rd, 10am PT?
19:07:58 <plh> plh to check
19:43:32 <yoav> yoav has joined #webperf
20:01:25 <yoav> yoav has joined #webperf
20:40:09 <rniwa> rniwa has joined #webperf
22:10:15 <yoav> yoav has joined #webperf
22:14:38 <yoav> yoav has joined #webperf