Confusing cancelBubble about polymer HOT 5 CLOSED

This issue is super old, not sure if relevant anymore.

from polymer.

We haven't actually answered this satisfactorily. It also helps me remember that we have a general issue that our event delegation system is under-designed.

from polymer.

Is this still relevant given that cancelBubble has been deprecated? http://dom.spec.whatwg.org/#event

from polymer.

cancelBubble is no longer relevant. Polymer no longer does event
dispatching, instead putting listeners directly on elements containing
declarative event attributes. The normal methods of affecting event
bubbling should now work: event.preventDefault() and
event.stopPropagation().

On Sun, Mar 16, 2014 at 2:08 PM, Addy Osmani [email protected]:

Is this still relevant given that cancelBubble has been deprecated?
http://dom.spec.whatwg.org/#event

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/74#issuecomment-37770994
.

from polymer.

Just to be clear preventDefault is unrelated to event propagation (a lot of
people have cargo culted these two into the same bucket)
On Mar 17, 2014 11:25 AM, "Steve Orvell" [email protected] wrote:

cancelBubble is no longer relevant. Polymer no longer does event
dispatching, instead putting listeners directly on elements containing
declarative event attributes. The normal methods of affecting event
bubbling should now work: event.preventDefault() and
event.stopPropagation().

On Sun, Mar 16, 2014 at 2:08 PM, Addy Osmani [email protected]:

Is this still relevant given that cancelBubble has been deprecated?
http://dom.spec.whatwg.org/#event

—
Reply to this email directly or view it on GitHub<
https://github.com/Polymer/polymer/issues/74#issuecomment-37770994>
.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/74#issuecomment-37828402
.

from polymer.