Open
Bug 1819902
Opened 2 years ago
Updated 11 months ago
Support origin checks when deserializing a shared reference
Categories
(Remote Protocol :: WebDriver BiDi, enhancement, P2)
Remote Protocol
WebDriver BiDi
Tracking
(Not tracked)
NEW
People
(Reporter: whimboo, Unassigned)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [webdriver:backlog])
On bug 1770733 I'm going to add support for shared references. To be able to land the patch earlier we agreed on that support for origin checks can be done as a follow-up. Also because there is the open WebDriver BiDi issue which I would like to see clarified first - so that it is clear if we should throw an error or not.
|
Reporter | |
Comment 1•2 years ago
|
||
The PR https://github.com/w3c/webdriver-bidi/issues/376 has been merged.
|
|
Reporter | |
Updated•2 years ago
|
Points: --- → 5
Priority: -- → P2
Whiteboard: [webdriver:backlog]
|
|
Reporter | |
Updated•2 years ago
|
Priority: P2 → P1
Whiteboard: [webdriver:backlog] → [webdriver:m7]
|
|
Reporter | |
Updated•2 years ago
|
Priority: P1 → P2
|
||
Updated•1 year ago
|
Whiteboard: [webdriver:m7] → [webdriver:m8]
|
|
Reporter | |
Updated•1 year ago
|
Whiteboard: [webdriver:m8] → [webdriver:backlog]
|
||
Comment 2•11 months ago
|
||
As the way to verify this, we could also add a test case for browsingContext.locateNodes that uses a node from the one browsing context as startNode and then tries to locate in the another browsing context. See a discussion here: https://phabricator.services.mozilla.com/D196743#inline-1093416.
You need to log in
before you can comment on or make changes to this bug.
Description
•