browser UUIDs created by TabManager should not be shared between sessions
Categories
(Remote Protocol :: Agent, task, P3)
Tracking
(Not tracked)
People
(Reporter: jdescottes, Unassigned)
References
(Blocks 1 open bug, )
Details
For marionette and soon WebDriver BiDi, UUIDs for top level browsing contexts are created by the TabManager singleton.
Since it's a singleton, living in the parent process, all consumers will share the same UUIDs for the same top-level browsing context. This is fine when two consumers share the same session, but it should not be the case when different sessions are involved.
We should make sure to instantiate the TabManager and use a single instance per session.
|
||
Comment 1•3 years ago
|
||
Given that the WebDriver BiDi spec isn't clear about that, maybe we could share the window handles between sessions for now. At least until it's clear how we have to handle CDP in terms of the Puppeteer transition to WebDriver?
|
Reporter | |
Updated•3 years ago
|
|
|
Reporter | |
Comment 2•1 year ago
|
||
Seems like we want to go for session specific ids -> https://github.com/w3c/webdriver-bidi/pull/565
Description
•