Logpoints are only visible in the Browser Toolbox when "Show content messages" is enabled
Categories
(DevTools :: Debugger, defect, P2)
Tracking
(firefox-esr91 unaffected, firefox-esr102 wontfix, firefox102 wontfix, firefox103 wontfix, firefox104 fixed)
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox-esr102 | --- | wontfix |
| firefox102 | --- | wontfix |
| firefox103 | --- | wontfix |
| firefox104 | --- | fixed |
People
(Reporter: mconley, Assigned: nchevobbe)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
STR:
- Make sure that the Browser Toolbox is enabled, and then launch it
- Set a log point somewhere in some code that you know you can run easily. I use tabbrowser.js's "addTab" method, which is called when creating a new tab.
- Switch to the Console and (optionally) clear it
- Add a new tab in your Firefox window
ER:
The log point should be sent to the console.
AR:
No log point is sent to the console.
I did some mozregression, and here's the range:
nchevobbe, any idea which of these two bugs might have introduced this?
Updated•3 years ago
|
| Assignee | ||
Comment 1•3 years ago
|
||
Thanks for the report Mike
We got similar report from tgiles this last month, and in this case, checking "Show content messages" in the console setting menu was showing the logpoints.
With the STR from Comment 0, I can see the logpoints with the option enabled.
This was regressed by Bug 1760590, but it only look like it revealed the underlying issue, which is that we probably don't set the chromeContext property to the appropriate value when firing logpoints (probably in https://searchfox.org/mozilla-central/rev/3cb31675aeffd10f1f6ae7c40e24b254da7798e5/devtools/server/actors/utils/logEvent.js#72-81 , called from https://searchfox.org/mozilla-central/rev/3cb31675aeffd10f1f6ae7c40e24b254da7798e5/devtools/server/actors/breakpoint.js#196-201).
Comment 2•3 years ago
|
||
Set release status flags based on info from the regressing bug 1760590
| Assignee | ||
Comment 3•3 years ago
|
||
We only set it to true if the target the breakpoint
was hit in is a parent process target, which should
be enough.
Updated•3 years ago
|
Comment 5•3 years ago
|
||
| bugherder | ||
Updated•3 years ago
|
Updated•3 years ago
|
Description
•