Skip to content
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

Testing of warnings of unsaved changes #56

Open
treiher opened this issue Sep 4, 2024 · 0 comments
Open

Testing of warnings of unsaved changes #56

treiher opened this issue Sep 4, 2024 · 0 comments

Comments

@treiher
Copy link
Owner

treiher commented Sep 4, 2024

In Chromium 127 the steps to fire beforeunload has been changed (see SeleniumHQ/selenium#14290 (comment)). Enabling BiDi mode (chrome_options.set_capability("webSocketUrl", value=True)) solves this issue.

Apparently, in Chromium 128 the behavior changed again. SeleniumHQ/selenium#14468 (comment) suggests to set the "unhandledPromptBehavior" to "ignore". Unfortunately, this didn't solve the issue for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant