20:52:40 <RRSAgent> RRSAgent has joined #webperf
20:52:40 <RRSAgent> logging to http://www.w3.org/2011/10/12-webperf-irc
20:52:42 <trackbot> RRSAgent, make logs world
20:52:44 <trackbot> Zakim, this will be WPWG
20:52:44 <Zakim> ok, trackbot; I see RWC_web-per(WPWG)4:00PM scheduled to start 52 minutes ago
20:52:45 <trackbot> Meeting: Web Performance Working Group Teleconference
20:52:45 <trackbot> Date: 12 October 2011
21:00:34 <Zakim> RWC_web-per(WPWG)4:00PM has now started
21:00:40 <Zakim> +[Microsoft]
21:01:32 <Zakim> +Plh
21:02:13 <Zakim> + +1.650.253.aaaa
21:04:37 <JatinderMann> present+ Karen Anderson
21:04:44 <JatinderMann> present+ JatinderMann
21:04:50 <JatinderMann> present+ Arvind Jain
21:04:56 <JatinderMann> present+ Plh
21:11:48 <JatinderMann> Topic: IFrame visibility for the Page Visibility spec
21:13:36 <JatinderMann> Jatinder: Our options are to either mirror IFrame visibility with that of the top level document or giving the more granular IFrane visibility including the applied styling and offscreen location.
21:16:51 <JatinderMann> Jatinder: I have found there are two interesting cases where the granular IFrame visibility may be useful: UA extension applying a display:none style to cross-origin iframes or ad being scrolled off screen and can throttle work. The first case does seem like an edge case. The spec today makes a simplifying assumption that anything in the visible page is visible.
21:21:47 <JatinderMann> Jatinder: The goal is to reduce background interference. This goal is relatively well met with the current spec, where pages in background tabs are throttled. 
21:24:49 <JatinderMann> Arvind: There are some cases that we haven't covered, like fully obscured window. Likewise, this can be another case that can be covered in the next cut of the spec.
21:25:48 <JatinderMann> Jatinder: If we do support this in the spec, I feel it should not be a normative requirement.
21:25:55 <JatinderMann> Arvind: I will respond to the mailing list.
21:28:29 <JatinderMann> Arvind: The next topic was whether the visibility event should be fired and state changed for the navigate away case.
21:29:04 <JatinderMann> Jatinder: I think we should make an assumption that we should either fire the event and change the state or not fire the event or change the state.
21:32:23 <Zakim> -Plh
21:32:24 <Zakim> - +1.650.253.aaaa
21:32:26 <Zakim> -[Microsoft]
21:32:26 <Zakim> RWC_web-per(WPWG)4:00PM has ended
21:32:28 <Zakim> Attendees were [Microsoft], Plh, +1.650.253.aaaa
22:19:24 <JatinderMann> Jatinder: Before the unload event, we are still visible, so we shouldn't report as hidden then. After the unload event, the page should be unloaded, so there shouldn't be any action that can be taken by knowing the page is hidden. We should follow up on the mailing list to understand why this behavior would be desired.
22:20:18 <JatinderMann> Topic: TPAC Schedule
22:20:31 <JatinderMann> Jatinder: As for TPAC, the proposed timeframe will be to meet between 1-5pm Tuesday afternoon. This gives us the morning to potentially chat with the WebApp Security WG. If we need more time, we can move the meeting to the morning.
22:22:50 <JatinderMann> rssagent, generate minutes
22:22:56 <JatinderMann> rrsagent, generate minutes
22:22:56 <RRSAgent> I have made the request to generate http://www.w3.org/2011/10/12-webperf-minutes.html JatinderMann