W3C home > Mailing lists > Public > public-web-perf@w3.org > May 2012

RE: [Page Visibility] Navigate away behavior (was RE: TPAC 2011 Web Performance WG 2011-11-01)

From: Jatinder Mann <jmann@microsoft.com>
Date: Thu, 17 May 2012 23:54:21 +0000
To: "public-web-perf@w3.org" <public-web-perf@w3.org>, "Boris Zbarsky (bzbarsky@mit.edu)" <bzbarsky@mit.edu>, "arvind@google.com" <arvind@google.com>
Message-ID: <AE5FFD9402CD4F4785E812F2C9929D6504EFE067@SN2PRD0310MB383.namprd03.prod.outlook.com>
Considering we have reached consensus on ISSUE-8: Determine whether to fire visibilitychange even unloading or suspending, http://www.w3.org/2010/webperf/track/issues/8, I have updated the Page Visibility spec to fire the visibilitychange event before the pageshow event, after the pagehide event and before the unload event.

I have removed the "suspended" event and have made the "unloaded" event optional, as there is still value in informing developers of this scenario. Based on feedback that the "preview" state is confusing, I have removed that optional state. Per the vendor prefix section, UAs are free to add additional vendor prefixed states as needed.

Thanks,
Jatinder
Received on Thursday, 17 May 2012 23:55:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:32 UTC