Closed Bug 1561930 Opened 1 year ago Closed 1 year ago

Calls to Cu.reportError() from chrome JS shouldn't be treated as "web content" messages

Categories

(DevTools :: Console, defect, P1)

defect

Tracking

(firefox70 fixed)

RESOLVED FIXED
Firefox 70
Tracking Status
firefox70 --- fixed

People

(Reporter: Gijs, Assigned: edenchuang)

References

(Blocks 2 open bugs, Regression)

Details

Attachments

(1 file)

What were you doing?

  1. Open Firefox with a clean profile
  2. Open regular devtools
  3. Enable chrome/add-on debugging in the devtools settings
  4. open the browser console (accel-shift-j)
  5. Run Cu.reportError("Hello");

What happened?

The hello message was not visible. It is only visible once you tick "Show content messages".

What should have happened?

The hello message should have been visible. It did not come from content and should not be filtered by that checkbox.

Flags: needinfo?(nchevobbe)

Thanks for the report Gijs!
Eden, any idea what's going on?

Flags: needinfo?(nchevobbe) → needinfo?(echuang)
Priority: -- → P1
Regressed by: 1544862

Sorry for the late response. Working on it.

Flags: needinfo?(echuang)
Keywords: checkin-needed
Assignee: nobody → echuang
Status: NEW → ASSIGNED

Pushed by cbrindusan@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1c1e27b9d73b
Correct the wrong attribute isFromChromeContext value for chrome context messages from Cu.reportError r=baku

Keywords: checkin-needed
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 70

Thanks Eden!

Blocks: 1613367
You need to log in before you can comment on or make changes to this bug.