- From: Jatinder Mann <jmann@microsoft.com>
- Date: Wed, 5 Oct 2011 23:06:12 +0000
- To: Boris Zbarsky <bzbarsky@MIT.EDU>, "public-web-perf@w3.org" <public-web-perf@w3.org>
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. Jatinder -----Original Message----- From: public-web-perf-request@w3.org [mailto:public-web-perf-request@w3.org] On Behalf Of Boris Zbarsky Sent: Wednesday, September 28, 2011 7:39 PM To: public-web-perf@w3.org Subject: [PageVisibility] Need to define what sort of event visibilitychange is Specifically, what interface it implements. Can we just reference the "fire a simple event" definition from html5? Also, is this event cancelable? I'd think not, but I'm not quite sure what it really means to be cancelable or not for events without default actions. -Boris
Received on Wednesday, 5 October 2011 23:08:20 UTC