Fired when a View is added.
Fired when the player can resume playback of the media data.
- In comparison to canplaythrough, the player estimates that if playback were to be started now, the media resource could not be rendered at the current playback rate up to its end without having to stop for further buffering of content.
- See HTML media - network state events.
Fired when the player can resume playback of the media data and buffering is unlikely.
- In comparison to canplay, the player estimates that if playback were to be started now, the media resource could be rendered at the current playback rate all the way to its end without having to stop for further buffering.
- See HTML media - network state events.
Fired when MultiViewPlayer.duration changes.
- Fired after MultiViewPlayer.readyState has loaded metadata, or when the last segment is appended and there is a mismatch with the original duration.
Fired when playback has stopped because the end of the media resource was reached.
Fired when an error occurs.
Fired when the player goes into or out of fullscreen.
Fired when MultiViewPlayer.layout changes.
Fired when the player can render the media data at the current playback position for the first time.
Fired when the player determines the duration and dimensions of the media resources for all Views.
- See HTML media - network state events.
- The seekable range should be available as soon as the duration is known. However, certain browsers (e.g. Safari) do not make it available until the loadeddata event is fired.
Fired when the player has started loading the manifest of all Views.
Fired when MultiViewPlayer.paused changes to true.
- Fired after the pause() method has returned.
Fired when MultiViewPlayer.paused changes to false.
- Either fired after the play() method has returned, or when the MultiViewPlayer.autoplay attribute has caused playback to begin.
Fired when playback is ready to start after having been paused or delayed due to lack of media data.
Fired when the player loaded media data.
- For DASH streams, the event is fired every 350ms or for every byte received whichever is least frequent.
- See HTML media - network state events.
Fired when MultiViewPlayer.playbackRate changes.
Fired when MultiViewPlayer.readyState changes.
Fired when a View is removed.
Fired when MultiViewPlayer.seeking changes to false after the current playback position was changed.
Fired when MultiViewPlayer.seeking changes to true, and the player has started seeking to a new position.
Fired when the first View enters MultiViewPlayer.views or all views are removed.
Fired when the current playback position changed as part of normal playback or in an especially interesting way, for example discontinuously.
Fired when a view's enabled changes.
Fired when a View swapped positions in the list.
Fired when MultiViewPlayer.volume changes.
Fired when playback has stopped because the next frame is not available, but the player expects that frame to become available in due course.
The MultiViewPlayer API