Module chromiumoxide::cdp::browser_protocol::media [−][src]
This domain allows detailed inspection of media elements
Structs
DisableParams | Disables the Media domain. disable |
DisableReturns | Disables the Media domain. disable |
EnableParams | Enables the Media domain enable |
EnableReturns | Enables the Media domain enable |
EventPlayerErrorsRaised | Send a list of any errors that need to be delivered. playerErrorsRaised |
EventPlayerEventsAdded | Send events as a list, allowing them to be batched on the browser for less congestion. If batched, events must ALWAYS be in chronological order. playerEventsAdded |
EventPlayerMessagesLogged | Send a list of any messages that need to be delivered. playerMessagesLogged |
EventPlayerPropertiesChanged | This can be called multiple times, and can be used to set / override / remove player properties. A null propValue indicates removal. playerPropertiesChanged |
EventPlayersCreated | Called whenever a player is created, or when a new agent joins and recieves a list of active players. If an agent is restored, it will recieve the full list of player ids and all events again. playersCreated |
PlayerError | Corresponds to kMediaError PlayerError |
PlayerErrorBuilder | |
PlayerEvent | Corresponds to kMediaEventTriggered PlayerEvent |
PlayerEventBuilder | |
PlayerId | Players will get an ID that is unique within the agent context. PlayerId |
PlayerMessage | Have one type per entry in MediaLogRecord::Type Corresponds to kMessage PlayerMessage |
PlayerMessageBuilder | |
PlayerProperty | Corresponds to kMediaPropertyChange PlayerProperty |
PlayerPropertyBuilder | |
Timestamp |
Enums
PlayerErrorType | |
PlayerMessageLevel | Keep in sync with MediaLogMessageLevel We are currently keeping the message level ‘error’ separate from the PlayerError type because right now they represent different things, this one being a DVLOG(ERROR) style log message that gets printed based on what log level is selected in the UI, and the other is a representation of a media::PipelineStatus object. Soon however we’re going to be moving away from using PipelineStatus for errors and introducing a new error type which should hopefully let us integrate the error log level into the PlayerError type. |