- From: Brian Birtles via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Jan 2021 03:32:37 +0000
- To: public-css-archive@w3.org
> What are your thoughts on my "Alternative" section on my last comment? > > i.e. what is the rationale for having the `current ready promise` be initially _resolved_? If the current ready promise was initially un-resolved, this would solve my problem as well. The `ready` promise represents the state of an asynchronous operation. When it resolves, it tells you that it is safe to read the `currentTime` (for pausing) and `startTime` (for playing) values. Having it be unresolved initially breaks that model. There is no operation pending and it is safe to read `currentTime` / `startTime` so I don't think it should be unresolved at that point. I'd also be a little concerned about changing that behavior now that it is shipping in all browsers. -- GitHub Notification of comment by birtles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5871#issuecomment-762579981 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 January 2021 03:32:39 UTC