- From: Andreas Pehrson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 May 2019 15:16:12 +0000
- To: public-webrtc-logs@w3.org
I eventually found this in the HTMLMediaElement spec: > The media element load algorithm consists of the following steps. > 1. Abort any already-running instance of the resource selection algorithm for this element. > 2. Let pending tasks be a list of all tasks from the media element's media element event task source in one of the task queues. > 3. For each task in pending tasks that would resolve pending play promises or reject pending play promises, immediately resolve or reject those promises in the order the corresponding tasks were queued. > 4. Remove each task in pending tasks from its task queue > > Basically, pending events and callbacks are discarded and promises in-flight to be resolved/rejected are resolved/rejected immediately when the media element starts loading a new resource. That takes care of my "ratechange" concern. But the question remains of what values `playbackRate`, `defaultPlaybackRate` and `preload` should have when changing to a non-MediaStream source after having had a MediaStream source.. -- GitHub Notification of comment by Pehrsons Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/599#issuecomment-496561453 using your GitHub account
Received on Tuesday, 28 May 2019 15:16:13 UTC