Expand description
This domain allows detailed inspection of media elements
Structs§
- Disable
Params - Disables the Media domain. disable
- Disable
Returns - Disables the Media domain. disable
- Enable
Params - Enables the Media domain enable
- Enable
Returns - Enables the Media domain enable
- Event
Player Errors Raised - Send a list of any errors that need to be delivered. playerErrorsRaised
- Event
Player Events Added - 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
- Event
Player Messages Logged - Send a list of any messages that need to be delivered. playerMessagesLogged
- Event
Player Properties Changed - This can be called multiple times, and can be used to set / override / remove player properties. A null propValue indicates removal. playerPropertiesChanged
- Event
Players Created - Called whenever a player is created, or when a new agent joins and receives a list of active players. If an agent is restored, it will receive the full list of player ids and all events again. playersCreated
- Player
Error - Corresponds to kMediaError PlayerError
- Player
Error Builder - Player
Error Source Location - Represents logged source line numbers reported in an error. NOTE: file and line are from chromium c++ implementation code, not js. PlayerErrorSourceLocation
- Player
Error Source Location Builder - Player
Event - Corresponds to kMediaEventTriggered PlayerEvent
- Player
Event Builder - Player
Id - Players will get an ID that is unique within the agent context. PlayerId
- Player
Message - Have one type per entry in MediaLogRecord::Type Corresponds to kMessage PlayerMessage
- Player
Message Builder - Player
Property - Corresponds to kMediaPropertyChange PlayerProperty
- Player
Property Builder - Timestamp
Enums§
- Player
Message Level - 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.