Skip to content
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. #12013

Closed

Conversation

burg
Copy link
Contributor

@burg burg commented Jul 16, 2018

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.

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.
@burg
Copy link
Contributor Author

burg commented Jul 18, 2018

I don't quite understand this CI failure. Did Chrome previously pass these tests?

ERROR:/home/travis/build/web-platform-tests/wpt/tools/ci:| /webdriver/tests/actions/key.py | test_single_printable_key_sends_correct_events["-Quote] | ERROR, FAIL | teardown error;UnknownCommandException: unknown command (404): (Session infochrome=69.0.3486.0) |

@jgraham
Copy link
Contributor

jgraham commented Sep 25, 2018

The CI failure is a bug in the harness that makes it look like Chrome gets multiple results for tests it fails. If this PR is still valid I can merge it.

@whimboo
Copy link
Contributor

whimboo commented Sep 25, 2018

The PR would need an update given that the tests have been relocated and refactored.

@andreastt
Copy link
Member

@burg Do you want to have a stab at updating the PR? I think it’s a worthwhile fix to have.

@andreastt
Copy link
Member

Rebased in #14415.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants