Support executing “script.evaluate” and “script.callFunction” for browsing contexts in the parent process
Categories
(Remote Protocol :: WebDriver BiDi, task, P2)
Tracking
(Not tracked)
People
(Reporter: whimboo, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: [webdriver:m15])
To support the evaluation of JavaScript in the parent process, the existing JSWindowActor implementation for the MessageHandler can be reused. No additional work is required because the actor can be enabled for Chrome by setting the includeChrome field in the actor configuration to true during registration.
This feature should only be taken into account when system access is enabled to avoid unintended side effects in the normal operational mode.
Once enabled, the JSWindowActor will automatically route IPC messages to the appropriate target BrowsingContext, whether it resides in the content or parent process.
Also we do not want to enable support for the parent process for all available WebDriver BiDi commands (particularly event subscriptions) at that point. So an additional internal flag will most likely be required. It can be passed by the two evaluation commands to the underlying MessageHandler to indicate that it is allowed to forward the command to the parent process. Commands that do not set this flag will be aborted with an "operation not supported" error when a browsing context of the parent process is referenced.
Description
•