Open
Bug 1401163
Opened 7 years ago
Updated 2 years ago
Pointer Interactable checks not used when implicitly waiting for elements in Element Interaction commands
Categories
(Remote Protocol :: Marionette, enhancement, P2)
Tracking
(Not tracked)
NEW
People
(Reporter: automatedtester, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: pi-marionette-spec)
In the webdriver specification it says that we need to wait for an element to become interactable.
https://w3c.github.io/webdriver/webdriver-spec.html#dfn-interactable-element
Reporter | ||
Comment 1•7 years ago
|
||
Issue raised in https://github.com/mozilla/geckodriver/issues/960
Comment 2•7 years ago
|
||
Also see the webdriver spec issue for getting that implemented: https://github.com/w3c/webdriver/issues/1097
Comment 3•7 years ago
|
||
Is this still relevant? I don’t entirely understand what it entails to wait for an element to become interactable. Are we expecting Element.scrollIntoView not to be synchronous?
Flags: needinfo?(dburns)
Priority: P3 → P2
Reporter | ||
Comment 4•7 years ago
|
||
We are waiting for an element to become visible and to have scrolled into view before we do a click if there is an implicit wait.
Flags: needinfo?(dburns)
Comment 5•7 years ago
|
||
Neither the spec nor the description of this bug explains exactly what needs to change in Marionette.
Updated•2 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•