- From: Eric Bidelman <notifications@github.com>
- Date: Mon, 08 Aug 2016 20:07:40 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Tuesday, 9 August 2016 03:08:18 UTC
I can think of a few examples where `TransitionEvent` and `AnimationEvent ` have been helpful in v0. A ripple animation as the result of a button press: http://jsbin.com/yobuloralo/edit?html,output. A component consumer may want to wait for the animation to finish before doing more work (and thus preventing jank). A mobile app drawer sliding in/out (as the result of a user interaction). Users may want to know when the drawer has fully opened. A dialog overlay that transitions in (as the result of a user interaction). Users may want to know when the dialog's transition is done. The component _could_ fire fire a custom event, but that requires more boilerplate for its author. It's natural to listen for the animation events the component is already firing. --- 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-238441270
Received on Tuesday, 9 August 2016 03:08:18 UTC