ReadonlyabortReadonlycanFired when the user agent can play the media, but estimates that not enough data has been loaded to play the media up to its end without having to stop for further buffering of content.
readyState will be at least PlaybackReadyState.HAVE_FUTURE_DATA
ReadonlycanFired when the user agent can play the media, and estimates that enough data has been loaded to play the media up to its end without having to stop for further buffering of content.
readyState will be at least PlaybackReadyState.HAVE_ENOUGH_DATA
ReadonlydurationFired when the duration attribute has been updated.
ReadonlyemptiedFired when the media has become empty; for example, this event is sent if the media has already been loaded (or partially loaded), and the load() method is called to reload it.
readyState will be PlaybackReadyState.HAVE_NOTHING
ReadonlyendedFired when playback or streaming has stopped because the end of the media was reached or because no further data is available.
ReadonlyerrorDispatched when the media element dispatches an error.
ReadonlyloadedFired when the frame at the current playback position of the media has finished loading; often the first frame.
readyState will be at least PlaybackReadyState.HAVE_CURRENT_DATA
ReadonlyloadedFired when the metadata has been loaded.
readyState will be at least PlaybackReadyState.HAVE_METADATA
ReadonlyloadFired when the browser has started to load a resource.
ReadonlyloopedFired when ReadonlyPlaybackController.loop is true and playback has looped to track beginning.
ReadonlymutedFired when the mute status has changed.
ReadonlypauseFired when a request to pause an activity is handled and the activity has entered its paused state, most commonly after the media has been paused through a call to the element's pause() method.
ReadonlyplayFired when the paused property is changed from true to false, as a result of the play method, or the autoplay attribute.
ReadonlyplayedFired when playback has stopped, for any reason.
When media begins playing, a playing event is emitted. If playback stops due to 'pause',
'seeking', 'emptied', 'waiting', or 'ended', then played will be fired.
ReadonlyplayingFired after playback is first started, and whenever it is restarted. For example, it is fired when playback resumes after having been paused or delayed due to lack of data.
ReadonlyplayFired when ReadonlyPlaybackController.playIsPending has changed.
ReadonlyplayFired if play() has been attempted, but rejected.
ReadonlyprogressFired periodically as the browser loads a resource.
ReadonlyrateFired when the playback rate has changed.
ReadonlyreadyFired when ReadonlyPlaybackController.readyState has changed.
This is fired when any of the following events have fired: loadedData, loadedMetadata canPlay canPlayThrough emptied waiting
ReadonlyresetEmitted when the error state has been reset.
ReadonlyseekedFired when a seek operation completed, the current playback position has changed, and the Boolean seeking attribute is changed to false.
ReadonlyseekingFired when a seek operation starts, meaning the Boolean seeking attribute has changed to true and the media is seeking a new position.
ReadonlytimeFired when the time indicated by the currentTime attribute has been updated.
ReadonlyvolumeFired when the volume has changed.
ReadonlywaitedFired when waiting has completed. This will be emitted after a waiting event when playback has resumed, paused, or unloaded.
ReadonlywaitingFired when playback has stopped because of a temporary lack of data.
Note: this includes during initial loading or after a seek and data is needed to buffer. Will not be emitted when paused.
ReadonlywaitingPlayback is blocked waiting for a key.
Fired when the resource was not fully loaded, but not as the result of an error.