-
Notifications
You must be signed in to change notification settings - Fork 609
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
Headless mode: deprecation warning after upgrading #1525
Comments
@fuhlig I agree, and know this is planned for a future release. "new" is not new so much anymore ¯_(ツ)_/¯ I'll look into submitting a PR for the change today. |
Cheers mate |
dgrebb
added a commit
to dgrebb/BackstopJS
that referenced
this issue
Dec 23, 2023
dgrebb
added a commit
to dgrebb/BackstopJS
that referenced
this issue
Dec 24, 2023
dgrebb
added a commit
to dgrebb/BackstopJS
that referenced
this issue
Dec 24, 2023
dgrebb
added a commit
to dgrebb/BackstopJS
that referenced
this issue
Dec 24, 2023
This was referenced Dec 24, 2023
garris
pushed a commit
that referenced
this issue
Dec 24, 2023
* feat: defaults puppeteer to `new` headless mode (garris/BackstopJS/#1525) * fix: corrects playwr typo in `test/configs/playwright.json` * fix: supports string in `headless: "new"` for Playwright (#1534) * fix: corrects path for integration test pass/fail message scripts * documentation: update README with `new` headless mode information * documentation: adjust comment language in runPlaywright
Awesome, thanks @dgrebb! Have a happy new year! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After the upgraded Puppeteer dependency with the latest

6.3.1
release, Puppeteer/Chrome throws the following deprecation warning:docs:
https://developer.chrome.com/docs/chromium/new-headless?hl=en
While this is documented in the Backstop docs, it might be a better option is setting the headless mode to
new
by default to avoid deprecation warnings (and potential failures in future versions).The text was updated successfully, but these errors were encountered: