Summary: | Drop beforeload event | ||
---|---|---|---|
Product: | WebKit | Reporter: | Yusuke Suzuki <ysuzuki> |
Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
Status: | REOPENED --- | ||
Severity: | Normal | CC: | ap, cdumez, koivisto, rniwa, ysuzuki |
Priority: | P2 | ||
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
Yusuke Suzuki
2017-06-30 01:49:45 PDT
I don't think we're in the position to drop the beforeunload event. There are just too many Safari extensions and the web content (particularly enterprise websites) that rely on this feature. (In reply to Ryosuke Niwa from comment #1) > I don't think we're in the position to drop the beforeunload event. There Ah, no. This bug intends to drop "beforeload" event. Not "beforeunload". Is it typo? Or is there so many Safari extensions and the web content using "before load" event? If so, we cannot drop it :) > are just too many Safari extensions and the web content (particularly > enterprise websites) that rely on this feature. (In reply to Yusuke Suzuki from comment #2) > (In reply to Ryosuke Niwa from comment #1) > > I don't think we're in the position to drop the beforeunload event. There > > Ah, no. This bug intends to drop "beforeload" event. Not "beforeunload". > Is it typo? Or is there so many Safari extensions and the web content using > "before load" event? If so, we cannot drop it :) Oh, oops. I misread. My understanding is that we can't completely drop this yet due to amount of old style extensions using it. However we could stop exposing it to the web and make it extension-only. (In reply to Antti Koivisto from comment #4) > My understanding is that we can't completely drop this yet due to amount of > old style extensions using it. Oh, that's unfortunate thing... > However we could stop exposing it to the web > and make it extension-only. It sounds nice direction to me. |