Skip to content

Conversation

mykola-mokhnach
Copy link
Contributor

Change list

This is kind of dirty hack to make W3C protocol working properly with Appium. Currently Selenium has a bunch of hardcoded javascript snippets there, which are not going to work in mobile env. I'm also not sure how this is going to work in web context.

Perhaps, @TikhomirovSergey, you'll have better ideas on how to improve it. Check the recent conversation in java_client Slack group for more details.

Types of changes

  • 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)
Copy link
Contributor

@TikhomirovSergey TikhomirovSergey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks very good. I need to finish my work on capabilities to check all the scope on 1.8.0

@appium appium deleted a comment Jan 29, 2018
@mykola-mokhnach
Copy link
Contributor Author

I've moved the custom codec to a different package and addressed linker complains. Can you please check it one more time @TikhomirovSergey ?

@appium appium deleted a comment Jan 29, 2018
@appium appium deleted a comment Jan 29, 2018
@appium appium deleted a comment Jan 30, 2018
TikhomirovSergey added a commit that referenced this pull request Feb 4, 2018
…w3c_codec Addition to the #817. JsonToMobileElementConverter: fixed
@mykola-mokhnach mykola-mokhnach deleted the appium_w3c_codec branch February 7, 2018 10:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants