- From: Domenic Denicola <notifications@github.com>
- Date: Tue, 21 Feb 2017 08:53:24 -0800
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 21 February 2017 16:54:09 UTC
In Chrome at least Event's returnValue is a Web IDL boolean, so setting it to 0 and null should be the same as setting it to false. It sounds like your proposing one of the following deltas from the current specs: 1. Add returnValue as a boolean to Event, so that setting it to false (or something that converts to false) cancels the event. 2. (1), but also: - Remove returnValue as a DOMString from BeforeUnloadEvent, making it an empty interface - Remove the setting of `e.returnValue` to the return value of `onbeforeunload` event handlers in https://html.spec.whatwg.org/#the-event-handler-processing-algorithm step 4 - Remove the checking of `e.returnValue` in https://html.spec.whatwg.org/#unloading-documents:dom-beforeunloadevent-returnvalue (thus relying entirely on the checking of cancelation) 3. (2), but also remove the BeforeUnloadEvent interface entirely -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/334#issuecomment-281404452
Received on Tuesday, 21 February 2017 16:54:09 UTC