e89e264a16
This corresponds to Chromium 85.0.4182.0. This roll includes: - Enable SameSiteByDefaultCookies and CookiesWithoutSameSiteMustBeSecure https://crrev.com/c/2231445 - [FlexNG] Enable FlexNG by default https://crrev.com/c/2216595 Closes #6151.
22 lines
1.3 KiB
Markdown
22 lines
1.3 KiB
Markdown
<!-- Do not edit this file. It is automatically generated by API Documenter. -->
|
|
|
|
[Home](./index.md) > [puppeteer](./puppeteer.md) > [Protocol](./puppeteer.protocol.md) > [Media](./puppeteer.protocol.media.md) > [PlayerMessage](./puppeteer.protocol.media.playermessage.md)
|
|
|
|
## Protocol.Media.PlayerMessage interface
|
|
|
|
Have one type per entry in MediaLogRecord::Type Corresponds to kMessage
|
|
|
|
<b>Signature:</b>
|
|
|
|
```typescript
|
|
export interface PlayerMessage
|
|
```
|
|
|
|
## Properties
|
|
|
|
| Property | Type | Description |
|
|
| --- | --- | --- |
|
|
| [level](./puppeteer.protocol.media.playermessage.level.md) | ('error' \| 'warning' \| 'info' \| 'debug') | 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. (PlayerMessageLevel enum) |
|
|
| [message](./puppeteer.protocol.media.playermessage.message.md) | string | |
|
|
|