23:55:32 RRSAgent has joined #webperf 23:55:32 logging to http://www.w3.org/2015/10/26-webperf-irc 23:55:59 Zakim has joined #webperf 23:59:34 RRSAgent, make logs world 23:59:36 Zakim, this will be web-per 23:59:36 I do not see a conference matching that name scheduled within the next hour, trackbot 23:59:37 Meeting: Web Performance Working Group Teleconference 23:59:37 Date: 26 October 2015 00:02:12 bkardell_ has joined #WebPerf 00:11:45 schuki has joined #webperf 00:13:26 moto has joined #webperf 00:14:02 stakagi has joined #webperf 00:14:55 yoav has joined #webperf 00:15:21 yubo has joined #webperf 00:15:29 minami_ has joined #webperf 00:16:38 npdoty has joined #webperf 00:22:50 npdoty has joined #webperf 00:25:47 hellojintae has joined #webperf 00:26:02 plh has joined #webperf 00:27:27 npdoty has joined #webperf 00:28:42 Topic: Frame timing 00:29:12 yoav: I believe Intersection observer will help answer my RUM use cases 00:29:35 ... still need to talk to David Baron about :visited 00:29:54 rniwa has joined #webperf 00:32:18 Ilya: looking at implementation feedback 00:32:45 Todd: new proposal needs to be circulated within MS 00:33:03 ... current proposal seems acceptable 00:34:01 Ilya: google and firefox did implementations of the first prosal 00:34:07 s/prosal/proposal/ 00:35:13 jinbyung has joined #webperf 00:35:46 moto has joined #webperf 00:35:58 ACTION: plh to clean up frame timing 00:35:58 Created ACTION-166 - Clean up frame timing [on Philippe Le Hégaret - due 2015-11-03]. 00:37:31 Topic: Page Visibility 00:40:06 https://github.com/w3c/page-visibility/pull/16 00:40:27 Todd: you could merge the PR for the time being while still figuring if we got the right task source 00:41:21 ... do we have tests for PV? 00:41:39 ... our interop is weak when you include life cycles 00:42:14 Ilya: firefox fires a transition from visible to hidden when the page is being unloaded 00:43:43 plh: we need a test for prerender 00:44:07 ACTION: plh to look into testing prerender in Page Visibility 00:44:07 Created ACTION-167 - Look into testing prerender in page visibility [on Philippe Le Hégaret - due 2015-11-03]. 00:45:49 Ilya: in FF, they fire hidden hidden in all cases 00:47:29 Ilya: I don't think we need to transition when it's unloaded 00:48:02 ... we could tell devs that they should always listen to visibility events, ie background transition or close tabs 00:48:10 ... but that's handle pagehide 00:48:20 s/pagehide/by pagehide/ 00:48:48 ... ie we could use a combination of visitibilityState and pagehide 00:50:11 https://github.com/w3c/page-visibility/issues/18 00:52:15 Ilya: no explicit definition of when the page is unloaded 00:52:23 ... with the new update 00:52:31 speculation that an example in the spec might have lead to hidden being true while a tab is being unloaded in some implementations 00:56:05 [discussion regarding differences between pagehide and unload] 00:56:51 Resolved: publish page visbility as a Wording Draft 00:57:04 s/Wording Draft/Working Draft/ 00:57:08 ACTION: plh to publish PV2 00:57:08 Created ACTION-168 - Publish pv2 [on Philippe Le Hégaret - due 2015-11-03]. 00:57:52 Topic: preload 00:59:20 Ilya: implemented in blink. needs to get it shipped and align in the spec. 00:59:27 ... need to talk to the webkit folks 00:59:58 ... push and preload don't connect bu there are some use cases for preload that can be resolved with push 01:00:04 s/bu/but/ 01:02:18 ... http://www.w3.org/TR/preload/#issue-1 01:02:40 ... we need to define the caching more formaly 01:04:13 ... there is magic there 01:05:30 ... we retain the page for the navigation session if no cache is requested 01:05:37 ... if preload is activated 01:06:03 ... fetch needs tobe aware since the subsequent fetch will need to take it into account 01:06:51 yoav: in terms of interop, do prefetch live for the duration of the next navigation? 01:08:14 Todd: we don't do preload and preconnect yet 01:09:02 Ilya: for preload, it's a declarative fetch, so I don't think we're exposing anything special here in terms of security and privacy 01:10:10 yoav: depending on the cross origin attribute and the as, we would send credentials 01:11:10 hellojintae has joined #webperf 01:11:53 ilya: if I do a preload with as image, no credentials. if I add crossorigin, we'll add them 01:15:20 plh: maybe we should say that preload is equivalent to adding an image 01:17:18 nick: can we list what it means to be equivalent? 01:17:32 plh: we would be duplicating other specs by doing so. 01:17:37 ... nit the right approach imho 01:17:41 s/nit/not/ 01:18:25 yoav: the only difference here is that these fetch don't block and can start early 01:18:57 ... header based csp are taking into account 01:20:06 ilya: we don't say that we process the csp headers are processed atomically 01:20:59 http://www.w3.org/TR/resource-hints/#security-and-privacy 01:23:26 yoav: csp can prevent from the preload to happen 01:23:55 ... csp is about protecting the html, not the link headers 01:24:24 ilya: if you start touse link headers, you should move the csp into link headers as well 01:27:14 ilya: fetch was updated to add a check at the exit 01:29:05 ... the ordering of link/meta between preload and csp isn't relevant. the implementation may do preemptive fetch on preload and have to discard it because of csp 01:29:22 Roy has joined #webperf 01:30:42 ... the question here because the impact on caching 01:31:56 Topic: Beacon 01:33:58 Ilya: step 10 of processing model 01:34:01 ... the mode is "CORS" 01:34:17 ... it means the origin you send the request must respond with two headers 01:34:56 ... ... we don't care about the response 01:35:13 ... we should change it not to use "CORS" 01:35:21 ... we need to check that we're not breaking anything 01:35:35 ... otherwise we're forcing the origin to respond with dynamic headers 01:35:42 Todd: indeed, it's unecessary 01:36:05 ... for the spec, you would preflight and not send the POST 01:36:59 Ilya: there could be a beacon-age 01:37:06 ... that nobody implements 01:37:14 ... but it would force a preflight 01:37:32 ... it also depends on the content type 01:37:39 ... a blob would trigger a preflight 01:38:40 nick: form submission implies no new headers 01:41:01 minami has joined #webperf 01:41:09 ... so due to beacon-age and content type, we're increasing the potential attack area 01:41:54 moto has joined #webperf 01:41:58 ... servers have to accomodate POST request from crossorigin that look like post submission 01:42:20 ... but if you get things that aren't like post submission, that's different 01:43:31 yoav: I've never seen crf protection as a strick headers check 01:44:08 nick: the conditions we have in cors. we're changing the assumption on form submissions. 01:44:48 yoav: can we include the beacon age in the data? 01:45:00 plh: no because we allow abitrary load 01:46:52 s/load/post/ 01:47:55 todd: if we remove beacon-age and restrict to form-data, we are the same as forms 01:48:17 nick: it wouldn't create new attack surfaces indeed 01:49:01 plh: are we llike xhr then? 01:49:06 yoav: no, because of cors 01:50:28 nicK; you could force cors, ie preflight request 01:51:11 todd: can we make it beacon age a simple header? 01:51:44 nick: user agents dont preflight in case of new headers 01:51:55 ... (according to Jonas) 01:52:53 ilya: we should clarify beacon-age with respect with user agents habits 01:53:09 s/habits/added headers/ 01:53:23 ... are user agent addefd headers treated simple headers 01:53:36 (that's issue 1) 01:54:11 Todd: should with only send form-data , even if it's a blob 01:54:29 nick: that seems confusing 01:55:01 ilya: I don't think we have telemetry on media type usage for beacon 01:55:22 ... half the time, people just send a uri 01:55:34 ... the whole payload thing isn't use 01:55:43 s/use/used/ 01:56:27 todd: folks with more advanced payload are probably sending json 01:57:01 ilya: the fetch spec doesn't do anything smart with json object 01:57:20 todd: ie you're responsible for the serilization and then fetch send a string 01:57:23 ilya: correct 01:57:49 nick: if you send a different content type, you culd incurred the preflight 01:58:06 todd: cost is non-trivial 01:59:16 stakagi has joined #webperf 02:00:14 ilya: current implementation aren't doing preflight 02:00:27 ... if type comes from a blob 02:00:40 plh: so we're breaking CORS and fetch specs then 02:02:04 yoav: I understand when you don't arbitrary headers, but the mime types... 02:02:33 ... I think the restriction on mime types is uncessary 02:03:44 plh: we should stop by the webapp secs 02:03:57 ... and talk about this over with them 02:05:18 [Todd is updating https://github.com/w3c/beacon/issues/10 ] 02:06:34 moto_ has joined #webperf 02:07:13 Nick: https://github.com/w3c/beacon/issues/9 02:07:55 mishizaw has joined #webperf 02:08:56 Nick: "This specification defines an interoperable means for site developers to asynchronously transfer small HTTP data from the User Agent to a web server." 02:09:04 ... doesn't say what the spec does 02:09:28 editorial comments in this email: https://lists.w3.org/Archives/Public/public-web-perf/2014Jul/0109.html 02:09:42 not small and "asynchronous" doesn't quite capture what the spec is about 02:10:21 nick: separate privacy considerations from security considerations 02:10:43 ... privacy concern is the browser making a request on you behalf after you closed the page 02:10:52 ... are the users going to be aware of that? 02:11:06 .... similar geafencing 02:11:21 bartek__ has joined #webperf 02:11:21 ... you might have a different IP adress 02:12:08 ... we had a discussion about this in web platform yesterday but no conclusion 02:12:18 ... at the very least, we should mention it in the privacy section 02:12:41 ilya: we don't want to block on unload 02:12:47 .... ie avoid sync XHR 02:13:02 ... you can use beacon to send things every 2 hours 02:13:22 todd: with beacon-age, you have the ability to send it much later 02:13:29 ... but no one implements it 02:14:19 nick: we need some guidances to implementrs on what to tell the users when sending a quest after the close 02:14:44 bob has joined #webperf 02:14:48 yoav: how is that different from background syncs in service workers? 02:14:52 nick: same issue :) 02:15:18 todd: it may be simplier to spec it down for the short term 02:16:09 ilya: agents could pile up beacons to wait for the next network request 02:16:39 ilya: perharps we should more clearly define beacon-age? 02:16:46 ... what are the use cases for beacon age? 02:17:24 nick: the processing model speaks about multiple attempts 02:17:43 todd: but with service workers, it seems handled now 02:18:32 plh: at the minimum, we should say it's sent after the close 02:18:56 nick: even if we say it's equivalent to an existing practice, it would affect users 02:24:19 nick: do UAs have the option to desactivate beacon? 02:24:55 plh: no, like we don't have the option to desactivate XHR. Beacon is generic, not restricted to telemetry data 02:25:10 ilya: we limit body size in chrome 02:26:34 nick: if it's only used for telemetry, what do you do in private mode? 02:27:57 hellojintae has joined #webperf 02:27:57 Zakim has left #webperf 02:28:45 ... you might want to add a note in privacy sectio that you considered the case of giving the user the ability to desactivate beacons and decided against it. 02:29:20 I'm not sure you want to say that the user can't have the ability to deactivate it, just because it's obviously true that user agents can turn off beacon functionality or do whatever the user wants 02:29:56 but you could explain why you're not putting conditions on when Beacon is used, because you think there is an advantage to users on the whole 02:30:44 ilya: btw, our size limit is 64Kb 02:32:09 Topic: Network Error Logging 02:32:43 scribenick: npdoty 02:32:58 looking at the open issues 02:34:23 ilya: how are the NEL requests treated? client requests? 02:34:38 ... NEL. you as an origin have registered to receive error reports 02:34:56 ... some site embeds your widget, and you want to know when your social media widget has failed to load 02:35:13 ... but if the embedding site has a service worker that intercepts requests 02:35:34 ... the service worker might pass through the request, which might fail 02:35:58 ... the report shouldn't be sent to the embedding site owner, but to the widget owner 02:36:23 ... any other report should be treated as client requests which bypass service workers 02:36:48 todd: should we go over network error logging in more detail? 02:37:39 ilya: lots of things could go wrong: DNS failures, route issues, etc. you as a site owner have no way to observe that this failure happened 02:38:04 ... large vendors have nodes around the world that will ping their site to try to identify these failures and work around them 02:38:22 ... NEL is supposed to notify you that we have failed to reach your site 02:39:44 ... specify a report-uri on a first successful reach, the report-uri should be a different domain, on a different subnet, etc. 02:39:55 @@: would be good to have more than one endpoint 02:40:02 ilya: yes, we do support that, with fallback through the list 02:40:37 ... modified after HSTS, can note that it applies to all subdomains as well 02:41:27 ... a well-structured report of failure, including the resolving IP address 02:41:59 @@: have a list of items in notes that I would like in addition 02:42:15 todd: would be great to have those as Github issues 02:42:45 ilya: are the errors that we define here reasonable? 02:43:01 ... this is restricted to HTTPS origins, and the report location must also be HTTPS 02:43:53 [note, "trustworthy origins" is out of date terminology] 02:44:16 ilya: noticed that we have multiple places in the Web platform that are delivering reports 02:44:29 ... would like to extract that into one common thing, a group of report uris 02:44:46 ... then other specs can reference this to say, "queue a report to group Security" 02:45:59 s/@@/Bartek/g 02:46:15 rrsagent, generate minutes 02:46:15 I have made the request to generate http://www.w3.org/2015/10/26-webperf-minutes.html plh 02:50:23 npdoty has joined #webperf 02:51:13 todd: privacy questions regarding these general out of band reporting mechanisms? 02:51:25 npdoty: sure, it was debated regarding csp, for example 02:51:49 plh: we could say for this spec, the user agent should provide a way to disable NEL 02:52:26 ... worth it to mention in the NEL spec that user agents should provide a way to disable NEL reports 02:52:33 ... question about whether SHOULD or MAY 02:53:10 ilya: the out of band reporting just has general restrictions, like clearing the cache 02:53:42 ... but for particular specs that have reporting, they should specify when to send requests, when they might not want to 02:53:58 ... the general out of band reporting is just under mkwest's repo for now 02:55:31 Bartek: what if we have reporting list not as a fallback, but simultaneous to more endpoints for auditing purposes? 02:55:38 ilya: could you do that yourself? 02:55:57 Bartek: you could, and it would be more efficient, but auditors might want independent reports 02:56:55 ... for example, if ads are served from within our origin 02:57:41 ilya: the fact that the user agent delivers it doesn't make it provably, just a convenience 02:57:51 ... wouldn't want to open it up to a very large list 02:59:26 Bartek: potentially lack of trust between parties 03:01:58 mishizaw has joined #webperf 03:02:05 todd: if there are particular regulatory requirements, that might make it easier 03:02:16 ... what if we had a concrete number: 2 or 3 03:10:28 npdoty has joined #webperf 03:10:43 npdoty: can we provide the assumption that error reporting uri's should be common across users? if so, it would make it easier to detect abuse for supercookies 03:11:02 yoav has joined #webperf 03:11:15 ilya: there are use cases where you would want the value to differ, between regions, for example 03:11:36 bartek__: could also have the report-uri in the DNS record (as a TXT record, say) 03:11:53 ... as a fallback if you never successfully reached the server 03:12:18 ilya: interesting, please raise 03:13:33 todd: could ship with a pre-loaded list in browsers, like with HSTS pre-load list 03:14:42 bartek__: dns should be considered as a fallback, just in case you can't load the policy on first load 03:14:55 [humorous tangent about how much policy can be pushed into DNS records] 03:15:45 ilya: don't typically load all DNS TXT records 03:15:55 npdoty: but would only need to when you had a network failure 03:17:43 ... DNS doesn't give you the security of HTTPS 03:17:56 ilya: yeah, so DNSSEC? 03:18:38 ... some information is reported that others wouldn't have received 03:19:23 [agenda discussion] 03:20:31 rrsagent, please draft minutes 03:20:31 I have made the request to generate http://www.w3.org/2015/10/26-webperf-minutes.html npdoty 03:42:57 hellojintae has joined #webperf 04:22:43 rniwa has joined #webperf 04:23:14 mishizaw has joined #webperf 04:24:04 primer -> http://siusin.github.io/perf-timing-primer/ 04:24:12 plh has joined #webperf 04:24:20 ToddReifsteck has joined #webperf 04:24:30 primer -> http://siusin.github.io/perf-timing-primer/ 04:24:43 yoav has joined #webperf 04:27:04 Roy has joined #webperf 04:31:20 npdoty has joined #webperf 04:32:34 mnot has joined #webperf 04:37:28 Andy's waterfall repo: https://github.com/andydavies/waterfall 04:39:35 npdoty has left #webperf 04:42:32 mishizaw has joined #webperf 04:44:40 https://github.com/addyosmani/timing.js/ 04:44:58 mnot has joined #webperf 04:48:47 mishizaw has joined #webperf 05:03:26 Topic: CustomPerformanceEntry 05:03:57 Yoav: how about we allow apps to add their own performance entry objects in the timeline so that one can observe those? 05:04:02 s/Yoav/Ilya/ 05:05:38 Todd: that would allow the use case of adding your own payload to an entry 05:06:13 ... sounds cool 05:06:30 ... and it cleans up the story around clear* 05:08:21 plh: we should open an issue/feature request 05:08:51 Ilya: I'll open one 05:10:38 https://github.com/w3c/user-timing/issues/3 05:14:37 Ilya: but it means we would allow huge payload into the observers and those are doing deep clones... 05:20:55 Topic: redirects 05:21:10 Ilya: besides security/privacy, what's the hold? 05:21:30 Todd: not a high priority 05:22:38 Ilya: we already reveal the fact that there was at least on redirect (since we return 0) 05:22:46 ... but we don't say how many 05:28:14 scribe: xiaoqian 05:31:30 plh: is this what you meant? -> //TAO only Redirect Timing{ URL } 05:31:58 Ilya: Not exactly. 05:32:27 yoav: just the entries 05:33:01 plh: Resource Timing{ 05:33:15 ... redirectCount; 05:33:27 ... redirect URL 05:33:29 ... } 05:38:51 plh: if I have two with the same name 05:39:53 yoav: you can link everything back together 05:42:16 yoav: If you go to HTTP server, we can expose it 05:42:46 ... expose Redirect there will be a concern 05:43:21 todd: you couldn't make guess 05:45:39 mishizaw has joined #webperf 05:50:52 plh: change 2 attrs only, redirectend and redirect start 05:51:40 Ilya: yeah, drop them 05:53:28 todd: you are also missing info about the chain 05:53:39 yoav: if redirect, you can change your cookie 05:57:31 rniwa has joined #webperf 06:00:06 mnot has joined #webperf 06:01:47 plh: if I have a redirect in the middle 06:01:58 Ilya: it will take longer 06:02:07 plh: I won’t get url in the end, so I won’t expose that 06:02:21 yoav: you can measure the time you took 06:03:46 Roy has joined #webperf 06:07:52 yoav: if you want to avoid this expose privacy problem, you will have to remove from a lot html 06:07:53 stakagi has joined #webperf 06:08:02 todd: that’s why we hide a lot of redirects 06:08:53 ... image people are choosing to expose, can we add the feature? 06:09:14 yoav has joined #webperf 06:10:45 ... if a website choose redirect as feature... 06:11:10 ... can you get the data? with xhr? 06:12:26 Yoav: if you site tell you to expose, redirects maybe the same pattern 06:12:49 ... TAO is already used today 06:13:05 Todd: Google phone has already turn TAO on 06:14:37 Yoav: If FB has no interest to expose TAO 06:14:52 Ilya: their widget do 06:15:03 Yoav: if we review all the redirect there, will it be private proper? 06:16:58 yoav: let bring it to the Security folks 06:17:30 yoav has joined #webperf 06:18:11 todd: strange to turn it on... go to log in server, use cookie, user redirect just not enough 06:18:52 Ilya: this question is a block of a lot of others 06:19:14 ... privacy issue will be a major change to the API 06:19:39 todd: I'd not recommend change the API in this way, what about NT-2? 06:21:21 plh: unless we are told NT do not get into the buffer 06:22:00 todd: more entries? 06:22:19 Ilya: back cases are ad force users to change 06:22:39 ... when you click those links, you are force to change 06:23:14 plh: any option is not to change RT and NT, and provide another entry 06:23:45 ... listen to resource, will have to do sth to get redirect 06:23:59 todd: have buffer on server time 06:24:19 Ilya: leave it as it is 06:25:06 ... for those new to the API, just look at Observer 06:25:20 Todd: yeah, historical reasons 06:26:19 plh: entry type for redirect will be what? 06:26:24 Ilya: resource 06:26:35 ... call it a new thing? 06:27:27 hellojintae has joined #webperf 06:27:39 Todd: that will cause sudden changes for redirects in timeline 06:28:22 ... RT with TAO, if no TAO, no redirects 06:28:45 plh: keep redirectCount in RT 06:28:53 Ilya: we need a new name 06:30:03 plh: get a R-entry for A 06:30:48 Ilya: B, C will never be seem today, name for B's entry will have some info about A 06:31:48 plh: if a is a fresh start C 06:32:12 Ilya: it should be the fetch start of A 06:32:21 s/fresh/fetch 06:48:40 yoav has joined #webperf 07:02:11 mishizaw has joined #webperf 07:02:48 yoav: people will assume that /TR is not the latest draft 07:03:07 plh: that's not true with the auto-publication system 07:06:20 topic: publication work flow 07:07:50 plh: our goal is try to apply the auto-pub system and have as less worry as possible 07:08:11 mishizaw has joined #webperf 07:08:15 todd: which are the spec we want to move? 07:08:54 plh: hr-2, pr-2 07:09:27 todd: pr-2 is a clean up for the failures in pr-1? 07:09:50 ... how about RT? 07:10:01 plh: never shop a level 1 07:10:11 s/shop/shipped 07:10:39 todd: but 3 vendors implement it 07:11:15 plh: but it relies on PR-2, may need a clean-up version, but not touch the ED 07:13:05 Todd: User Timing? 3 implementations 07:13:13 plh: That's already a REC 07:13:34 ... UT-2, same as RT, need a subset 07:13:59 Todd: already UT REC, not sure that's necessary to subset UT 07:15:03 ... for the specs blocked by performance Observer, how long do we need to wait? 07:15:24 Ilya: We don't know the intention of Moz yet 07:16:16 plh: HR-2, need a test for worker. PR-2, need to clean up the test suite 07:16:53 Todd: We have written quite a few test in the past 6 month, we'd like to share them with W3C 07:18:02 ... but there are a lot of spec corner cases in those cases 07:18:19 plh: Do we want to write test case for corner cases? 07:18:46 mnot has joined #webperf 07:21:24 ... Beacon, will need to write another python module under w-p-t 07:22:13 s/python module/python parser 07:22:35 mishizaw has joined #webperf 07:22:57 ... I will need to fire an issue, and James will add support for that 07:23:49 yoav: there are some blink test for Beacon. How do you get resource response in w-p-t? 07:24:25 plh: I wrote a test that can explain the process 07:24:58 Roy__ has joined #webperf 07:27:08 Ilya: RIC, no update on implementation 07:27:15 Todd: It's on my list 07:29:39 todd: Beacon in apps, what if it's closed? f.ex. WebView 07:30:10 Ilya: Independent to vendors 07:33:20 Todd: Resource Hints... 07:33:50 plh: How can we prove implementation? 07:34:21 ... how about a pre-fetch from the server? 07:36:30 todd: browsers can be triggered... 07:36:45 yoav: pre-connect should be a separate host 07:37:15 todd: need a new case for each attribute 07:37:58 plh: We'll need commons from WebDriver folks 07:38:11 s/commons/commends 07:42:00 Todd: pre-fetch and pre-render are implemented by Firefox 07:43:25 mnot has joined #webperf 07:43:52 plh: Is it possible for you to write a query for the usage? 07:43:59 Todd: not sure 07:47:52 ... pre-connect smells the highest one 07:48:35 Ilya: It isn't ready yet 07:51:03 ... the issue refers to Fetch 07:51:59 todd: same as SW 07:58:55 Ilya: Telconf ... any complain? 07:59:10 Yoav: I can do later 07:59:44 todd: it's difficult to schedule a time from Asia and the chairs 08:00:32 hellojintae has joined #webperf 08:04:36 resolve: 1 hour early 08:05:31 todd: we should switch goal for the next charter 08:06:48 Ilya: we got feedback from Moz 08:07:32 plh: we can do some minor update, add the primer 08:07:41 todd: and Memory API 08:08:21 Ilya: we should start from use cases 08:10:00 yoav: let's create a report and collect use cases 08:10:44 Ilya: a general use case report 08:10:48 mishizaw has joined #webperf 08:11:10 plh: we have a repo for WebPerf, which is a good place for that report 08:11:33 RRSAgent, make minutes 08:11:33 I have made the request to generate http://www.w3.org/2015/10/26-webperf-minutes.html xiaoqian 08:13:57 plh has left #webperf 08:18:46 yoav has joined #webperf 08:32:29 cristi has joined #webperf 12:12:55 yoav has joined #webperf 13:10:50 yoav has joined #webperf 13:13:46 Roy has joined #webperf 13:24:00 mishizaw has joined #webperf 13:24:43 mnot has joined #webperf 14:24:08 mnot has joined #webperf 14:30:30 yoav has joined #webperf 15:16:10 mishizaw has joined #webperf 16:17:19 mishizaw has joined #webperf 16:27:56 Roy has joined #webperf 17:19:42 mishizaw has joined #webperf 18:20:53 mishizaw has joined #webperf 18:55:18 yoav has joined #webperf 19:21:39 mishizaw has joined #webperf 21:02:42 yoav has joined #webperf 21:15:54 mishizaw has joined #webperf 21:45:01 yoav has joined #webperf 21:58:17 Roy has joined #webperf 22:26:39 mishizaw has joined #webperf 22:50:54 yoav has joined #webperf 22:51:55 Roy has joined #webperf 23:17:05 yoav has joined #webperf 23:28:28 Roy has joined #webperf 23:30:12 yoav has joined #webperf 23:35:31 plh has joined #webperf 00:29:32 mnot has joined #webperf 00:46:07 yoav_ has joined #webperf 01:03:48 rniwa has joined #webperf 01:38:44 mnot has joined #webperf 01:39:31 plh has joined #webperf 01:40:05 hellojintae has joined #webperf 01:40:16 Roy has joined #webperf 01:41:41 mishizaw has joined #webperf 01:48:49 yoav has joined #webperf 01:52:22 stakagi has joined #webperf 02:06:29 yoav has joined #webperf 02:08:51 mishizaw has joined #webperf 02:12:43 rniwa has joined #webperf 02:13:53 mishizaw has joined #webperf 02:22:54 mishizaw has joined #webperf 03:37:06 stakagi has joined #webperf 03:44:02 hellojintae has joined #webperf 04:23:58 yoav has joined #webperf 04:25:56 mnot has joined #webperf 04:28:43 stakagi has joined #webperf 04:31:20 rniwa has joined #webperf 04:38:38 mishizaw has joined #webperf 04:39:11 hellojin_ has joined #webperf 04:50:38 plh has joined #webperf 05:08:30 yoav has joined #webperf 05:12:24 mishizaw has joined #webperf 05:14:38 mnot has left #webperf 05:38:58 mishizaw has joined #webperf 05:43:07 hellojintae has joined #webperf 05:44:00 plh has joined #webperf 05:44:16 rniwa has joined #webperf 05:44:30 yoav has joined #webperf 05:52:36 stakagi has joined #webperf 06:09:24 hellojin_ has joined #webperf 06:24:36 mishizaw has joined #webperf 06:44:59 stakagi has joined #webperf 07:03:04 mishizaw has joined #webperf 07:06:54 yoav has joined #webperf 07:10:42 plh has joined #webperf 07:46:51 stakagi has joined #webperf 07:57:38 mishizaw has joined #webperf 08:09:07 mishizaw has joined #webperf 08:11:16 stakagi has joined #webperf 08:15:56 mishizaw has joined #webperf 08:44:43 cristi has joined #webperf 09:19:54 stakagi has joined #webperf 13:11:37 hellojintae has joined #webperf 13:15:16 hellojintae has joined #webperf 14:02:18 mishizaw has joined #webperf 14:30:30 mishizaw has joined #webperf 14:51:04 yoav has joined #webperf 15:31:40 mishizaw has joined #webperf 17:05:38 mishizaw has joined #webperf 18:06:41 mishizaw has joined #webperf 19:07:37 mishizaw has joined #webperf 21:09:20 mishizaw has joined #webperf 22:10:45 stakagi has joined #webperf 22:22:14 yoav has joined #webperf 22:31:35 mishizaw has joined #webperf 22:39:26 stakagi_ has joined #webperf 23:54:26 plh has joined #webperf 23:56:27 hellojintae has joined #webperf 23:59:25 stakagi has joined #webperf 00:05:51 rniwa has joined #webperf 00:17:34 mishizaw has joined #webperf 00:32:47 yoav has joined #webperf 00:49:13 mishizaw has joined #webperf 01:24:31 yoav has joined #webperf 01:25:21 mishizaw has joined #webperf 01:28:49 yoav has joined #webperf 01:46:17 mishizaw has joined #webperf 01:50:49 hellojintae has joined #webperf 01:58:23 mishizaw has joined #webperf 02:06:22 mishizaw has joined #webperf 03:53:59 yoav has joined #webperf 04:02:10 hellojintae has joined #webperf 04:16:21 rniwa has joined #webperf 04:17:55 stakagi has joined #webperf 04:22:24 plh has joined #webperf 04:37:53 mishizaw has joined #webperf 05:26:02 rniwa has joined #webperf 05:29:05 mishizaw has joined #webperf 06:00:38 mishizaw has joined #webperf 06:08:44 hellojintae has joined #webperf 06:19:03 yoav has joined #webperf 06:43:05 yoav has joined #webperf 06:57:20 stakagi has joined #webperf 07:20:23 mishizaw has joined #webperf 07:56:21 yoav has joined #webperf 08:09:38 mishizaw has joined #webperf 08:55:31 mishizaw has joined #webperf 11:15:30 cristi has joined #webperf 12:06:44 mishizaw has joined #webperf 13:19:08 yoav has joined #webperf 13:22:35 yoav has joined #webperf 13:25:13 hellojintae has joined #webperf 13:33:10 hellojintae has joined #webperf 13:34:05 hellojin_ has joined #webperf 14:25:47 mishizaw has joined #webperf 14:29:04 hellojintae has joined #webperf 14:54:43 mishizaw has joined #webperf 14:59:13 eliperelman has joined #webperf 15:28:09 mishizaw has joined #webperf 17:00:41 mishizaw has joined #webperf