Closed Bug 1567726 Opened 5 years ago Closed 5 years ago

"Error: Can't find the actor ID for stylesheets" when opening browser content toolbox console

Categories

(DevTools :: Console, defect, P1)

63 Branch
defect

Tracking

(firefox-esr60 unaffected, firefox-esr68 wontfix, firefox68 wontfix, firefox69 wontfix, firefox70 fixed)

RESOLVED FIXED
Firefox 70
Tracking Status
firefox-esr60 --- unaffected
firefox-esr68 --- wontfix
firefox68 --- wontfix
firefox69 --- wontfix
firefox70 --- fixed

People

(Reporter: Oriol, Assigned: ochameau)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

  1. Load about:blank (or any page with a content process)
  2. Open the browser content toolbox.
    You can use the menu or run this in the browser console:
    var { require } = ChromeUtils.import("resource://devtools/shared/Loader.jsm");
    var { gDevToolsBrowser } = require("devtools/client/framework/devtools-browser");
    gDevToolsBrowser.openContentProcessToolbox(gBrowser);
    

The browser console shows this error:

Error: Can't find the actor ID for stylesheets from root or target actor's form.

I'm using the code above in my patch for bug 1544175, but the error made the test fail. I had to add toolbox.selectTool("jsdebugger"); in order to avoid the problem, this shouldn't be necessary.

Regression window: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=72a737dd8639ab72ddc96d1144f44b06507b915e&tochange=ecb1726e2a622b8181c0d3ef30240a581ceedaf0

Alex, could you have a look please?

Flags: needinfo?(poirot.alex)

Thanks a lot for the bug report and the regression window!

Flags: needinfo?(poirot.alex)
Assignee: nobody → poirot.alex

This actor isn't implemented for processes, but only by browsing context targets.

Status: NEW → ASSIGNED
Priority: -- → P1
Pushed by ccoroiu@mozilla.com:
https://hg.mozilla.org/mozilla-central/rev/9522215f449a
Do not request stylesheets front for content processes in the source map service. r=yulia
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 70

Is this something we should consider uplifting to Beta for Fx69 or can it ride to release with Fx70?

Flags: needinfo?(poirot.alex)

This exception may mean that the source maps are broken in the browser content toolbox, but we are not using them there.
So I don't think it is important to uplift.

Flags: needinfo?(poirot.alex)
QA Whiteboard: [qa-70b-p2]
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: