- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 Aug 2017 10:30:15 +0000
- To: public-media-capture-logs@w3.org
Sorry, I misspoke, by "as is" I meant whatever is actually interoperably implemented, not what the spec says. The "pretend that the state changes synchronously" route seems OK if other implementers (not me) want it too. Note that for media elements, the true async nature can still be observed, e.g. calling `pause()` makes the element look paused, but currentTime will change at least once more since the playback doesn't happen on the main thread. Are there situations like that here? -- GitHub Notification of comment by foolip Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/123#issuecomment-324881548 using your GitHub account
Received on Friday, 25 August 2017 10:30:12 UTC