Closed Bug 1620234 Opened 5 months ago Closed 4 months ago

Use the Resources API to fetch console messages


(DevTools :: Console, enhancement, P1)



(Fission Milestone:M6, firefox76 fixed)

Firefox 76
Fission Milestone M6
Tracking Status
firefox76 --- fixed


(Reporter: ochameau, Assigned: ochameau)


(Blocks 3 open bugs)


(Whiteboard: dt-fission-m2-mvp)


(1 file)

In order to address bug 1614291, we have to start listening for every resource, like console messages, network requests, page error, ... via the Resources API.
The Resources API will allow to listen for these resources earlier than the current setup where we use the TargetList to listen to new target, and request to listen after the target is created.
With the Resources API, we will know as early as the document starts loading that we have to start listening for something.

This bug is about focusing on only one usecase in DevTools. And only one usecase in the console: the console messages.

Blocks: 1620243
Blocks: 1576624

This demonstrates using the Resources API for the console messages,
using the existing actor methods. It helps proving that this will work against old runtimes.
But the plan is to followup in bug 1620243 so that we implement this code on the server side.
This will help getting rid of this LegacyImplementation code and have a simplier code on the server.

Assignee: nobody → poirot.alex
Priority: P3 → P1

Tracking Fission DevTools bugs for Fission Nightly (M6) milestone

Fission Milestone: --- → M6
Blocks: 1623699
Blocks: 1625900
Blocks: 1625905
Blocks: 1625909
Blocks: 1625910
Pushed by
Use the Resources API for console messages. r=jdescottes,nchevobbe
Blocks: 1625930
Blocks: 1625935
Blocks: 1625942
Blocks: 1625955
Blocks: 1625957
Blocks: 1625961
No longer blocks: 1625930
No longer blocks: 1625909
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 76
Regressions: 1626286
You need to log in before you can comment on or make changes to this bug.