puppeteer/new-docs/puppeteer.protocol.media.playermessage.level.md
Johan Bay e89e264a16
feat(chromium): roll Chromium to r782078 (#6250)
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.
2020-07-20 17:17:06 +02:00

14 lines
1.1 KiB
Markdown

<!-- Do not edit this file. It is automatically generated by API Documenter. -->
[Home](./index.md) &gt; [puppeteer](./puppeteer.md) &gt; [Protocol](./puppeteer.protocol.md) &gt; [Media](./puppeteer.protocol.media.md) &gt; [PlayerMessage](./puppeteer.protocol.media.playermessage.md) &gt; [level](./puppeteer.protocol.media.playermessage.level.md)
## Protocol.Media.PlayerMessage.level property
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)
<b>Signature:</b>
```typescript
level: ('error' | 'warning' | 'info' | 'debug');
```