Re: [Page Visibility] Navigate away behavior (was RE: TPAC 2011 Web Performance WG 2011-11-01) from Jonas Sicking on 2011-11-15 (public-web-perf@w3.org from November 2011)

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 15 Nov 2011 13:29:22 -0800
To: Jatinder Mann <jmann@microsoft.com>
Cc: "Boris Zbarsky (bzbarsky@mit.edu)" <bzbarsky@mit.edu>, "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <CA+c2ei98jE_SKzfMi2H=PkoHb8sBqmJaxuELiyf9sUDL8=QB5A@mail.gmail.com>

On Tue, Nov 15, 2011 at 10:35 AM, Jatinder Mann <jmann@microsoft.com> wrote:
>>We do need to define ordering of that event with unload/pageshow/pagehide, of course.
>
> Yes, the ordering will need to be clearly defined. On the surface, it seems that the visibilitychange event should fire at the same time as the unload.

I think it'd make sense to fire visibilitychange after
pagehide/unload, but synchronously from the same task. That way pages
that don't want to do unneccesary work in visibilitychange when the
page is getting navigated away from can easily accomplish that.

/ Jonas

Received on Tuesday, 15 November 2011 21:30:21 UTC