Open
Bug 1821460
Opened 1 year ago
Updated 1 year ago
Handle actions "Input state" on the top-level browsing context
Categories
(Remote Protocol :: WebDriver BiDi, task, P2)
Remote Protocol
WebDriver BiDi
Tracking
(Not tracked)
NEW
People
(Reporter: whimboo, Unassigned)
References
(Blocks 3 open bugs, )
Details
(Whiteboard: [webdriver:backlog])
Bug 1792090 will implement the basics for perform actions with the limitation that the input states are stored on the actual browsing context and not the top-level browsing context as it should be per WebDriver classic spec.
We should be able to use the WebDriverProcessData actor to store the state equally to the nodeCache but per top-level browsing context.
The question still is if it would be fine for the child actor or if we have to store the data in the parent actor.
|
Reporter | |
Updated•1 year ago
|
Summary: Make → Handle actions "Input state" on the top-level browsing context
|
|
Reporter | |
Comment 1•1 year ago
|
||
As discussed today it might not happen that often that users will interact with elements in both the top-level browsing context and in child browsing contexts. That means the risk of mixing input state is low, but we will add this bug as optional for M7.
Severity: -- → S3
Priority: -- → P2
Whiteboard: [webdriver:backlog]
|
|
Reporter | |
Updated•1 year ago
|
Points: --- → 3
You need to log in
before you can comment on or make changes to this bug.
Description
•