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

Sure, you could listen for something like "click", but I'm not sure how you'd accurately know when the animation/transition is done. Plus, the last thing you'd want is user code (potentially) running during your animation.

A couple of more useful examples from the [Google I/O 2016 PWA](github.com/GoogleChrome/ioweb2016) (we waited for several components to fire a `transitionend` event for internal animations, to delay work and make sure animations were smooth).
- [a photo gallery](https://github.com/GoogleChrome/ioweb2016/blob/e9a6c4c216949ca6d484cfa08b6e802aa06ae339/app/elements/io-home-page.html#L123-L128) - manages a11y behavior when a new photo is transitioned to.
- `<countdown-timer>` that fades itself out when the time is up. [User code](https://github.com/GoogleChrome/ioweb2016/blob/41bdeb6ad3a41fe675f2b49dfa343121f720c135/app/elements/io-live.html#L271) hooks into the transition and sets state  when it's finally invisible.

---
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-238447242