- From: <bugzilla@jessica.w3.org>
- Date: Mon, 11 Apr 2016 16:59:41 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25002
Domenic Denicola <d@domenic.me> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |miketaylr@gmail.com,
| |travil@microsoft.com
--- Comment #7 from Domenic Denicola <d@domenic.me> ---
> And I guess BeforeUnloadEvent can just define its own version as it already does.
Hmm, I wonder if we could just remove BeforeUnloadEvent? The difference would
be that currently `unloadEv.returnValue = { toString() { return ""; } }` does
not prevent default, but if we removed BeforeUnloadEvent, it would. But
`unloadEv.returnValue = "any non empty string"` and `unloadEv.returnValue = ""`
would have the same behavior.
I guess reading `unloadEv.returnValue` after setting it would change behavior.
---
Re-reading the thread though, it seems nicer not to spec this. Did Edge
encounter pages that were depending on it, on the mobile web? +Travis and Mike
Taylor for compat questions.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 11 April 2016 16:59:44 UTC