Fixed #34675 -- Fixed creating remote webdriver for Selenium 4.10.0+. #17001
Conversation
In Selenium 4, the old way of setting capabilities for remote web drivers was deprecated.
|
The bug can be reproduced using a current Selenium version and running Selenium remotely. e. g. with |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hello! Thank you for your contribution 💪
As it's your first contribution be sure to check out the patch review checklist.
If you're fixing a ticket from Trac make sure to set the "Has patch" flag and include a link to this PR in the ticket!
If you have any design or process questions then you can ask in the Django forum.
Welcome aboard ⛵️!
Thank you Sarah! |
felixxm
changed the title
|
@hansegucker Thanks 👍 Welcome aboard ⛵ |
You're welcome! I am glad that I could help. Does this get any backporting to the 4.x.x series? |
Unfortunately not, we don't backport cleanups of new features. See Django’s release process for more details. |
Ok, I thought of this as a bug fix in the first way. But it actually seems to be supporting a newer version of Selenium with dropping support for old versions of Selenium. |
In Selenium 4, the old way of setting capabilities for remote web drivers was deprecated.