- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 May 2019 22:34:56 +0000
- To: public-webrtc-logs@w3.org
Yes, or maybe what Chrome [gives me](https://jsfiddle.net/jib1/kga04vLt/) ``` 0.6 1 1 0.5 ratechange ``` The [media element load algorithm](https://html.spec.whatwg.org/multipage/media.html#media-element-load-algorithm) says: > 7. Set the playbackRate attribute to the value of the defaultPlaybackRate attribute. Which is *after* step 3-4 which clears old tasks (silencing events for changes up to that point). On the one hand, there's no step 8 here that says to fire the `ratechange` event. However, elsewhere it says: > When the defaultPlaybackRate or playbackRate attributes change value (either by being set by script or by being changed directly by the user agent, e.g. in response to user control) the user agent must queue a task to fire an event named ratechange at the media element. Do explicit algorithms invoke other algorithms implicitly in that spec? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/599#issuecomment-497880364 using your GitHub account
Received on Friday, 31 May 2019 22:34:57 UTC