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

[Gecko Bug 1502864] webdriver: add tests for keyboard interactability for <input type=file #13885

Merged
merged 4 commits into from
Nov 5, 2018

Conversation

moz-wptsync-bot
Copy link
Collaborator

Normally all interactability tests are centralised in interactability.py,
but the WebDriver standard recently changed to apply a special
set of interactability checks specifically for .
These tests ensure the special code paths are invoked for form controls.

Differential Revision: https://phabricator.services.mozilla.com/D10269

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1502864
gecko-commit: 7616e25a07b38086a8a615be0158e93cbaa0a59a
gecko-integration-branch: central
gecko-reviewers: jgraham

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

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

Already reviewed downstream.

@andreastt
Copy link
Member

@jgraham This was backed out of central, then pushed again to autoland, then @wpt-pr-bot closed this PR without merging it. How does it handle a re-landing?

Normally all interactability tests are centralised in interactability.py,
but the WebDriver standard recently changed to apply a special
set of interactability checks specifically for <input type=file>.
These tests ensure the special code paths are invoked for form controls.

Differential Revision: https://phabricator.services.mozilla.com/D10269

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1502864
gecko-commit: 301c1d1d5e14f001e373b329de611460a177dec8
gecko-integration-branch: central
gecko-reviewers: jgraham
The WebDriver standard changed
in w3c/webdriver#1325 to align with
chromedriver's behaviour of permitting interaction with hidden
<input type=file> elements.

DOM elements can be hidden, i.e. not rendered, in two ways: through
applying the "hidden" DOM attribute or by setting the "display:
none" CSS style.

Depends on D10269

Depends on D10269

Differential Revision: https://phabricator.services.mozilla.com/D10270

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1502864
gecko-commit: 6fb763dc8e9b832ddd4aa24179b74db94a229c35
gecko-integration-branch: central
gecko-reviewers: jgraham, whimboo
The new strictFileInteractabilityTests capability takes a boolean and
can unconditionally be set to both true and false.  It is permitted
to be undefined.

Depends on D10270

Depends on D10270

Differential Revision: https://phabricator.services.mozilla.com/D10271

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1502864
gecko-commit: dc69c736701f2b7b405e50ed92e3384e44e233c7
gecko-integration-branch: central
gecko-reviewers: jgraham
Depends on D10271

Depends on D10271

Differential Revision: https://phabricator.services.mozilla.com/D10272

bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1502864
gecko-commit: 7a89ca7dca2d3df428a4a8d94c31cd5c48af3162
gecko-integration-branch: central
gecko-reviewers: jgraham
@andreastt
Copy link
Member

nm, looks like it will!

@andreastt
Copy link
Member

Impossible to tell from the log what is going on because:

Log reached capacity (3145728 bytes); output disabled.

@jgraham jgraham merged commit 31c7091 into master Nov 5, 2018
@moz-wptsync-bot moz-wptsync-bot deleted the gecko/1502864 branch November 5, 2018 11:37
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.

4 participants