You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "alwaysMatch" capabilities are extracted into a required capabilities variable, while the "firstMatch" capabilities array are extracted into a all first match capabilities variable. That list is turned into a validated first match capabilities.
Then comes the bug.
The merged capabilities is constructed from validated first match capabilities, but if that's an empty list, merged capabilities will also be empty and we will reach "Return success with data null."
That should cause https://w3c.github.io/webdriver/#new-session to fail at the following step, "If capabilities’s is null, return error with error code session not created.", but that's not what should happen.
Suggested fix: If merged capabilities is an empty list, append required capabilities to it.
The text was updated successfully, but these errors were encountered:
It looks like there's a bug in https://w3c.github.io/webdriver/#dfn-capabilities-processing.
The "alwaysMatch" capabilities are extracted into a required capabilities variable, while the "firstMatch" capabilities array are extracted into a all first match capabilities variable. That list is turned into a validated first match capabilities.
Then comes the bug.
The merged capabilities is constructed from validated first match capabilities, but if that's an empty list, merged capabilities will also be empty and we will reach "Return success with data null."
That should cause https://w3c.github.io/webdriver/#new-session to fail at the following step, "If capabilities’s is null, return error with error code session not created.", but that's not what should happen.
Suggested fix: If merged capabilities is an empty list, append required capabilities to it.
The text was updated successfully, but these errors were encountered: