IRC log of webperf on 2013-11-14

Timestamps are in UTC.

00:37:42 [RRSAgent]
RRSAgent has joined #webperf
00:37:42 [RRSAgent]
logging to http://www.w3.org/2013/11/14-webperf-irc
00:37:44 [trackbot]
RRSAgent, make logs world
00:37:44 [Zakim]
Zakim has joined #webperf
00:37:46 [trackbot]
Zakim, this will be WPWG
00:37:46 [Zakim]
I do not see a conference matching that name scheduled within the next hour, trackbot
00:37:47 [trackbot]
Meeting: Web Performance Working Group Teleconference
00:37:48 [trackbot]
Date: 14 November 2013
00:46:31 [plh]
plh has joined #webperf
00:48:42 [JatinderMann_]
present+ JatinderMann
00:49:02 [JatinderMann_]
present+ PanDeng
00:49:48 [plh]
hi Jatinder
00:49:57 [plh]
I'm on the podium at the AC right
00:50:06 [plh]
let me know when you're ready to start
00:50:09 [JatinderMann_]
Hi Philippe
00:50:12 [JatinderMann_]
Okay, sound's good
00:50:13 [plh]
and I'll come in the room
00:53:59 [JatinderMann_]
We're just waiting for more people to join. So far it's Pan and I.
00:56:34 [Pan]
Pan has joined #webperf
01:00:53 [thinker]
thinker has joined #webperf
01:01:18 [JatinderMann_]
present+ thinker
01:04:33 [plh3]
plh3 has joined #webperf
01:04:56 [AutomatedTester]
AutomatedTester has joined #webperf
01:07:54 [kkubota2]
kkubota2 has joined #webperf
01:08:49 [Sam_]
Sam_ has joined #webperf
01:09:21 [JatinderMann_]
present+ plh3
01:09:32 [JatinderMann_]
present+ AutomatedTester
01:09:39 [JatinderMann_]
present+ kkubota2
01:09:46 [JatinderMann_]
present+ Sam_
01:15:05 [plh3]
join #webperf
01:16:00 [plh]
Jatinder Mann
01:16:00 [plh]
Pan Deng
01:16:42 [plh]
Lei Xue
01:17:01 [Alois]
Alois has joined #webperf
01:17:04 [plh]
?, Tencent
01:17:11 [plh]
kkubota2, NTT
01:17:22 [plh]
Mark Nottingham, Akamais
01:17:28 [plh]
s/ais/ai/
01:17:40 [plh]
Renoir Boulanger, W3C
01:17:48 [plh]
David Burns, Mozilla
01:18:22 [plh]
Alois Reitbauer
01:18:28 [plh]
Jason Weber
01:18:44 [plh]
Sam ?, Foxconn
01:18:56 [plh]
Arvind Jain
01:19:47 [plh]
Topic: Prerender
01:20:10 [plh]
Jatinder: should HTML5 include prerender?
01:20:36 [plh]
... feedback is that we should just consider doing it on microformats
01:21:22 [plh]
... but it seems worthwhile to have it part of the spec
01:21:34 [plh]
... one feedback
01:21:50 [plh]
... around if you replace the current browsing context
01:21:59 [plh]
... if you loose "replace" you loose such constraint
01:24:53 [JatinderMann_]
Jatinder: Based on the bug, this was accepted to be added to HTML5.1. Are we okay with moving to HTML5 or leave it HTML5.1
01:25:41 [JatinderMann_]
Plh: We will need to give test cases if we want this put in. Are we okay with just leaving this?
01:25:55 [wonsuk]
wonsuk has joined #webperf
01:26:38 [rniwa]
rniwa has joined #webperf
01:26:45 [JatinderMann_]
Arvind: Ilya raised a resource hints proposal on preconnect, preload, prerender
01:27:19 [JatinderMann_]
http://lists.w3.org/Archives/Public/public-web-perf/2013Nov/0043.html
01:28:04 [JatinderMann_]
Arvind: As we had discussed in the past, we may want to keep some of this as browser optimizations
01:29:04 [JatinderMann_]
Jason: Some of these are environment specific optimizations. I'm not sure we want to require browsers to explain all the details.
01:29:23 [JatinderMann_]
Arvind: What's preload and preconnect? Are these new?
01:29:37 [JatinderMann_]
Jatinder: It's unclear if some of these are just renaming prefetch or something new.
01:29:52 [JatinderMann_]
Plh: It might be worthwhile to specify this in the spec so developers know what to expect
01:30:32 [JatinderMann_]
Jason: Depending on environment, like if you're on 3G, you may not want to do these optimizations.
01:31:57 [JatinderMann_]
Arvind: Ilya just asked questions here, there weren't any recommendations on the number. As Jason mentioned, the number of connections is hard to specify depending on device and enviroment. I recommend we just leave it as is, but if someone can justify having a specific number then we can add it to the them.
01:32:50 [JatinderMann_]
Jatinder: Prefetch is already defined and so is prerender. Are we really trying to define a preconnect
01:33:32 [JatinderMann_]
Jason: IE already has an internal database where its checking when to do a preconnect. It doesn't make sense to have a developer give this hint.
01:34:19 [sho]
sho has joined #webperf
01:34:32 [ken]
ken has joined #webperf
01:34:53 [JatinderMann_]
Arvind: in some cases the browser may not get to a resource fast enough, with a hint we can do something sooner. If you take an example of search engine, it can potentially benefit by specifying a preconnect.
01:35:24 [kkubota2_]
kkubota2_ has joined #webperf
01:35:26 [JatinderMann_]
Jatinder: But at parse time the browser will encounter the preconnect attribute at the same time as it encounters the URL.
01:35:38 [JatinderMann_]
Jason: this may be more useful for the second page.
01:36:24 [JatinderMann_]
Arvind: This might be a very light weight version of prerender.
01:37:02 [JatinderMann_]
Arvind: We should make sure this that the spec includes this. The registry includes prerender and the spec includes prefetch.
01:37:43 [JatinderMann_]
Jason: IE supports preconnect on a heuristics base. I believe its some 80% hit rate of determining which one is going to be preconnected
01:38:10 [JatinderMann_]
Jatinder: Are we leaning towards defining preconnect?
01:38:21 [plh]
plh has changed the topic to: Agenda: http://www.w3.org/wiki/Web_Performance/November2013Meeting
01:38:30 [JatinderMann_]
Jason: I would caution beucase the developer may shoot themselves on the foot.
01:39:02 [renoirb]
renoirb has joined #webperf
01:39:07 [JatinderMann_]
dns-pretetch
01:39:51 [arvind]
arvind has joined #webperf
01:39:55 [arvind]
https://docs.google.com/presentation/d/18zlAdKAxnc51y_kj-6sWLmnjl6TLnaru_WH0LJTjP-o/present#slide=id.g33211238_0_2
01:40:27 [bin_lee]
bin_lee has joined #webperf
01:42:06 [JatinderMann_]
Arvind: Based on Ilya's slides, there is "dns-prefetch", "prefetch", "prerender", "subresource". At least "prerender" and "prefetch" are supported everyone. "subresource" is unnecessary
01:44:31 [JatinderMann_]
Jatinder: I don't think there is any web developer value in giving the specifics on when the browser prerenders. The goal is to have the developer give the web browser a hint.
01:44:47 [JatinderMann_]
Arvind: I think we should wait and see if others have more concrete requirements.
01:45:20 [JatinderMann_]
Arvind: We should decide on whether or not we should define more states.
01:45:37 [JatinderMann_]
Arvind: Looks like some of us aren't happy in defining too many more.
01:47:28 [JatinderMann_]
Jason: As of IE11, we support the dns-prefetch tag.
01:48:38 [arvind]
values
01:48:42 [plh3]
plh3 has joined #webperf
01:48:47 [arvind]
http://microformats.org/wiki/existing-rel-values
01:49:44 [Sam__]
Sam__ has joined #webperf
01:49:59 [JatinderMann_]
Arvind: Looks like we currently have prefetch in the HTML5 spec, prerender and dns-prefetch is in the registry.
01:50:45 [JatinderMann_]
...I think it makes sense to bring in preconnect if dns-prefetch is there. dns-prefetch is the lowest cost, preconnect is a bit more work where we're opening the connection, prefetch will download the resource end to end, and prerender navigates to the page. Seems like it makes sense.
01:52:15 [JatinderMann_]
Jatinder: We should discuss with HTML5 WG to include dns-prefetch and prerender.
01:52:23 [JatinderMann_]
Arvind: We should discuss all four with the HTML WG.
01:52:47 [JatinderMann_]
ACTION Jatinder include prerender, dns-prefetch in HTML5 spec and consider preconnect as well
01:52:47 [trackbot]
Created ACTION-112 - Include prerender, dns-prefetch in html5 spec and consider preconnect as well [on Jatinder Mann - due 2013-11-21].
01:53:14 [JatinderMann_]
Jatinder: That's all of our open items. Does anyone else have any other questions?
01:54:03 [JatinderMann_]
thinker: I worry if prerender can be used for denial of service type attacks
01:55:15 [JatinderMann_]
Arvind: The page can always do a DoS attack. You can always just add the second frame as an iframe already. That will accomplish the same thing.
01:55:41 [JatinderMann_]
thinker: I think we should put same origin restrictions.
01:56:32 [JatinderMann_]
Arvind: Most of the current use cases are for cross-origins, e.g., a search engine would use the cross-origin prerenders. Both Microsoft and Google are using this in their search engines. I don't think this creates any new surface area because you can already do this.
01:57:21 [JatinderMann_]
Jason: There are two parts of this privacy and security. There isn't a new attack vector here just as Arvind mentions. The second problem is using up user's resources by prerendering excessively. I think that's up to the User Agent to be smart
01:58:15 [JatinderMann_]
...about how it prerenders. Chrome and IE both limit the prerenders.
01:58:44 [JatinderMann_]
Topic: Beacon
01:59:01 [JatinderMann_]
Arvind: We should probably start by talking about the goals of beacon and what isn't already solved by XHR.
02:00:09 [JatinderMann_]
Jason: What I'm most excited about beacon is asynchronously sending data when its convienent. Today sites are using XHR by blocking the site's unload to send the data.
02:00:50 [JatinderMann_]
...This is super ugly because it destroys power and perf. The browser internally can try to do optimizations, but it has to do continue doing work in the background.
02:02:03 [JatinderMann_]
Jatinder: I would also mention that it really slows down the navigation of the next page. And there is nothing the next page can do.
02:02:34 [Daniel_Austin]
Daniel_Austin has joined #webperf
02:02:50 [JatinderMann_]
Alois: What many people are doing is abusing the img element to send the data, or a sync XHR to really guarantee sending the data. The problem that beacon should solve is sending the data reliably without blocking the page.
02:03:11 [JatinderMann_]
Arvind: I agree that XHR doesn't solve this problem and beacon can solve this and is sufficiently different.
02:04:06 [JatinderMann_]
Arvind: I agree with the use case of reporting statistics without blocking the page. The use cases that I don't agree with are the battery usage or getting data.
02:05:08 [JatinderMann_]
...There was some suggestion that if you want to batch sending data, we may want to develop a resource batching mechanism that XHR can benefit from.
02:06:13 [jeroskim]
jeroskim has joined #webperf
02:06:31 [JatinderMann_]
Alois: I feel like a lot was brought into the spec, like the battery case and sending a lot of background data. I think we should scope.
02:07:50 [JatinderMann_]
Jatinder: Phillipe raised that some people were interested in abusing to use this send large amounts of data.
02:08:42 [JatinderMann_]
Arvind: Let's start by talking about the size limitations.
02:09:51 [JatinderMann_]
Arvind: Fixed values may look silly in the future.
02:09:59 [JatinderMann_]
Jatinder: Does XHR have a limit?
02:10:03 [JatinderMann_]
Arvind: No.
02:10:22 [JatinderMann_]
Jatinder: But XHR doesn't live after the page has gone away. But beacon can survive.
02:11:24 [plh]
plh has joined #webperf
02:11:36 [JatinderMann_]
Arvind: 10K is too small.
02:11:42 [Daniel_Austin]
q+ Daniel_Austin
02:12:03 [Yudong]
Yudong has joined #webperf
02:13:09 [JatinderMann_]
Arvind: Uploading 10GBs will cost you money on your mobile page. So I see a point here.
02:14:47 [JatinderMann_]
Arvind: The current solution of spinning is the worse case, as it blocks the unload and you can send as much data as you want.
02:15:35 [hayato_]
hayato_ has joined #webperf
02:15:41 [JatinderMann_]
Alois: We can also not include this in the spec, but the browser fails silently.
02:16:24 [JatinderMann_]
Plh: I don't think we should put a limit in the spec, but should be allow the ability to query data.
02:18:33 [JatinderMann_]
Daniel: The upload speeds are slower than download speed. Paypal are a serial XHR abuser. What we've found is that the omniture data is lost. The third point is that we've seen in the past serious abuse where we did not specify limits. Iniitally there weren't any limits on cookie data and people were sending 65K data. UAs started adding arbirtary limits on cookies. We have lost a lot of money as this, because some of our users weren't able to send.
02:19:09 [JatinderMann_]
...I think we should specify a limit. I just checked how much 25K with 6 different XHRs. Let's set a limit but keep it a rational limit.
02:19:33 [JatinderMann_]
Arvind: Should the limit be applied at a page level or function level?
02:20:30 [JatinderMann_]
Daniel: It should be on a page level. We make multiple calls to omniture. Maybe some of the service worker framework some of this can be used.
02:20:51 [JatinderMann_]
Arvind: What about a way to query?
02:20:58 [JatinderMann_]
Plh: I don't think it was a good idea afterall.
02:21:03 [JatinderMann_]
Jason: Agreed.
02:21:06 [JatinderMann_]
Daniel: Agreed.
02:22:56 [JatinderMann_]
Alois: What about single page applications? After 20 minutes you can't send any more data.
02:23:59 [JatinderMann_]
Daniel: We should set the limit to kilobytes rather than megabytes, especially from a mobile operator point of view.
02:26:12 [JatinderMann_]
Jason: We are developing a general purpose platform. We should be careful to set limits.
02:26:29 [JatinderMann_]
Jatinder: We have to keep in mind that we want to keep adoption of this API and have people move away from XHR.
02:27:19 [JatinderMann_]
Arvind: Partical example. In Google we track clicks using ping when people are clicking on links. Even minor amounts of data loss, you may not use it.
02:29:17 [ken]
ken has joined #webperf
02:29:46 [JatinderMann_]
Daniel: I want my developers to use good practices, but real large scale companies can easily abuse this. I can commonly see marketing folks add yet another analytics data they want to send up. If managing bandwidth should be up to us.
02:30:22 [JatinderMann_]
Jatinder: Arvind mentioned whether this should be limited to unload or else. I think this should be a general purpose async method that can be called at any time in the page.
02:30:46 [JatinderMann_]
Alois: We have found that data is sent at many times in the page, though unload is most common. I think we should be sent at any time.
02:30:51 [JatinderMann_]
Arvind: I agree as well.
02:31:09 [JatinderMann_]
Arvind: I don't think we should add any batching details in the spec about battery life.
02:31:42 [JatinderMann_]
Jason: I think when you send the beacon, the UA adds the beacon to a queue to send as soon as it can asynchronously send. It should be lower priority than other items.
02:32:15 [JatinderMann_]
Arvind: I agree with that. I think the spec should remove the battery life use cases.
02:32:41 [JatinderMann_]
ACTION Jatinder update beacon use cases to just be the asynchronous data sending case
02:32:41 [trackbot]
Created ACTION-113 - Update beacon use cases to just be the asynchronous data sending case [on Jatinder Mann - due 2013-11-21].
02:33:13 [JatinderMann_]
Arvind: Let's talk about retry. XHRs don't retry right?
02:33:25 [JatinderMann_]
Alois: Yep, they just return a failure code, doesn't retry.
02:34:27 [JatinderMann_]
Arvind: I think we all agree that we shouldn't return a return code.
02:34:33 [JatinderMann_]
Arvind: What are the retry semantics?
02:35:43 [JatinderMann_]
Jason: We should leave this to the quality of implementation.
02:35:53 [JatinderMann_]
Arvind: The mechanism has to be robust to actually use it.
02:37:52 [JatinderMann_]
Alois: The browser may crash not an issue, the server may not be able to accept that's okay too. What about when there is no internet connection.
02:40:01 [JatinderMann_]
Alois: I think after 10 minutes the data is useless anyway. Some marketing folks may want to hold data longer.
02:40:35 [JatinderMann_]
Jason: I recommend we leave the text quite general and let the user agent may try best effort while maintaining privacy and security.
02:40:51 [JatinderMann_]
Arvind: We may want to add examples in the notes.
02:43:36 [JatinderMann_]
Daniel: I just checked what our paypal beacon does on my mobile device. It is 26K. It's using Google Analytics and Omniture.
02:44:03 [JatinderMann_]
Daniel: We will just not use beacon if it has 10K limit.
02:47:00 [JatinderMann_]
Jason: Let me give an example of data URI. Initially it has a 32k limit. We were spec compliant it was great. But developers were sending larger data URI and IE was failing. Now we have a larger limit and sites work. I don't think we should add any limits. Let the browser set the limit.
02:48:19 [JatinderMann_]
Arvind: We have closed on a few issues. The beacon should have no limit. The spec shouldn't specify retry logic, but we may consider adding a note in the future. The spec should remove batching logic.
02:49:31 [JatinderMann_]
Arvind: I also don't think we should include get. This adds complexity. Its not the common use case.
02:49:34 [taocai]
taocai has joined #webperf
02:49:52 [JatinderMann_]
Arvind: I think POST should be the only method.
02:50:37 [JatinderMann_]
Alois: I think we should limit to POST as well.
02:50:53 [JatinderMann_]
Jatinder: Let's solve the problem we intended to solve. Let's only stick with POST.
02:51:07 [JatinderMann_]
ACTION Jatinder Update beacon spec to have no limits, no retry logic, no batching, POST is the only method.
02:51:07 [trackbot]
Created ACTION-114 - Update beacon spec to have no limits, no retry logic, no batching, post is the only method. [on Jatinder Mann - due 2013-11-21].
02:51:59 [JatinderMann_]
Daniel: I just checked, and Microsoft.com uses 22KB beacon.
02:52:29 [JatinderMann_]
Daniel: Best effort felt like the best security and privacy method.
02:53:50 [renoirb]
Suggestion: How about allowing HEAD too, backend might not want to have to create a full document.
02:53:54 [myakura]
myakura has joined #webperf
02:54:18 [JatinderMann_]
Arvind: There can be DNS failure, connect failure, server failure. What should you try for these?
02:55:53 [renoirb]
Forget about it, sending state update using only URL would not be sufficient.
02:56:10 [JatinderMann_]
Arvind: For server busy, I may want to try once or twice right away. We have done some data analysis on this where we found that a single retry significantly incraeses reliability (e.g., if you have a 1% failure rate and you retry once, you'll have a 0.5% impact).
02:56:25 [JatinderMann_]
Arvind: I think a random retry for all of these failures may be worthwhile.
02:57:11 [JatinderMann_]
Daniel: I know some data carriers block uploads while you're on the call. So it blocks that.
03:14:53 [plh3]
plh3 has joined #webperf
03:15:12 [JatinderMann_]
ACTION Arvind Can beacon response set a cookie and if so, is it treated as a first or third party cookie write
03:15:12 [trackbot]
Created ACTION-115 - Can beacon response set a cookie and if so, is it treated as a first or third party cookie write [on Arvind Jain - due 2013-11-21].
03:18:41 [ito]
ito has joined #webperf
03:23:37 [aizu]
aizu has joined #webperf
03:24:24 [a12u]
a12u has joined #webperf
03:24:27 [Alois]
Alois has joined #webperf
03:26:01 [JatinderMann_]
Topic: Resource Priorities
03:26:49 [myakura]
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/ResourcePriorities/Overview.html
03:27:30 [taocai]
taocai has joined #webperf
03:27:53 [rniwa]
rniwa has joined #webperf
03:28:30 [Daniel_Austin]
adding a link to the Serviceworker proposal to the notes - of possible interest for the beacon discussion: https://github.com/slightlyoff/ServiceWorker/blob/master/explainer.md
03:32:01 [joshpeek]
joshpeek has joined #webperf
03:33:51 [JatinderMann_]
Alois: If you have a postpone on the background image, we don't know that the element is visible yet until we do styling.
03:33:52 [ken]
ken has joined #webperf
03:34:49 [plh]
plh has joined #webperf
03:35:14 [JatinderMann_]
Jason: IE doesn't even download the resources from CSS until the formatting is done.
03:36:50 [sho]
sho has joined #webperf
03:37:23 [JatinderMann_]
Jason: I think we should remove the postpone CSS property as the browser will already do this work.
03:38:23 [rniwa_]
rniwa_ has joined #webperf
03:38:28 [JatinderMann_]
Anna: In many cases, its hard to know when the image will be in the page.
03:41:40 [plh]
s/Anna/Anne/
03:44:00 [masatakayakura]
masatakayakura has joined #webperf
03:52:26 [johnny___]
johnny___ has joined #webperf
03:55:14 [JatinderMann_]
Jason: Seems like there is agreement that there is a need for lazyload / postpone, but there may be some confusion in the spec.
03:55:19 [JatinderMann_]
Anne: I think I agree with that.
03:58:56 [JatinderMann_]
Jatinder: Looks like we need to remove the CSS property.
03:59:08 [Alois]
preload none on video http://www.w3schools.com/tags/att_video_preload.asp
04:00:19 [junil]
junil has joined #webperf
04:00:24 [JatinderMann_]
Jason: I think we should scope this to lazyload and then consider adding postpone later on in an Level 2 based on feedback.
04:01:11 [JatinderMann_]
Anne: I think we should consider starting with lazyload. For example, the user agent could interpret lazyload to mean postpone based on data.
04:02:07 [masatakayakura]
https://github.com/slightlyoff/ServiceWorker/blob/master/explainer.md
04:06:41 [slightlyoff]
I can be summoned by meme...
04:06:42 [AutomatedTester]
AutomatedTester has joined #webperf
04:06:45 [slightlyoff]
;-)
04:14:55 [JatinderMann_]
Off to lunch break.
04:15:15 [Zakim]
Zakim has left #webperf
04:15:35 [ken]
ken has joined #webperf
04:37:51 [ito]
ito has left #webperf
04:48:52 [johnny]
johnny has joined #webperf
05:11:06 [johnny__]
johnny__ has joined #webperf
05:13:08 [Alois]
Alois has joined #webperf
05:13:45 [simonste_]
simonste_ has joined #webperf
05:14:47 [johnny]
johnny has joined #webperf
05:17:24 [Sam]
Sam has joined #webperf
05:18:23 [AutomatedTester]
AutomatedTester has joined #webperf
05:18:51 [annevk]
annevk has joined #webperf
05:18:54 [simonste_]
Hello
05:19:02 [annevk]
\o/
05:19:37 [JatinderMann]
JatinderMann has joined #webperf
05:19:44 [annevk]
wb
05:19:58 [JatinderMann_]
JatinderMann_ has joined #WebPerf
05:20:24 [JatinderMann_]
Topic: Page Visibility
05:21:51 [plh]
plh has joined #webperf
05:22:34 [junil]
junil has joined #webperf
05:25:56 [Pan]
Pan has joined #webperf
05:26:02 [danielkim]
danielkim has joined #webperf
05:26:02 [a12u]
a12u has joined #webperf
05:26:09 [ken]
ken has joined #webperf
05:26:35 [aizu]
aizu has joined #webperf
05:27:18 [myakura]
myakura has joined #webperf
05:28:26 [simonstewart]
The WebDriver spec had a bash at attempting to define visibility: http://www.w3.org/TR/webdriver/#determining-visibility
05:28:29 [JatinderMann_]
Jatinder: We need to define visibility in Level 2 spec. Is it fine to tie visibility to the viewport or the users agent's intrepretation of the viewport.
05:29:04 [JatinderMann_]
Jason: We should tie it to the viewport, which is what the user sees. Tying it to the user agent's internal intrepretation just seems to add complexity.
05:29:49 [pmsangal]
pmsangal has joined #webperf
05:31:36 [JatinderMann_]
Arvind: I think we need to cover give more details on the definition, including display:none.
05:32:55 [ken_]
ken_ has joined #webperf
05:33:04 [pmsangal]
Hi. Is there a phone bridge, for TPAC, that I can dial into?
05:33:05 [Daniel_Austin]
Daniel_Austin has joined #webperf
05:34:01 [rniwa]
rniwa has joined #webperf
05:35:21 [JatinderMann_]
Simon: We need to define element visibility for Web Driver.
05:37:13 [arvind]
arvind has joined #webperf
05:37:15 [arvind]
http://lists.w3.org/Archives/Public/public-web-perf/2013Oct/0031.html
05:37:28 [plh]
pmsangal, yes, there is
05:37:51 [plh]
zakim, room for 4 for 240 minutes?
05:37:54 [Zakim]
Zakim has joined #webperf
05:37:59 [plh]
zakim, room for 4 for 240 minutes?
05:38:00 [Zakim]
ok, plh; conference Team_(webperf)05:37Z scheduled with code 26631 (CONF1) for 240 minutes until 0937Z
05:38:20 [plh]
zakim, call wuzhou-middle
05:38:20 [Zakim]
I am sorry, plh; I do not know a number for wuzhou-middle
05:38:27 [plh]
zakim, call wuzhou-_iddle
05:38:27 [Zakim]
I am sorry, plh; I do not know a number for wuzhou-_iddle
05:38:31 [plh]
zakim, call wuzhou_iddle
05:38:31 [Zakim]
I am sorry, plh; I do not know a number for wuzhou_iddle
05:38:37 [plh]
zakim, call wuzhou_middle
05:38:37 [Zakim]
ok, plh; the call is being made
05:38:38 [Zakim]
Team_(webperf)05:37Z has now started
05:38:39 [Zakim]
+Wuzhou_middle
05:39:00 [plh]
zakim, passcode?
05:39:00 [Zakim]
the conference code is 26631 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), plh
05:39:13 [plh]
pmsangal, we're on the bridge now
05:39:23 [pmsangal]
thanks, I'll dial in
05:40:02 [Zakim]
+ +1.617.294.aaaa
05:40:04 [Zakim]
- +1.617.294.aaaa
05:40:04 [Zakim]
+ +1.617.294.aaaa
05:40:42 [JatinderMann_]
Simon: We should really call our spec as displayability, instead of visibility.
05:40:45 [Zakim]
- +1.617.294.aaaa
05:42:13 [Zakim]
+ +1.617.294.aabb
05:42:15 [Zakim]
- +1.617.294.aabb
05:42:15 [Zakim]
+ +1.617.294.aabb
05:42:23 [JatinderMann_]
Jason: From the advertising point of view, they want proper element visibilty that gives them with high confidence that the ad is on or off screen.
05:43:07 [pmsangal]
ok I'm in, but I don't hear anything. Is the line muted?
05:43:45 [plh]
nope, it's not muted :(
05:43:48 [Zakim]
-Wuzhou_middle
05:43:50 [simonstewart]
I'm finding this flash discussion really interesting.
05:43:54 [plh]
oops
05:43:58 [plh]
we got dropped
05:44:07 [plh]
zakim, call wuzhou_middle
05:44:07 [Zakim]
ok, plh; the call is being made
05:44:09 [Zakim]
+Wuzhou_middle
05:44:30 [JatinderMann_]
Jason: Today, advertisers use many techniques to determine visibility, including flash.
05:44:33 [plh]
zakim, drop wuzhou
05:44:33 [Zakim]
Wuzhou_middle is being disconnected
05:44:34 [Zakim]
-Wuzhou_middle
05:44:37 [plh]
zakim, call wuzhou_middle
05:44:37 [Zakim]
ok, plh; the call is being made
05:44:39 [Zakim]
+Wuzhou_middle
05:45:22 [plh]
zakim, mute aabb
05:45:22 [Zakim]
+1.617.294.aabb should now be muted
05:45:23 [JatinderMann_]
Jason: We can probably define it as a layout level displayable, but I don't know if I'd call it visibility.
05:45:47 [plh]
pmsangal, I muted you since we were able to hear you
05:46:12 [pmsangal]
Sorry about that. I'm in now, thx
05:46:21 [plh]
zakim, aabb is pmsangal
05:46:22 [Zakim]
+pmsangal; got it
05:46:47 [plh]
it's a big room and not everybody is sitting next to the polycom :(
05:47:17 [JatinderMann_]
Arvind: I think element visibility is harder. I rather think about iframe visibility.
05:47:40 [JatinderMann_]
Anne: Isn't it the same issue as element visibility?
05:47:53 [pmsangal]
plh: np, I'll try for sometime. If I can't make out what's happening, over the phone, I'll drop off and attend the next TPAC in person :)
05:48:26 [rniwa]
rniwa has joined #webperf
05:50:02 [JatinderMann_]
Jason: From a display point of view, it's the same problem.
05:51:13 [igarashi]
igarashi has joined #webperf
05:52:11 [igarashi]
igarashi has left #webperf
05:54:39 [simonstewart]
One other thing to keep in mind: http://dev.w3.org/csswg/cssom-view/#extensions-to-the-document-interface
05:55:43 [simonstewart]
The intention here is that "getElementFromPoint" would return the top-most "visible" element. With a slightly better nuancing.
05:55:51 [sho]
sho has joined #webperf
05:56:42 [AutomatedTester]
simonstewart: it returns the hittable element
05:56:52 [simonstewart]
Right
05:57:13 [simonstewart]
s/"visbible" element/"hittable" element/
05:57:20 [kkubota2]
kkubota2 has joined #webperf
05:58:30 [JatinderMann_]
Jatinder: For Page Visibility L1, when we say you are hidden, we are certain that you are hidden. When we say that your are visible, you may or may not be visible.
05:59:10 [JatinderMann_]
Jatinder: Should we apply the same principal to the L2 spec?
06:00:40 [simonstewart]
JatinderMann_: that definition might well work for WebDriver. We already have a fairly loose definition of visibility.
06:00:51 [rniwa]
rniwa has joined #webperf
06:00:53 [JatinderMann_]
Jason: You can give layout information like your width and display, but that's not necessarily what the display sees
06:01:06 [myakura]
myakura has joined #webperf
06:01:30 [dennisdmac_]
dennisdmac_ has joined #webperf
06:02:05 [JatinderMann_]
Anne: We should follow up with CSS folks and see if they want to support this.
06:02:33 [JatinderMann_]
Jason: We can possibly provide the layout properties and let them know if there is a transform applied.
06:04:35 [JatinderMann_]
Jason: If you have an Ad in the center of the page. If you have the CSS transform to 1px, there is no way to make sure that the Ad is no visible, because that's happening on the GPU. So we can give layout coordinates and a boolean api that lets them know if there are css transforms or other graphics techniques. This could be enough solution to solve the advertiser scenario.
06:04:47 [JatinderMann_]
Simon: The Web Driver could also use that potentially.
06:05:29 [mz-modeltaxi]
mz-modeltaxi has joined #webperf
06:05:49 [taocai]
taocai has joined #webperf
06:07:25 [JatinderMann_]
Jatinder: Is there a scenario where we want the current Page Visibility L2 spec where visibility is tied to the document and not the top level document.
06:09:22 [JatinderMann_]
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/HighResolutionTime2/Overview.html
06:09:23 [aizu]
aizu has joined #webperf
06:11:14 [JatinderMann_]
Topic: High Resolution Time
06:11:25 [JatinderMann_]
Anne: Can we remove the NoInterfaceObject
06:11:26 [JatinderMann_]
?
06:11:49 [JatinderMann_]
Jatinder: Yes, I can remove.
06:11:58 [JatinderMann_]
Plh: Can we move to Last CAll?
06:12:01 [JatinderMann_]
Jatinder: Yes.
06:12:16 [plh]
Resolved: HRT 2 to Last Call
06:14:07 [johnny]
johnny has joined #webperf
06:14:56 [JatinderMann_]
Topic: Navigation Error Logging
06:15:14 [JatinderMann_]
Daniel: I prefer having detailed errors, not just the general errors.
06:16:18 [JatinderMann_]
Daniel: Today, we have to have many tools to determine error cases, I'm still going to be stuck with getting those errors. I don't think general errors are good enough, we need explicit errors.
06:17:23 [JatinderMann_]
...There were a number of proposals to solve this. We had looked at a bunch of different lists of errors, including POSIX.
06:19:24 [JatinderMann_]
...The POSIX spec doesn't define any of the errors in very specific ways, so different machines give different error numbers. I don't feel these lists are useful.
06:19:46 [JatinderMann_]
Jatinder: Does it make sense for us to define a list of errors we want to support in our spec?
06:20:29 [ken]
ken has joined #webperf
06:24:19 [plh]
http://lists.w3.org/Archives/Public/public-web-perf/2013Apr/0007.html
06:28:13 [JatinderMann_]
Anne: That's why we don't want to share errors in XHR. This topic has come up before many times before, and it's always been shot down.
06:29:10 [Daniel_Austin]
http://lists.w3.org/Archives/Public/public-web-perf/2013May/0053.html
06:29:31 [JatinderMann_]
Anne: You may want to do a security review.
06:31:28 [JatinderMann_]
Alois: We may want to ask the security team both whether its a problem to share the detailed and not detailed security information.
06:31:45 [Daniel_Austin]
http://lists.w3.org/Archives/Public/public-web-perf/2013Apr/0007.html
06:32:17 [JatinderMann_]
ACTION Jatinder Do review to see if sharing these network errors is a security or privacy concern
06:32:18 [trackbot]
Created ACTION-116 - Do review to see if sharing these network errors is a security or privacy concern [on Jatinder Mann - due 2013-11-21].
06:33:06 [Zakim]
-pmsangal
06:34:47 [JatinderMann_]
Mark: There are issues that we need to consider about standarizing a list. How do we handle new errors that have been created. We may want to consider black or whitelisting errors in the registry.
06:35:26 [ken]
ken has joined #webperf
06:36:55 [Zakim]
-Wuzhou_middle
06:36:56 [Zakim]
Team_(webperf)05:37Z has ended
06:36:56 [Zakim]
Attendees were Wuzhou_middle, +1.617.294.aaaa, +1.617.294.aabb, pmsangal
06:37:55 [JatinderMann_]
Mark: Instead of having one field, we may have two fields to make it easier.
06:38:08 [JatinderMann_]
Jatinder: We are very open to API surface.
06:39:52 [JatinderMann_]
Jatinder: Which one of these errors are we not concerned with?
06:39:53 [yahui]
yahui has joined #webperf
06:40:00 [JatinderMann_]
http://lists.w3.org/Archives/Public/public-web-perf/2013Apr/att-0007/WebRequestStatusCodes4.html
06:41:07 [pmsangal]
pmsangal has joined #webperf
06:41:58 [JatinderMann_]
Mark: 200s are fine, a lot of these are fine. Some of these that give more information on the user should be a problem.
06:44:18 [johnny_]
johnny_ has joined #webperf
06:48:37 [JatinderMann_]
Arvind: Some folks are Google are interested in reporting the errors to a different URL.
06:49:07 [JatinderMann_]
Alois: This makes a lot more sense. Because if you're going to see the problem after its fixed, then this API is useful.
06:49:19 [JatinderMann_]
Anne: Coordinate with the CSP guys.
06:49:35 [JatinderMann_]
Arvind: This would just be like report URI.
06:50:33 [plh]
rrsagent, this meeting spans midnight
06:51:43 [JatinderMann_]
ACTION Arvind add method to allow ability to send to a third party URL using CSP
06:51:43 [trackbot]
Created ACTION-117 - Add method to allow ability to send to a third party url using csp [on Arvind Jain - due 2013-11-21].
06:52:51 [wilhelm]
wilhelm has joined #webperf
06:53:35 [JatinderMann_]
ACTION Mark to review the error list and reduce it down
06:53:36 [trackbot]
Created ACTION-118 - Review the error list and reduce it down [on Mark Nottingham - due 2013-11-21].
06:56:01 [JatinderMann_]
Topic: Resource Timing
06:56:17 [JatinderMann_]
http://www.w3.org/2013/11/cr-resource-timing.html
06:58:10 [AndroUser]
AndroUser has joined #webperf
07:02:11 [JatinderMann_]
Arvind: We closed "A resource request without a network connection" feedback from James Simonsen.
07:03:14 [JatinderMann_]
Jatinder: Resource Timing doesn't include resources that have errors. So closing "Resource request: failure and success? (Andy Davies)"
07:06:01 [pmsangal]
pmsangal has joined #webperf
07:10:03 [JatinderMann_]
Plh: We should include a 404 error code test to see if it is included in the resource timing
07:12:30 [myakura]
myakura has joined #webperf
07:14:29 [johnny]
johnny has joined #webperf
07:15:44 [giuseppep]
giuseppep has joined #webperf
07:17:04 [kimwoonyoung]
kimwoonyoung has joined #webperf
07:25:25 [cwdoh_]
cwdoh_ has joined #webperf
07:25:46 [myakura]
myakura has joined #webperf
07:27:29 [plh]
ACTION" mnot to come up with an HTTP2 proposal for R
07:27:45 [plh]
s/R/RT/
07:29:18 [junil_]
junil_ has joined #webperf
07:33:18 [Sam]
Sam has joined #webperf
07:33:48 [cwdoh]
cwdoh has joined #webperf
07:36:03 [JatinderMann_]
Jatinder: We will define Performance in Navigation Timing L2 and extend EventTarget. Resource Timing should reference Navigation Timing L2.
07:42:26 [JatinderMann_]
ACTION Jatinder update Resource Timing to use Navigation Timing L2
07:42:26 [trackbot]
Created ACTION-119 - Update resource timing to use navigation timing l2 [on Jatinder Mann - due 2013-11-21].
07:44:31 [johnny]
johnny has joined #webperf
07:45:58 [JatinderMann_]
Topic: Resource Timing L2
07:46:27 [JatinderMann_]
Jatinder: Should we define the JSON.stringify(performance) in a spec?
07:46:28 [JatinderMann_]
http://lists.w3.org/Archives/Public/public-web-perf/2013Aug/0109.html
07:46:48 [johnny_]
johnny_ has joined #webperf
07:46:50 [ken]
ken has joined #webperf
07:48:32 [johnny]
johnny has joined #webperf
07:52:42 [JatinderMann_]
Anne: WE should define a JSON method.
07:52:46 [plh]
http://w3c-test.org/webperf/specs/ResourceTiming2/
07:52:55 [JatinderMann_]
Plh: In the Performance Timeline L2 spec.
07:53:01 [mnot]
mnot has joined #webperf
07:55:32 [JatinderMann_]
Jatinder: What about web workers support? Should be able to use performance.getEntries in web workers? Resources downloaded by web workers should be included? Should initator type be web worker? Shared worker resources should be put in which timeline? The shared worker's timeline?
07:58:22 [JatinderMann_]
Anne: I think you should include workers as a seperate iframe context. Email WebAppsSec to make sure they're on board.
07:58:30 [JatinderMann_]
JatindeR: I like the feedback. I'll share a proposal.
07:59:04 [cwdoh]
cwdoh has joined #webperf
08:00:45 [cwdoh]
cwdoh has joined #webperf
08:03:39 [plh]
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/PerformanceTimeline/Overview.html#terminology
08:05:00 [JatinderMann_]
jatinder: What about protocol information?
08:05:50 [JatinderMann_]
Mark: We should just return the ALP procotols in the registry.
08:08:41 [mnot]
http://tools.ietf.org/html/draft-ietf-tls-applayerprotoneg-03
08:09:08 [cwdoh]
cwdoh has joined #webperf
08:09:24 [ito]
ito has joined #webperf
08:09:58 [JatinderMann_]
Jatinder: Should we include byte size information?
08:10:30 [Automate_]
Automate_ has joined #webperf
08:11:09 [JatinderMann_]
Anne: Typically with Data URI we're worried about the size, becuase you have to go collect it.
08:13:07 [JatinderMann_]
Mark: There are so many interesting numbers with so many warnings.
08:13:37 [JatinderMann_]
Anne: Sites like Facebook may be interested in seeing what kind of content your different users are seeing.
08:13:57 [JatinderMann_]
Alois: especially for mobile cases, they maybe change the content.
08:17:21 [JatinderMann_]
rrsagent, generate minutes
08:17:21 [RRSAgent]
I have made the request to generate http://www.w3.org/2013/11/14-webperf-minutes.html JatinderMann_
08:17:44 [wonsuk]
wonsuk has joined #webperf
08:19:22 [taocai]
taocai has joined #webperf
08:26:27 [johnny]
johnny has joined #webperf
08:34:30 [joshpeek_]
joshpeek_ has joined #webperf
08:37:05 [kimwoonyoung]
kimwoonyoung has joined #webperf
08:37:48 [kennyluck]
kennyluck has joined #webperf
08:42:57 [rniwa]
rniwa has joined #webperf
08:48:48 [cwdoh]
cwdoh has joined #webperf
08:50:55 [ito]
ito has left #webperf
08:59:09 [Zakim]
Zakim has left #webperf
09:03:34 [sangwhan]
sangwhan has joined #webperf
09:06:25 [kennyluck]
sangwhan, yeah. Is the mini-workshop starting?
09:07:26 [kimwoonyoung]
kimwoonyoung has joined #webperf
09:08:01 [kkubota2]
kkubota2 has joined #webperf
09:08:43 [a12u]
a12u has joined #webperf
09:09:48 [ken]
ken has joined #webperf
09:10:09 [ken]
ken has joined #webperf
09:10:09 [giuseppep]
giuseppep has joined #webperf
09:12:57 [kennyluck]
kennyluck has joined #webperf
09:13:09 [ito]
ito has joined #webperf
09:13:17 [johnny]
johnny has joined #webperf
09:14:30 [tao]
tao has joined #webperf
09:16:42 [sho]
sho has joined #webperf
09:17:37 [a1zu]
a1zu has joined #webperf
09:18:12 [igarashi]
igarashi has joined #webperf
09:20:37 [saki]
saki has joined #webperf
09:27:59 [masatakayakura]
masatakayakura has joined #webperf
09:29:12 [myakura_]
myakura_ has joined #webperf
09:35:28 [cwdoh]
cwdoh has joined #webperf
09:35:49 [kawada]
kawada has joined #webperf
09:43:13 [ito]
ito has left #webperf
09:45:43 [saki]
saki has joined #webperf
09:46:15 [kawada_]
kawada_ has joined #webperf
09:48:55 [cwdoh]
cwdoh has joined #webperf
09:52:53 [igarashi]
igarashi has joined #webperf
09:54:31 [cwdoh]
cwdoh has joined #webperf
09:58:15 [hayato]
hayato has joined #webperf
10:17:20 [myakura]
myakura has joined #webperf
10:30:11 [saki]
saki has joined #webperf
10:31:04 [kennyluck]
sangwhan, my slides is online ☞ http://dev.oupeng.com/wp-content/uploads/20131109-kennyluck-optimizing-js-games.html#namespace-object
11:33:07 [AndroUser]
AndroUser has joined #webperf
11:40:00 [ken]
ken has joined #webperf
12:13:53 [myakura]
myakura has joined #webperf
13:08:56 [kawada]
kawada has joined #webperf
13:30:44 [saki]
saki has joined #webperf
13:32:45 [cwdoh]
cwdoh has joined #webperf
13:54:15 [rniwa]
rniwa has joined #webperf
13:54:33 [saki_]
saki_ has joined #webperf
14:57:33 [kimwoonyoung]
kimwoonyoung has joined #webperf
15:23:06 [cwdoh]
cwdoh has joined #webperf
16:06:49 [cwdoh]
cwdoh has joined #webperf
16:21:08 [cwdoh]
cwdoh has joined #webperf
18:15:21 [myakura]
myakura has joined #webperf
19:19:59 [myakura]
myakura has joined #webperf
20:20:24 [myakura]
myakura has joined #webperf
21:20:49 [myakura]
myakura has joined #webperf
21:31:56 [myakura]
myakura has joined #webperf
22:08:28 [ken]
ken has joined #webperf
00:44:35 [ken_]
ken_ has joined #webperf
01:05:10 [cwdoh]
cwdoh has joined #webperf
01:05:15 [kimwoonyoung]
kimwoonyoung has joined #webperf
01:10:23 [mz-modeltaxi]
mz-modeltaxi has joined #webperf
01:18:34 [igarashi]
igarashi has joined #webperf
01:18:38 [igarashi]
igarashi has left #webperf
01:24:16 [taocai]
taocai has joined #webperf
01:26:34 [plh]
plh has joined #webperf
01:29:15 [rniwa]
rniwa has joined #webperf
01:29:46 [Pan]
Pan has joined #webperf
01:30:57 [plh]
Topic: JavaScript Pre-Flight
01:31:01 [myakura]
myakura has joined #webperf
01:31:07 [plh]
Alois: [explains the use case]
01:31:22 [plh]
... we break pages by injecting JS in it
01:36:19 [junil_]
junil_ has joined #webperf
01:37:23 [plh]
rrsagent, generate minutes
01:37:23 [RRSAgent]
I have made the request to generate http://www.w3.org/2013/11/14-webperf-minutes.html plh
01:37:46 [plh]
[Alois will give poiners to Jason about IE issue]
01:39:06 [plh]
Regrets+ James
01:39:12 [plh]
Chair: Jason, Arvind
01:39:15 [Sam]
Sam has joined #webperf
01:39:15 [plh]
rrsagent, generate minutes
01:39:15 [RRSAgent]
I have made the request to generate http://www.w3.org/2013/11/14-webperf-minutes.html plh
01:40:48 [plh]
Present+ Arvind
01:40:55 [plh]
Present+ Anne
01:41:09 [plh]
rrsagent, generate minutes
01:41:09 [RRSAgent]
I have made the request to generate http://www.w3.org/2013/11/14-webperf-minutes.html plh
01:42:55 [plh]
Alois: we do runtime injection
01:43:22 [plh]
... script tag in HTTP header, ...
01:43:36 [plh]
Jason: it fits into our charter
01:43:44 [a12u]
a12u has joined #webperf
01:43:46 [plh]
... this would help sites
01:43:54 [plh]
.... help with cacheability
01:44:37 [plh]
... a man in the middle attack can do this today
01:45:23 [tao]
tao has joined #webperf
01:45:58 [plh]
Alois: it would have to be sent with every request
01:46:01 [plh]
... ie not cached
01:46:21 [plh]
Jason: on the surface, it seems a good idea
01:46:30 [plh]
... pretty trivial in most user agents
01:49:47 [plh]
Arvind: Alois: header woul only go for the root HTML
01:50:22 [plh]
s/Arvind: Alois/Alois:/
01:50:25 [plh]
s/woul/would/
01:50:57 [plh]
Jason: proposed next step: I'll talk to the SharePoint team
01:51:06 [plh]
... we need to do research on our side
01:51:13 [plh]
... and Arvind will see at Google
01:51:18 [jehoochen_]
jehoochen_ has joined #webperf
01:51:21 [plh]
... Alois should talk to Mark Nottingham
01:52:21 [plh]
ACTION: Jason to get preflight feedback from MS
01:52:21 [trackbot]
Error finding 'Jason'. You can review and register nicknames at <http://www.w3.org/2010/webperf/track/users>.
01:52:31 [plh]
ACTION: Arvind to get preflight feedback from Google
01:52:31 [trackbot]
Created ACTION-120 - Get preflight feedback from google [on Arvind Jain - due 2013-11-22].
01:52:56 [plh]
ACTION: Alois to talk about preflight to mnot
01:52:56 [trackbot]
Created ACTION-121 - Talk about preflight to mnot [on Alois Reitbauer - due 2013-11-22].
01:53:19 [plh]
plh: if feedback positive, we'll contact public-script-coord
01:54:45 [plh]
ACTION: Jatinder to get preflight feedback from MS
01:54:45 [trackbot]
Created ACTION-122 - Get preflight feedback from ms [on Jatinder Mann - due 2013-11-22].
01:54:49 [tcai]
tcai has joined #webperf
01:54:56 [aizu]
aizu has joined #webperf
01:55:02 [plh]
ACTION-122: Jatinder to get Jason to get preflight feedback from MS
01:55:02 [trackbot]
Notes added to ACTION-122 Get preflight feedback from ms.
01:55:27 [AutomatedTester]
AutomatedTester has joined #webperf
01:56:09 [wonsuk]
wonsuk has joined #webperf
02:00:08 [plh]
Alois: running it into a separate worker wouldn't cut it, since we want DOM access
02:00:15 [plh]
... not just timing information
02:00:27 [plh]
Jason: finding a proper name would be good
02:00:56 [plh]
... let's keep with preflight for now
02:01:04 [plh]
s/keep/stick/
02:01:10 [ken]
ken has joined #webperf
02:03:00 [plh]
Topic: HAR
02:03:15 [plh]
Arvind: there is a new revision of the draft coming by end of the month
02:03:42 [plh]
Jason: having the spec documented, as a tool at least.
02:05:24 [plh]
... we always talk about cutting "Web Archive" formats
02:05:37 [plh]
Arvind: I wonder if it makes to have JSON in the saveAs
02:05:44 [plh]
Jason: it's a dev tool option
02:06:04 [Alois]
Alois has joined #webperf
02:06:07 [plh]
plh: it's a waterfall
02:06:52 [Sam]
Sam has joined #webperf
02:07:25 [plh]
Arvind: HAR has more info that the Web performance object
02:07:36 [plh]
... so toJSON isn't enough for HAR
02:07:56 [plh]
... Andy will make the HAR format closely tied to nav timing and resource timing
02:08:38 [cwdoh]
cwdoh has joined #webperf
02:08:48 [plh]
Jason: chrome dev and HTTP archive supports HAR
02:08:59 [plh]
Alois: and a few other tools
02:09:19 [Alois]
HAR Spec: http://www.softwareishard.com/blog/har-12-spec/
02:09:19 [plh]
Arvind: we're working with Ian
02:09:39 [plh]
Arvind: let's see if it works out this time
02:10:57 [plh]
ACTION: Arvind to look into the licensing/IP situation related to HAR
02:10:57 [trackbot]
Created ACTION-123 - Look into the licensing/ip situation related to har [on Arvind Jain - due 2013-11-22].
02:15:39 [plh]
Topic: f2f, workshop
02:15:50 [plh]
Jason: I'd like to do in the bay area next year
02:16:01 [plh]
... we socialize and reach out to companies
02:16:03 [sho]
sho has joined #webperf
02:16:25 [ken]
ken has joined #webperf
02:16:38 [plh]
Alois: would make to get feedback on implementations
02:17:06 [plh]
Jason: I'd like the format we used in November
02:17:17 [cwdoh]
cwdoh has joined #webperf
02:18:28 [plh]
... let's do it the day before or after
02:18:52 [plh]
... I recommend a full day workshop
02:19:05 [plh]
... then do a debrief
02:20:32 [plh]
... 9-3 for the workshop, 3-5 for the webperf
02:20:35 [saki]
saki has joined #webperf
02:20:44 [plh]
Jatinder: if it doesn't fit, we'll do more
02:21:49 [plh]
[Google will be hosting]
02:23:28 [plh]
frequence of teleconferences
02:23:40 [plh]
Arvind: making decisions on the phone are problematic
02:23:47 [plh]
Jatinder: we can be async
02:25:02 [plh]
Arvind: we're missing the history
02:25:37 [plh]
Jatinder: I like to talk things out
02:25:44 [plh]
... but yes, involved others would be good
02:25:50 [plh]
... no one read minutes
02:25:57 [plh]
... but we need to separate decisions
02:27:19 [plh]
... let's meet, make good minutes, and have separate emails for decisions
02:30:41 [plh]
[teleconference time]
02:31:17 [cwdoh]
cwdoh has joined #webperf
02:31:45 [kimwoonyoung]
kimwoonyoung has joined #webperf
02:32:05 [plh]
ACTION: plh to change the teleconf time for 3pm ET
02:32:05 [trackbot]
Created ACTION-124 - Change the teleconf time for 3pm et [on Philippe Le Hégaret - due 2013-11-22].
02:33:12 [a1zu]
a1zu has joined #webperf
02:35:53 [sho]
sho has joined #webperf
02:35:54 [plh]
Topic: New specs
02:36:31 [plh]
Jason: two things: power
02:36:41 [plh]
... what can we do to provide an API for power info?
02:37:00 [plh]
... no good way to track power per process, per website basis
02:37:19 [plh]
... I don't know what it is yet however
02:37:25 [plh]
... an API for joules doesn't seem effective
02:37:36 [plh]
.... since don't know what to do with the data
02:38:11 [plh]
... second one is what happen when the TAB is in the background
02:38:13 [plh]
... appnap
02:38:19 [plh]
... or when the tab is suspended
02:38:42 [plh]
... browsers and user agents are doing things to improve by altering runtime patterns
02:39:13 [plh]
... we're solving it in inconsistent ways
02:39:19 [plh]
... we could be more predictible
02:39:46 [plh]
... a JS API/event/notification seems needed
02:39:53 [plh]
... with a time limit to respond
02:40:15 [plh]
... RAF isn't called if it's background
02:40:29 [plh]
... but not great for other things like sync emails, facebook update, etc.
02:40:55 [plh]
... some potential here
02:41:21 [plh]
Alois: profiling power usage, and how to help devs to write more power efficient apps
02:43:07 [plh]
Jason: Boris mentioned that they increase the timeout duration between callbacks in background
02:44:00 [plh]
Aois: setTimeout getting slower seems problematic
02:44:20 [plh]
Jatinder: setTimeout isn't reliable anyway
02:44:36 [plh]
Jason: the HTML5 spec doesn specify a time
02:44:54 [plh]
... but maybe we can progressive throlling timers frequency
02:45:11 [plh]
... don't kow if it's a new API
02:45:20 [plh]
... or standardize agreement what the user agent should do
02:45:29 [plh]
... we're all doing different things right now
02:47:19 [plh]
plh: can we find a pattern in what user agents do right now?
02:47:33 [plh]
Arvind: what does Windows do for background tabs?
02:48:21 [plh]
Jason: you wakeup as occasoinally as possible
02:48:28 [plh]
... you proceed by burst
02:48:38 [plh]
... ie do as uch as possible when you're awake
02:48:42 [plh]
... then back to sleep
02:49:05 [cwdoh]
cwdoh has joined #webperf
02:49:10 [plh]
... for IE, when launched without page, no power will be consumed. no timers, no anything, besides one case
02:49:22 [plh]
... (besides a hang in flash :)
02:49:34 [plh]
... others have a polling based model
02:50:00 [plh]
... it's mapped to HTML5, setTimeout, RAF, etc.
02:50:09 [plh]
... all interrupts are aligned to the hardware
02:50:22 [plh]
... ie vlbank for the display
02:50:45 [plh]
... if no pending work, we bail out
02:51:03 [plh]
... if work, we'll guarantee the callbacks
02:51:27 [plh]
... the number of callbacks per second, but not the frequency
02:51:44 [plh]
... ex: 4ms callbacks, so expect 250 callbacks for that
02:52:14 [plh]
... but we'll map than to the display interrupt, ie 60ms
02:52:23 [plh]
... we'll have 4 callbacks instead
02:52:36 [plh]
... we'll nest them
02:53:02 [plh]
... make the callbacks not looking consistent for benchmarks
02:53:33 [plh]
Arvind: on windows phone, if I look at an other app, not the browser, but there are tabs
02:53:37 [taocai]
taocai has joined #webperf
02:53:38 [plh]
... what happen to them?
02:54:05 [plh]
Jason: if it's windows phone 8, phone or surface, the TAB is in backstack
02:54:11 [plh]
... most recently used app
02:54:20 [plh]
... so IE goes into the backstack
02:54:26 [plh]
... it will run for 8s there
02:54:37 [plh]
... not painting, lower priority, ...
02:54:41 [plh]
... but still running
02:54:49 [plh]
... after 8s, it is suspended
02:55:02 [plh]
... ie stop executing
02:55:10 [plh]
... the further it goes into the backstack
02:55:19 [plh]
... the process will be serialized
02:55:54 [plh]
... we send the visisiliby event
02:56:03 [plh]
... but don't know they are going to be suspended
02:56:15 [ken]
ken has joined #webperf
02:56:24 [plh]
... but you can register for an windows RT event with an app
02:56:54 [plh]
... email client
02:57:06 [plh]
... we use techniques to flush the memory
02:57:08 [JatinderMann_]
JatinderMann_ has joined #webperf
02:57:30 [JatinderMann_]
present+ JatinderMann
02:57:36 [plh]
... if the user doesn't go back to the app for long time, we'll terminate the process
02:58:09 [plh]
... apple model is very similar
02:58:22 [plh]
Arvind: what kind of event is sent?
02:58:27 [plh]
Jason: "onsuspend"
02:58:34 [plh]
... (something like that)
02:58:46 [ken]
ken has joined #webperf
02:59:27 [plh]
... we sent an event if we wake up again
02:59:59 [plh]
Arvind: what about tabs?
03:00:11 [plh]
Jason: ok, so that was for foreground tab
03:00:24 [plh]
... for background tab, we reduce frequency
03:00:49 [JatinderMann_]
scribe: JatinderMann
03:01:38 [JatinderMann_]
Arvind: Is there a scenario where a tab hasn't been used for a few days, do you kill the javascript.
03:02:25 [JatinderMann_]
Jason: The desktop browser doesn't do anything special here becaus its trying to maintain compatibility with line of business apps.
03:02:45 [JatinderMann_]
...The immersive browser will suspend tabs on an individual basis.
03:03:08 [plh3]
plh3 has joined #webperf
03:03:10 [JatinderMann_]
Arvind: Thanks for the info.
03:03:34 [JatinderMann_]
Jason: Everything shared is public. You can check our build talks for details.
03:03:47 [JatinderMann_]
...Seems like iOS has a similar model here.
03:04:23 [JatinderMann_]
Arvind: I'm guessing the OSX's app nap is something similar.
03:05:00 [JatinderMann_]
Jason: Based on yesterdays discusson, looks like they are slowing down the background tabs, but not necessarily shut down.
03:05:36 [JatinderMann_]
...We have seen cases where some US banks have security built into the onload handlers. So shutting down may have a compat issue for some users.
03:06:05 [JatinderMann_]
Arvind: Wht about andriod and ios? do they serialize?
03:06:22 [JatinderMann_]
Jason: I'm not very famaliar with andriod.
03:06:40 [JatinderMann_]
Arvind: Seems like most apps consume a ton of RAM these days.
03:07:19 [JatinderMann_]
Jason: Have you heard of super fetch in windows? The ability to suspend on a page level.
03:08:57 [JatinderMann_]
Jason: Everyone's doing these little optimizations, which are great. but developers aren't aware of them, so it just seems like a bit random. Seeing that apple and microsoft both have a similar suspend models, it may make sense to bring such a suspend event to tne web platform.
03:09:12 [JatinderMann_]
Arvind: You also mentioned throttling down timers based on how long the tab hasn't been used.
03:09:23 [JatinderMann_]
Jason: I think thats something id fine interesting.
03:09:57 [JatinderMann_]
Arvind: I think theres definitely interest in the community around power consumption. i think its a good area. ilya has done some research in tbis area
03:10:39 [cwdoh]
cwdoh has joined #webperf
03:11:30 [JatinderMann_]
alois: the maling list had an idea on gzipping on the network. today theres no opportunkty in javascript to gzip.
03:12:14 [JatinderMann_]
alois: it may be interesting to have a functon to gzip.
03:12:31 [JatinderMann_]
jason: i'm not sure it makes sense compress from client to server
03:12:56 [JatinderMann_]
arvind: it'll help to save battery
03:13:22 [JatinderMann_]
jason: i think the compressing process may actually burn in more cpu trying to compress
03:13:59 [JatinderMann_]
jatinder: there definitely a curve here. we may want to prototype this and check what the data look like
03:14:24 [JatinderMann_]
arvind: jonas mentioned we should try to find out if a JS compression is comparable to a native functon
03:15:03 [JatinderMann_]
... seems like there are libraries that do compressand that's why we dont have a native functon
03:15:27 [JatinderMann_]
jason: i bet the JS implementtio in a library wll be 100x more expensive than doing it natively
03:16:48 [JatinderMann_]
... there are definitly wire costs but i think the power loss will be higher due to cpu cost
03:17:46 [AutomatedTester]
AutomatedTester has joined #webperf
03:17:52 [JatinderMann_]
jatinder: prototyping will help us determine the cost / benefit analysis. if we find that there s really just a small window of improvement, this may not be something we want to pursue. but if the data shows that the window is much larger, we may want to pursue
03:18:44 [JatinderMann_]
alois: i also want to talk about single page applications and measuring performance. a lot of timing apis are built on normal docunents, but single page appications user timing is not as useful
03:19:33 [JatinderMann_]
alois: i think we should invest in new ideas here
03:20:10 [JatinderMann_]
jatinder: i know single page apps are becoming the rage. do we have data on how many single page apps there are?
03:20:32 [JatinderMann_]
alois: i dnt have great numbers, but we should include these guys at our next workshop.
03:20:33 [kimwoonyoung]
kimwoonyoung has joined #webperf
03:20:44 [JatinderMann_]
...we currently don't get good information on that area today
03:21:01 [Takahiro]
Takahiro has joined #webperf
03:22:37 [JatinderMann_]
arvind: thanks eveyone for joining us these last two days. great discussions!
03:23:03 [JatinderMann_]
rrsagent, generate minutes
03:23:03 [RRSAgent]
I have made the request to generate http://www.w3.org/2013/11/14-webperf-minutes.html JatinderMann_
03:24:04 [cwdoh_]
cwdoh_ has joined #webperf
03:25:20 [rniwa]
rniwa has joined #webperf
03:29:56 [cwdoh]
cwdoh has joined #webperf
03:33:59 [a12u]
a12u has joined #webperf
04:00:15 [myakura]
myakura has joined #webperf
04:01:50 [cwdoh]
cwdoh has joined #webperf
04:10:44 [saki_]
saki_ has joined #webperf
04:33:47 [ken]
ken has joined #webperf
04:36:12 [tao]
tao has joined #webperf
04:46:45 [taocai]
taocai has joined #webperf
05:25:46 [saki]
saki has joined #webperf
05:27:02 [saki_]
saki_ has joined #webperf
05:34:16 [myakura]
myakura has joined #webperf
05:38:20 [Pan]
Pan has joined #webperf
05:45:02 [rniwa]
rniwa has joined #webperf
05:51:44 [saki]
saki has joined #webperf
06:05:19 [rniwa]
rniwa has joined #webperf
06:05:43 [Tomoyuki]
Tomoyuki has joined #webperf
06:16:13 [taocai]
taocai has joined #webperf
06:17:21 [rniwa]
rniwa has joined #webperf
06:32:56 [Tomoyuki]
Tomoyuki has joined #webperf
06:40:07 [Tomoyuki]
Tomoyuki has left #webperf
07:02:01 [renoirb]
renoirb has left #webperf
07:30:51 [tao]
tao has joined #webperf
07:31:43 [tao]
tao has left #webperf
07:35:23 [taocai]
taocai has joined #webperf
07:37:55 [taocai]
taocai has left #webperf
08:45:46 [myakura]
myakura has joined #webperf
08:47:00 [ken]
ken has joined #webperf
08:52:30 [ken_]
ken_ has joined #webperf
08:55:55 [masatakayakura]
masatakayakura has joined #webperf
09:29:14 [ken]
ken has joined #webperf
09:36:08 [kimwoonyoung]
kimwoonyoung has joined #webperf
10:58:10 [myakura]
myakura has joined #webperf
11:58:36 [myakura]
myakura has joined #webperf
12:52:11 [kimwoonyoung]
kimwoonyoung has joined #webperf
12:59:01 [myakura]
myakura has joined #webperf
13:11:06 [kimwoonyoung]
kimwoonyoung has joined #webperf
13:23:52 [kimwoonyoung]
kimwoonyoung has joined #webperf
13:59:29 [myakura]
myakura has joined #webperf
14:11:24 [Takahiro]
Takahiro has joined #webperf
14:59:54 [myakura]
myakura has joined #webperf
15:59:51 [cwdoh]
cwdoh has joined #webperf
16:00:19 [myakura]
myakura has joined #webperf
16:01:29 [cwdoh]
cwdoh has joined #webperf
16:13:00 [rniwa]
rniwa has joined #webperf
16:38:16 [kimwoonyoung]
kimwoonyoung has joined #webperf
16:41:04 [rniwa]
rniwa has joined #webperf
16:42:45 [cwdoh]
cwdoh has joined #webperf
17:00:46 [myakura]
myakura has joined #webperf
18:01:08 [myakura]
myakura has joined #webperf
18:34:21 [myakura]
myakura has joined #webperf
21:26:13 [myakura]
myakura has joined #webperf
22:30:57 [myakura]
myakura has joined #webperf
23:31:22 [myakura]
myakura has joined #webperf
00:01:33 [myakura]
myakura has joined #webperf
00:19:09 [ken]
ken has joined #webperf
01:01:57 [myakura]
myakura has joined #webperf
01:03:40 [masatakayakura]
masatakayakura has joined #webperf