You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no BCD for this, and it is marked as experimental and deprecated in MDN with the comment:
This property is not part of any specification. Although the similar Event.cancelBubble property was included in an old Working Draft of W3C DOM Level 2. Microsoft has a description of it on MSDN.
The link on MSDN just links back to Event.cancelBubble. What this means is that we have a method that is non-spec and deprecated and since we don't have BCD there is no way for anyone to tell what browsers it might work on (though I guess maybe the old version of Edge based on the MSDN link). Further because it isn't in a spec or implemented anywhere that we know of there is no trigger to clean this up.
So my thinking is we should delete this method as "never going to be helpful for anyone". We could perhaps redirect to Event.cancelBubble too (a nearly as not-useful property, but at least one that has some spec justification).
@hamishwillee yeah, I think I'd agree with this. It quite probably comes under the BCD irrelevant features guideline, and I know @foolip has bene making a bunchof removals based on that, getting rid of BCD and then removing the corresponding docs too.
Thanks @foolip . There is no doubt you know more about Javascript than me - this reads like the property is defined in Event AND reimplemented in UIEvent (the Event version being widely supported, and the UIEvent version being deprecated).
Anyway, fixed in #4900 - the UIEvent version is removed and redirected. There was nothing extra to capture from the removed doc.
I think we should delete UIEvent.cancelBubble page (and mention of it in UIEvent).
There is no BCD for this, and it is marked as experimental and deprecated in MDN with the comment:
The link on MSDN just links back to
Event.cancelBubble
. What this means is that we have a method that is non-spec and deprecated and since we don't have BCD there is no way for anyone to tell what browsers it might work on (though I guess maybe the old version of Edge based on the MSDN link). Further because it isn't in a spec or implemented anywhere that we know of there is no trigger to clean this up.So my thinking is we should delete this method as "never going to be helpful for anyone". We could perhaps redirect to
Event.cancelBubble
too (a nearly as not-useful property, but at least one that has some spec justification).@chrisdavidmills ?
The text was updated successfully, but these errors were encountered: