Re: [csswg-drafts] [web-animations-1] Should async playback methods return the `ready` Promise?

I discussed this with @graouts and @flackr yesterday and decided to revert this change because:

* It will cause users who simply want to call `play()` to have to explicitly catch and ignore rejected Promises to avoid console warnings.
* Such warnings will only fire depending on when the animation is canceled making for potentially hard-to-debug occasional console warnings.
* It is a little inconsistent to have `play()` return the `finished` promise while `pause()` etc. return the `ready` promise. Requiring the author to explicitly specify the Promise on which they wish to wait avoids confusion.
* It makes it harder for authors to distinguish between rejections in `reverse()` etc. due to not being able to reverse vs the animation being canceled.
* It requires implementations to always generates these Promise objects even when they are not used.

-- 
GitHub Notification of comment by birtles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2206#issuecomment-400515500 using your GitHub account

Received on Wednesday, 27 June 2018 01:40:30 UTC