Browser console doesn't list expected content (Windows 10)
Categories
(DevTools :: Console, defect)
Tracking
(firefox-esr78 unaffected, firefox85 unaffected, firefox86 unaffected, firefox87 verified, firefox88 verified)
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox85 | --- | unaffected |
firefox86 | --- | unaffected |
firefox87 | --- | verified |
firefox88 | --- | verified |
People
(Reporter: aflorinescu, Assigned: ochameau)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
|
Details | Review |
[Description:]
Browser console shows blank: no debug/logging messages, although the logs are enabled from config.
[Environment:]
Windows 10 / 87.0a1 2021-02-19
not reproducible Mac 10.14.6 and Ubuntu 20.04 / 87.0a1 2021-02-19
[Steps:]
- New profile.
- Start up Firefox.
- Open about:config:
set app.normandy.logging.level to 0
set browser.search.log to true - Close and reopen the browser.
- Open browser console (Ctrl+Shift+J)
[Actual Result:]
Blank browser console.
[Expected Result:]
At least the logs for search and normandy should be listed.
[Regression Range:]
Bug 1642599 - [devtools] Enable all console messages server support everywhere. r=ochameau.
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
Bug 1642599 should be backed out and revisited. This breaks console resources for content process targets.
That's because resource-available-form event isn't declared on content process targets:
https://searchfox.org/mozilla-central/source/devtools/shared/specs/targets/content-process.js#35-43
Registering the events will highlight more work because bug 1642599's patch will spawn duplicated messages as per:
https://phabricator.services.mozilla.com/D103285#3357864
Assignee | ||
Comment 2•4 years ago
|
||
The missing resource-available-form event on content process target specifications
break console resources for content process targets.
Adding this event will probably create duplicate and so requires some more analysis.
Comment 3•4 years ago
|
||
:ochameau, since this bug is a regression, could you fill (if possible) the regressed_by field?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
Comment 5•4 years ago
|
||
bugherder |
Comment 6•4 years ago
|
||
The patch landed in nightly and beta is affected.
:ochameau, is this bug important enough to require an uplift?
If not please set status_beta
to wontfix
.
For more information, please visit auto_nag documentation.
Comment 7•4 years ago
|
||
(In reply to Release mgmt bot [:sylvestre / :calixte / :marco for bugbug] from comment #6)
The patch landed in nightly and beta is affected.
:ochameau, is this bug important enough to require an uplift?
If not please setstatus_beta
towontfix
.For more information, please visit auto_nag documentation.
yes, let's uplift, I'll do the request
Comment 8•4 years ago
|
||
Comment on attachment 9204520 [details]
Bug 1693854 - Disable console resources in targets other than tabs.
Beta/Release Uplift Approval Request
- User impact if declined: Some messages won't be visible in the Browser Console
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): A flag that we flipped during the 87 cycle was reverted to its original value, and a test was added
- String changes made/needed:
Comment 9•4 years ago
|
||
Comment on attachment 9204520 [details]
Bug 1693854 - Disable console resources in targets other than tabs.
Approved for 87.0b3.
Comment 10•4 years ago
|
||
bugherder uplift |
Updated•4 years ago
|
Comment 12•4 years ago
|
||
verified fix with WIndows10 64bit, Macos 10.15 and ubuntu 20
using Firefox beta 87.0b5 & Firefox Nightly 88.0a1
browser console now shows data.
Description
•