chore: Add non-W3C endpoints remove from Selenium client by valfirst · Pull Request #2093 · appium/java-client
Conversation
Change list
Closes #2090.
Types of changes
What types of changes are you proposing/introducing to Java client?
Put an x in the boxes that apply
- No changes in production code.
- Bugfix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
Details
See #2090 and linked issues.
@mykola-mokhnach yes, but I think it'll be better to do it upon a new release. Selenium team will release a new client, then we'll be needed to release a new version of Appium Java client. The actual version numbers will be known only after the releases.
@valfirst I also assume we'd have eventually to move location getting and setting APIs to java client as they got deprecated in Selenium
valfirst
deleted the
add-non-w3c-endpoints-removed-from-selenium-client
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters