Re: [whatwg/dom] cancelBubble legacy property (#211)

Our [usage stats](https://www.chromestatus.com/metrics/feature/timeline/popularity/344) suggest that it's still pretty popular (though falling).  This will be tainted somewhat by event copying code, but 4% of page views is huge compared to what we normally see for event copying (eg. 0.2% [for webkitMovementX](https://www.chromestatus.com/metrics/feature/timeline/popularity/382) before we removed it).  I Get a ton of hits for "cancelBubble" in httpArchive.

So yeah we're unlikely to be able to remove it.  But if Gecko just has it mapped to stopPropagation then perhaps that would be web compatible for us (certainly simpler).  What does Edge do?   We might need to add UseCounters measuring how often the difference matters (eg. how often it's set back to false, or set from within capturing handlers while there are still other capturing handlers to run).

That said, if IE, Edge, WebKit and blink are all consistent here already, maybe it's best to just define it exactly as it's implemented in those browsers.  I guess it's not completely crazy to think that some capturing handler may want to prevent all bubbling without preventing the rest of the capture or target phases.

@tkent-google any thoughts?

---
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/211#issuecomment-207823569