Missing Get Element Property tests for mutated web content
Categories
(Testing :: geckodriver, enhancement, P1)
Tracking
(firefox68 fixed)
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: ato, Assigned: ato)
References
Details
Attachments
(2 files)
We have quite few tests for Get Element Property in general, but
specifically we’re missing tests for returning properties that have
been mutated by executed scripts.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Nothing remarkable in this patch.
Assignee | ||
Comment 2•5 years ago
|
||
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.
Assignee | ||
Comment 3•5 years ago
|
||
Pushed by atolfsen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/f81199595401 webdriver: sanitise get_element_property/get.py; r=automatedtester https://hg.mozilla.org/integration/autoland/rev/728a88d61132 webdriver: add Get Element Property tests for mutated web content; r=automatedtester
Comment 5•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/f81199595401
https://hg.mozilla.org/mozilla-central/rev/728a88d61132
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/16526 for changes under testing/web-platform/tests
Upstream PR merged
Updated•4 years ago
|
Description
•