This adds a basic set of tests for interacting with various kinds
of DOM properties from the WebDriver commands Execute Script and
Execute Async Script.
Differential Revision: https://phabricator.services.mozilla.com/D28453
--HG--
extra : moz-landing-system : lando
There are approximately zero coverage for properties modified or set
by web content and through script evaluation. The only succcess
path test for Get Element Property is test_element, but it checks
an attribute already present in the prototype of the HTMLInputElement.
This patch adds tests where the property is defined through web
content. This uncovers a defect in Firefox, where Get Element
Property seemingly operates on the initial value of the attribute.
Differential Revision: https://phabricator.services.mozilla.com/D28463
--HG--
extra : moz-landing-system : lando
To prevent possible rate limits by the browser when running the
tests in verify mode, each test should run in its own tab.
Differential Revision: https://phabricator.services.mozilla.com/D20312
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Updating WebDriver new window command tests to switch window (#15043)
As originally implemented, the tests set the `handle` property of
the session instead of the `window_handle` property. So they don't
switch to the new window context before checking the
url, opener, and name. This commit fixes it.
--
wpt-commits: 363fd4ea3dd3f3ee5fde4f56bf26a3ad690b3b78
wpt-pr: 15043
Automatic update from web-platform-tests
webdriver: enable older browsers values for KeyboardEvent.key (#15204)
When propagating keyboard events, older browsers use different strings
for the "key" property of the KeyboardEvent object. This commit enables
the ability of the WebDriver tests for keyboard events to validate the
comparison to these older values in addition to the values used by
modern browsers. See the footnotes in the sections of the following:
https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/key/Key_Values
--
wpt-commits: b879d5c7d8103cdb6948c2a4d8d8b31f845dae7b
wpt-pr: 15204
Automatic update from web-platform-tests
webdriver: replicate "Alt" key workaround for IE WebDriver tests (#15208)
When the Alt key is pressed on Windows, it activates the menu bar for
the focused application. This means that subsequent operations must
first dismiss the menu before being able to carry on. This commit
for Internet Explorer duplicates the workaround for Alt keys from
the test_special_key_sends_keydown subtest in key_events.py to the
test_modifier_key_sends_correct_events subtest.
--
wpt-commits: 9366e48c23a041b398b3345ba8bce6fc66a934ff
wpt-pr: 15208
To have the same pre-conditions for all wdspec tests, the session fixture
has to set a default window position.
Depends on D16338
Differential Revision: https://phabricator.services.mozilla.com/D16340
--HG--
extra : moz-landing-system : lando
The WebDriver:TakeScreenshot command relied on the document element's
clientWidth/clientHeight, but should according to the WebDriver
specification use the viewport's dimensions.
Thanks-to: JinaJita <jitajina@gmail.com>
The WebDriver:TakeScreenshot command relied on the document element's
clientWidth/clientHeight, but should according to the WebDriver
specification use the viewport's dimensions.
Thanks-to: JinaJita <jitajina@gmail.com>
Marionette recently had changes made to its window maximisation algorithm
that lets us re-enable this test. It tests that session.window.maximize()
does not hang when the window is already maximised.
Differential Revision: https://phabricator.services.mozilla.com/D15582
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-testswebdriver: update scroll into view tests to support older user agents (#14130)
Removing the use of ES6 constructs (fat-arrow and object shortcut
syntax) as well as adding use of alternatives for user agents that
do not support window.scrollX and window.scrollY.
--
wpt-commits: fcef20974685c994c830a23eae88906449fe93f7
wpt-pr: 14130
Automatic update from web-platform-testsRemove ES6 object matching shorthand notation from WebDriver tests (#14015)
This change is to allow older user agents that do not support ES6
constructs to run the WebDriver tests.
--
wpt-commits: fc1a5b73230225faf32bfb85f3928ce154211b0a
wpt-pr: 14015
Automatic update from web-platform-testswebdriver: remove ES6 construct from in-view center point tests (#13799)
Older user agents (read: "Internet Explorer") do not support the
ES6 "fat arrow" construct. Changing the test event handler to the
older function-based syntax.
--
wpt-commits: b704e37ec97fe90b3a3d59c10f78c21907b5b576
wpt-pr: 13799
By throttling the Get Window Rect calls we avoid the buffer filling
up on Windows, and avoid errors such as: [Errno 10055] An operation
on a socket could not be performed because the system lacked
sufficient buffer space or because a queue was full
Differential Revision: https://phabricator.services.mozilla.com/D11410
--HG--
extra : moz-landing-system : lando
On some systems and window managers, such as macOS and when X11
forwarding an application across systems, there exists a 22px
window border that we cannot detect or do anything about. As this
test is to verify that the width/height changed beyond 800x600,
this assertion change should make the tests pass on more configurations.
Depends on D8409
Differential Revision: https://phabricator.services.mozilla.com/D8410
--HG--
extra : moz-landing-system : lando
The iterator returned by reversed() can apparently return None in
some configurations. WPT treats this as an in-test skip and errors
the test. To avoid this configuration-specific problem we use a
literal list.
Differential Revision: https://phabricator.services.mozilla.com/D11159
--HG--
extra : moz-landing-system : lando
Partially visible elements should according to WebDriver not be
scrolled into view. Drivers first run the in-view centre point
algorithm to determine if any portion of the targetted element is
in view, and if it is not, the element is scrolled into view.
As little as a 1 CSS pixel is sufficient for the element to deemed
in view. Implementations have had problems with deeming elements
out of view when a single pixel border has in fact been in view due
to faulty rounding of the target point, which is why we test a range
from 10 to 1 pixels.
Depends on D10821
Differential Revision: https://phabricator.services.mozilla.com/D10822
--HG--
extra : moz-landing-system : lando
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
--HG--
extra : moz-landing-system : lando
The WebDriver standard changed
in https://github.com/w3c/webdriver/pull/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
--HG--
extra : moz-landing-system : lando
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
--HG--
extra : moz-landing-system : lando
