-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
webdriver: fix expected key code for "Unidentified" keys #14415
base: master
Are you sure you want to change the base?
Conversation
Let’s see how the CI fares this time around. |
This PR is blocked on the required "Travis CI - Pull Request" check after #14499. In order to trigger it, I will close and reopen this PR. |
Shouldn't we also update the WebDriver spec? As it looks like the only appearance of "Unidentified" is currently for |
@andreastt can you please check my last comment? |
Yes, probably if it’s not there already. This is really a question for @burg, since I just rebased his original PR. |
@jgraham would you mind having a look at this PR? In our implementation for Firefox we also still fallback to an empty string. |
Per the UI Events specification (https://w3c.github.io/uievents-code/#key-legacy), keys such as \u00e0 (i.e., à) should have a code of "Unidentified". Some tests in key.py expect an empty value, which seems to be an oversight.
0c61d8d
to
7e5d396
Compare
@jgraham all the webdriver tests are passing which is interesting. Maybe I miss something? |
Per the UI Events specification
(https://w3c.github.io/uievents-code/#key-legacy), keys such as
\u00e0 (i.e., à) should have a code of "Unidentified". Some tests
in key.py expect an empty value, which seems to be an oversight.
This PR supersedes #12013.