- From: Jonas Sicking <jonas@sicking.cc>
- Date: Wed, 5 Oct 2011 16:30:07 -0700
- To: Jatinder Mann <jmann@microsoft.com>
- Cc: Boris Zbarsky <bzbarsky@mit.edu>, "public-web-perf@w3.org" <public-web-perf@w3.org>
On Wed, Oct 5, 2011 at 4:06 PM, Jatinder Mann <jmann@microsoft.com> wrote: > I agree that the visibilitychange event should be a simple event that implements the Event interface. Considering this event fires after the visibility has changed, I don't think it should, or can be, cancelable. Particularly, I don't think we can preventDefault for page visibility - e.g., we can't stop the user from minimizing the browser. > > I will update the spec to have some verbiage like so: Queue a task to fire a simple event that bubbles named visibilitychange at the Document. You'll need to explicitly say that it's not cancelable too. So something like "...simple event that bubbles, but isn't cancelable, named...". Other than that it sounds good. / Jonas
Received on Wednesday, 5 October 2011 23:31:16 UTC