Open Bug 1713440 Opened 4 months ago Updated 6 days ago

MessageHandler: Support chrome window contexts

Categories

(Remote Protocol :: WebDriver BiDi, task, P3)

task
Points:
8

Tracking

(Not tracked)

People

(Reporter: jdescottes, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [bidi-m2-mvp])

Add support for chrome window contexts. This is currently not handled in the prototype stack.

Even for such parent process contexts, a dedicated CommandsHandler should be created for the target chrome window context.
We might reuse the same transport class as the one created for Bug 1713439 or come up with a dedicated one.

Whiteboard: [bidi-m1-mvp]
Points: --- → 8
Priority: -- → P3
Summary: CommandsHandler: Support chrome window contexts → MessageHandler: Support chrome window contexts
Blocks: 1722679

As a proof of concept based on the current MessageHandler patches, the following patch allows to capture log events emitted from a chrome window.

https://hg.mozilla.org/try/rev/8d985698a779b2bebcd8fc042be13b37c87a8b7d

It does two things:

  • relaxes the filtering performed in the FrameTransport in order to also accept parent process browsing contexts
  • adds the includeChrome flag to the MessageHandlerFrameActor definition

With this, the following manual test should work:

  • start firefox with --remote-debugging-port
  • direct connect to BiDi with a websocket client
  • create a session
  • send a session.subscribe command for ['log.entryAdded']
  • open the BrowserToolbox
  • run gBrowser.ownerGlobal.console.log("TEST") (gBrowser.ownerGlobal points to the Chrome window)
  • you should receive an entryAdded event
Whiteboard: [bidi-m1-mvp] → [bidi-m2-mvp]
Priority: P3 → --
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.