-
-
Notifications
You must be signed in to change notification settings - Fork 760
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
Fix session payload for W3C #913
Conversation
@@ -268,12 +268,9 @@ public void writeTo(Appendable appendable) throws IOException { | |||
json.name(CAPABILITIES); | |||
json.beginObject(); | |||
|
|||
json.name(DESIRED_CAPABILITIES); | |||
json.name(ALWAYS_MATCH); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it looks like we were writing DESIRED_CAPABILITIES
twice before
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. Is anyone able to fix the C# client too?
@dpgraham It doesn't initiate w3c post this change instead it instantiates JSWP sesson so i'm revisiting this in sometime. |
@mykola-mokhnach @dpgraham I make the changes and java client session payload is as same as other clients now. For w3c,
For MJSWP,
Payload was like this before the change,
|
Looks good. |
Change list
Fix appium/dotnet-client#229
https://github.com/jlipps/simple-wd-spec#processing-capabilities
Types of changes
What types of changes are you proposing/introducing to Java client?
Put an
x
in the boxes that applyDetails
@dpgraham @mykola-mokhnach ping