I wonder if we can drop "beforeload" event support. This is already dropped in Chrome long ago. (2014) https://bugs.chromium.org/p/chromium/issues/detail?id=333318 And Firefox does not support it. It has a bug attempting to support "beforeload" event. But it seems rejected. https://bugzilla.mozilla.org/show_bug.cgi?id=715695 And according to the Firefox's bug, "beforeload" event is introduced to be used by ad-blocking user extensions. However, we already have more efficient mechanism to implement ad-block. Furthermore, "beforeload" event frequently causes some troubles because it can insert JS handler execution.
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.