Alex Rudenko
Alex Rudenko
@v-dev-cl if you do not have an init process in the container, the multi-process containers might not work as expected (e.g., the browser process might not get killed based on...
Not able to reproduce in the latest version. The script prints the expected result.
Fixed upstream https://chromium-review.googlesource.com/c/chromium/src/+/5155468
The issue got resolved in the latest versions using the new default headless mode: ``` const puppeteer = require('puppeteer'); (async() => { const browser = await puppeteer.launch(); const domain =...
It looks like notifications are covering push notifications. The following works in the latest versions. ``` const puppeteer = require('puppeteer'); (async() => { const browser = await puppeteer.launch(); const domain...
Not reproducible in the latest versions.
I am not able to reproduce if the sites are different, e.g., `example.com` and `wikipedia.org`. I think in the case of npm URLs the coverage is just very similar. The...
It looks like a problem with Firefox's implementation of CDP. Firefox team won't extend the functionality of their CDP implementation given the focus on WebDriver BiDi, therefore, closing this issue.
I believe this might have been fixed in the latest Chromium (there were quite a few regression with the new printing layout algorithm). Please re-open if still happens.
@Flamenco can you provide a test page?