- From: Darin Fisher <darin@chromium.org>
- Date: Fri, 7 Oct 2011 09:48:52 -0700
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: public-web-perf@w3.org
Received on Friday, 7 October 2011 16:49:27 UTC
On Thu, Oct 6, 2011 at 5:30 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 10/6/11 3:22 AM, Darin Fisher wrote: > >> 2) The visibility state of a document changes synchronously on page >> navigations. In particular, it changes to hidden (if not already >> hidden) synchronously after the firing of the pagehide event and >> changes to visible as needed synchronously before the firing of the >> pageshow event. >> >> >> This makes sense, although Chromium does not implement a back/forward >> page cache. Otherwise, it sounds like we will have compatible >> implementations. >> > > Just to make sure... does that mean you fire visibilitychange on > navigation? > >From my testing it looks like we do, but I've asked the engineer who developed this feature to verify and comment on this thread. -Darin > > Note that my implementation in Gecko does so no matter what's going on with > the back/forward cache, just like we always fire pagehide/pageshow. > > -Boris > >
Received on Friday, 7 October 2011 16:49:27 UTC