Closed Bug 1792439 Opened 2 months ago Closed 2 months ago

Prototype a WebConsole UI using WebDriver BiDi commands

Categories

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

task
Points:
5

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jdescottes, Assigned: Sasha)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [webdriver:m5])

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).

Summary: Prototype a webconsole UI using webdriver BiDi commands → Prototype a WebConsole UI using WebDriver BiDi commands

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.

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

Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.