WebConsole can end up broken when navigating between pages that would create warning groups
Categories
(DevTools :: Console, defect, P2)
Tracking
(firefox89 fixed, firefox90 fixed)
People
(Reporter: kernp25, Assigned: nchevobbe)
Details
Attachments
(4 files, 6 obsolete files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:87.0) Gecko/20100101 Firefox/87.0
Steps to reproduce:
- Install https://addons.mozilla.org/firefox/addon/docx-viewer/
- Open a new tab
- Make sure
devtools.webconsole.persistlogistrue - Open the developer console (https://developer.mozilla.org/en-US/docs/Tools/Web_Console)
- Open https://calibre-ebook.com/downloads/demos/demo.docx
Actual results:
It will stop logging the Navigated to... in the console.
After some more browsing the console gets broken (see picture).
Expected results:
Should just work as expected.
Comment 1•5 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Console' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Update 2: You need to open google and search for filetype:docx test.
Then click on any link that points to a docx file.
In this video the toolbar will only be removed but the logging will continue working.
(In reply to kernp25 from comment #8)
Created attachment 9216416 [details]
SswzPiSXuN.mp4In this video the toolbar will only be removed but the logging will continue working.
This happens also with devtools.webconsole.persistlog set to false.
| Assignee | ||
Comment 10•5 years ago
|
||
Hello kernps25, thanks for the report.
Could you paste the content of the browser console here (https://developer.mozilla.org/en-US/docs/Tools/Browser_Console) ? that might help
| Reporter | ||
Comment 11•5 years ago
|
||
| Reporter | ||
Comment 12•5 years ago
|
||
For the toolbar removed only bug (this bug seems to happen, if the page is still loading and then navigated back).
| Reporter | ||
Comment 13•5 years ago
|
||
The browser console content for the bug i reported first.
| Assignee | ||
Comment 14•5 years ago
|
||
I was able to reproduce on 87 once, but I was able to get the new message once I did evaluated an expression in the console.
I wasn't able to reproduce on Firefox 89, and I know we did some changes around those areas.
Would you be able to check on Firefox Nightly if you still see the issue?
| Reporter | ||
Comment 15•5 years ago
|
||
On Firefox Nightly (89.0a1 (2021-04-16) (64-Bit)) it will show TypeError: can't access property "push", state.warningGroupsById.get(...) is undefined in the browser console.
STR for the stop logging bug:
- Open a new tab
- Make sure
devtools.webconsole.persistlogistrue - Open the web console (https://developer.mozilla.org/en-US/docs/Tools/Web_Console)
- Open google and search for
filetype:docx test - Click on a link that points to a docx file
| Reporter | ||
Comment 16•5 years ago
|
||
The bug with the toolbar being removed seems fixed in Firefox Nightly.
Updated•5 years ago
|
Updated•5 years ago
|
| Assignee | ||
Comment 17•5 years ago
|
||
Looks like there's a race condition that can be triggered where a warning group message could be "repeated" with a warning message from a previous navigation, which would make the new one being ignored and causing issues further down the road.
I'll work on a proper patch and test for this on Monday (the issue is probably here since we introduced warning groups)
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Comment 18•5 years ago
|
||
It could happen that 2 warning group messages could be added successively, before
the navigation message was emitted.
In the reducer, the second message would be seen the same as the first one, and
we'd try to increment the repeat count for the first one.
Unfortunately, the code was expecting a warning group to be created, and there
was an exception thrown as we couldn't retrieve it.
This is fixed by not allowing warning groups to be repeated.
A mocha test is added instead of a mochitest, as the issue would have been tricky
to trigger properly.
Comment 19•5 years ago
|
||
Comment 20•5 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 21•5 years ago
|
||
Comment on attachment 9218227 [details]
Bug 1705697 - [devtools] Warning group messages shouldn't be repeatable. r=bomsy.
Beta/Release Uplift Approval Request
- User impact if declined: The WebConsole can end up in a broken state, not showing any messages that are emitted from the page, which could be very confusing for the user
- 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): the patch is a one line fix, where we change the "configuration" of a given type of message so it can't be "repeated" in the console UI
- String changes made/needed:
Comment 22•5 years ago
|
||
Comment on attachment 9218227 [details]
Bug 1705697 - [devtools] Warning group messages shouldn't be repeatable. r=bomsy.
Low risk one liner with tests, approved for 89 beta 9, thanks.
Comment 23•5 years ago
|
||
| bugherder uplift | ||
Description
•