Re: [w3c/webcomponents] Events whose composed flag should be true (#513)

This was my earlier point:

> The component _could_ fire a custom event, but that requires more boilerplate for its author (has to add listeners, catch it, forward a different name, and do cleanup work in detached). It's more natural to use the animation events already being fired. 

IMO, that's all more complicated than it needs to be.

> What happens when in v2...

Events are part of a component's public API. I'd expect well authored components to clearly document changes. For example: https://elements.polymer-project.org/elements/paper-button#events


---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/513#issuecomment-238450567