1792439 - Prototype a WebConsole UI using WebDriver BiDi commands

Status: RESOLVED FIXED

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

Description

[Julian Descottes [:jdescottes]]

We want to prototype a simple webconsole UI relying on WebDriver BiDi events and commands.

This UI should be a web application connecting to a Firefox instance started with remote debugging enabled (similar to the web client).

Comment 1

[Alexandra Borovova [:Sasha]]

The development was happening on Github in https://github.com/lutien/bidi-webconsole-prototype.
Demo: https://lutien.github.io/bidi-webconsole-prototype/

Discovered limitations/missing features of BiDi:

• log.entryAdded event and script.evaluate don't return enough data to fully mimic console behavior, especially for the objects, which values are not serialized (e.g. functions, WeakMap, window,..). Potential work around: sending the script.callFunction command with handle to get additional data from content process.

• A currently hidden feature of showing an url of a browsing context next to a console message, to see where it comes from, would require implementation of browsingContext.navigationStarted event to call browsingContext.getTree command earlier. Right now, it's happening on browsingContext.load event, which is too late for some log.entryAdded events to show the correct data.

Comment 2

[Alexandra Borovova [:Sasha]]

The repo was moved to https://github.com/firefox-devtools/bidi-webconsole-prototype
The demo is now on: https://firefox-dev.tools/bidi-webconsole-prototype/

Comment 3

[Alexandra Borovova [:Sasha]]

This bug was planned only for one week, the follow-up work will be planned in the scope of bug 1794433.