I don't think there are fatal issues in PageVisibiliy2. :( Visibility state and event in document level is quite useful to saving power/improve performance in a lot of scenarios by taking little runtime check efforts, I'm trying to implement it in Blink and measure some data.
By Scanning previous threads, we may have issues to define the "visible", I quite agree Jatinder's suggestion that we follow the principle of PV1: when say hidden, it is actually hidden, when say visible, we accept some error report. Then we can focus on clarifying the "actually hidden" case, which is helpful enough. We may have some compatibility issues with PV1, I guess it means some existing app may depend on top context visibility when they are accessing sub document's property, so when PV2 is shipped, the behavior may be affected. While, for the same origin case, it won't be blocked to access the top context visibility state from sub frame, there is still a way to access top context visibility. Thanks Pan From: Tobin Titus [mailto:tob...@microsoft.com] Sent: Wednesday, October 15, 2014 10:08 AM To: public-web-perf Subject: [agenda] Web Performance WG Teleconference #139 Agenda 2014-10-15 Below is the proposed agenda for our conference call meeting Wednesday, October 15th at 3PM EST / 12PM PST. Feel free to propose additional topics to the agenda. We may not get much to update, but we can at least sync on current status. - Beacon - Security and Privacy - Web Smoothness API - Microsoft feedback - Page Visibility 2 - Last call for discussion on dropping this spec - Resource Hints - Discuss first draft timeline - TPAC - Discuss getting topics in the agenda for TPAC Face to Face Zakim Bridge Number: +1.617.761.6200 . For SIP access, see http://www.w3.org/2006/tools/wiki/Zakim-SIP Passcode 97373 (WPERF) IRC channel #webperf on irc.w3.org<http://irc.w3.org/>:6665 http://irc.w3.org/ Working Group Conference Call (3-4PM EST/12-1PM PST) Thanks, Tobin
