17:00:06 <RRSAgent> RRSAgent has joined #webperf
17:00:06 <RRSAgent> logging to http://www.w3.org/2013/08/21-webperf-irc
17:00:08 <trackbot> RRSAgent, make logs world
17:00:08 <Zakim> Zakim has joined #webperf
17:00:10 <trackbot> Zakim, this will be WPWG
17:00:10 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
17:00:11 <trackbot> Meeting: Web Performance Working Group Teleconference
17:00:11 <trackbot> Date: 21 August 2013
17:01:19 <plh> zakim, this is per
17:01:20 <Zakim> ok, plh; that matches RWC_web-per()1:00PM
17:01:24 <Zakim> +Plh
17:01:33 <JatinderMann> present+ JatinderMann
17:01:39 <JatinderMann> present+ plh
17:01:43 <JatinderMann> present+ Daniel
17:02:23 <Zakim> +[Microsoft.a]
17:02:54 <Zakim> + +1.949.754.aaaa
17:03:05 <JatinderMann> present+ AaronHeady
17:03:49 <robfromdell> robfromdell has joined #webperf
17:04:03 <Zakim> + +1.408.203.aabb
17:04:07 <plh> zakim, aaaa is Rob
17:04:07 <Zakim> +Rob; got it
17:04:15 <plh> zakim, aabb is Arvind
17:04:15 <Zakim> +Arvind; got it
17:04:17 <JatinderMann> present+ ArvindJain
17:04:23 <JatinderMann> present+ RobDickenson
17:06:10 <JatinderMann> Topic: Element Visibility
17:07:20 <simonjam> simonjam has joined #webperf
17:07:24 <JatinderMann> Arvind: I've seen a few different types of requests: one is to see visibility on an element level. Today visibility is for top level browsing context. One ask is to see if it can be made at an element level. E.g., if an iframe is scrolled below the fold, it wants to know if its visible or not.
17:08:39 <AaronHeady> AaronHeady has joined #webperf
17:09:01 <JatinderMann> ...In one case the JavaScript on the main page can query the visibility of elements. The other case is third party advertisers want to be able to query when their ad is viewed or not.
17:09:31 <ganesh> ganesh has joined #webperf
17:09:50 <Zakim> + +1.650.214.aacc
17:10:21 <Zakim> - +1.650.214.aacc
17:10:39 <JatinderMann> ...Mozilla has a interface to give the iframe the screen coordinates to determine screen coordinates. See https://www.w3.org/Bugs/Public/show_bug.cgi?id=22931.
17:10:44 <Zakim> + +1.650.214.aadd
17:12:15 <Zakim> + +1.503.712.aaee
17:19:10 <JatinderMann> Jatinder: If we are giving screen coordinates, we can just do the math and avoid the developer doing the math.
17:22:56 <Zakim> - +1.650.214.aadd
17:23:39 <Zakim> + +1.650.214.aaff
17:28:13 <JatinderMann> Jatinder: Let's put together an Element Visibility to answer the first part of the question. I'll share a draft with you Arvind. Arvind, also send me any thoughts or proposals.
17:34:08 <JatinderMann> Jatinder: We need to determine whether Chrome or IE for cross origin iframes share the top level parent or not.
17:34:16 <JatinderMann> Arvind: I'll follow up with Chrome behavior.
17:34:23 <JatinderMann> Jatinder: I can follow up with IE behavior.
17:36:36 <Zakim> -Arvind
17:39:44 <JatinderMann> Topic: Resource Priorities
17:55:16 <plh> http://www.w3.org/2013/08/results-user-timing-tests.html
17:55:35 <JatinderMann> Jatinder: Please review the Resource Priorities spec updates and raise issues. Thanks!
17:55:38 <JatinderMann> Topic: Test Cases
17:56:56 <JatinderMann> Plh: IE and Chrome both pass the tests.
17:57:00 <plh> http://www.w3.org/2013/08/results-google-resource-timing-tests.html
17:57:01 <JatinderMann> Plh: Do we need any additional tests?
17:57:20 <JatinderMann> James: I don't believe there are new tests we need to write.
18:02:24 <Zakim> - +1.503.712.aaee
18:02:25 <Zakim> -Rob
18:02:26 <Zakim> -[Microsoft]
18:02:26 <Zakim> - +1.650.214.aaff
18:02:27 <Zakim> -Daniel
18:02:27 <Zakim> -[Microsoft.a]
18:02:30 <Zakim> -Plh
18:02:32 <Zakim> RWC_web-per()1:00PM has ended
18:02:32 <Zakim> Attendees were Daniel, [Microsoft], Plh, +1.949.754.aaaa, +1.408.203.aabb, Rob, Arvind, +1.650.214.aacc, +1.650.214.aadd, +1.503.712.aaee, +1.650.214.aaff
18:02:35 <JatinderMann> Plh: Jatinder, can you check for the IE test failures?
18:03:01 <JatinderMann> Jatinder: I'll review all the test cases. I think this is a good opportunity to find test case issues, browser issues, or potentially spec issues.
18:03:37 <JatinderMann> Plh: I think we can move User Timing and Performance Timeline to PR and rAF to CR, based on this information. Resource Timing will just have to come in after.
18:03:46 <JatinderMann> Topic: Next meeting
18:03:54 <JatinderMann> James: I'm out next week.
18:03:57 <JatinderMann> Plh: Me too.
18:04:05 <JatinderMann> Jatinder: Let's schedule our next meeting for two weeks out.
18:04:11 <JatinderMann> rrsagent, generate minutes
18:04:11 <RRSAgent> I have made the request to generate http://www.w3.org/2013/08/21-webperf-minutes.html JatinderMann
19:34:24 <Zakim> Zakim has left #webperf