![]() ![]() Since Puppeteer (in all configurations) controls a desktop version of Chromium/Chrome, features that are only supported by the mobile version of Chrome are not supported.You should only use this configuration if you need an official release of Chrome that supports these media formats.) (However, it is possible to force Puppeteer to use a separately-installed version Chrome instead of Chromium via the executablePath option to puppeteer.launch. This means that Puppeteer does not support licensed formats such as AAC or H.264. Puppeteer is bundled with Chromium-not Chrome-and so by default, it inherits all of Chromium's media-related limitations.(For example, video playback/screenshots is likely to fail.) There are two reasons for this: You may find that Puppeteer does not behave as expected when controlling pages that incorporate audio and video. ![]() launch ( ) Q: What features does Puppeteer not support? Give it a spin: Getting Started InstallationĬonst browser = await puppeteer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |