-
Notifications
You must be signed in to change notification settings - Fork 607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Puppeteer old Headless deprecation warning #1485
Comments
Thanks for raising! Looks like we should update this behavior to allow updating with non-bool values and to make a decision on how backstop should interpret the old backstop default value going forward. Would be happy to review a PR on this. Cheers |
The new mode however should be treated with care - e.g. https://bugs.chromium.org/p/chromium/issues/detail?id=1440046 the performance loss is extreme and at least for me in docker I can't even use the new mode because angle fails to initialize the egl rendering acceleration and just quits, I am forced at the moment to use the "old" one and I guess I am not alone with that. So if the new one is considered make it configurable for the user and better stay on the old one for the moment. |
Guys, thanks a lot for great tool! |
…breaking fashion (garris#1485) (garris#1486) Puppet and Playwright complain and pollute logs with warnings about "new headless mode". This reads the value set in backstop.json, or uses true if 'headless' is not set, or 'new', as a string. README updated with details. Closes: garris#1485
Another update on this with PR #1535 1535 Playwright is going to stay defaulted to "old" headless mode for now, but Puppeteer will start default to @tkrah I included a fallback for "old" in Puppeteer, which, ironically, can be set by passing |
Seeing a bunch of these in the latest release on docker hub.
Seems mostly informational and not problematic but there's just a swarm of them when testing. Quick skim looks to be caused by the
headless: <!!!config.debugWindow>
logic which passes true. The boolean cast also means we can't put 'new' in the config and "opt in" so I haven't tested if opting in is functional or not.The text was updated successfully, but these errors were encountered: