-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[py] Fix WPEWebKit launch failure due to invalid alwaysMatch capabilities #16178
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
Conversation
fixed WPE WebKit fail
|
|
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨Explore these optional code suggestions:
|
||||||||||||||
|
@11byte I'm going to reject this. Your change essentially just changes Also, the code is very hacky and doesn't even work. This is not the proper place to change the I'm not sure why you think this fixes the issue. but it definitely doesn't. I described a proper fix here: |
User description
🔗 Related Issues
Fixes #15541
💥 What does this PR do?
This PR fixes a bug where launching the WPE WebKit browser via Python bindings (
webdriver.WPEWebKit()) fails with the error:The issue stems from the WPE WebKit driver rejecting W3C-style
alwaysMatchcapabilities, which are automatically generated when passingoptions=Options()toRemoteWebDriver.🔧 Implementation Notes
options=optionswith a minimal, manually defineddesired_capabilitiesdictionary:{"browserName": "wpewebkit"}