1627287 - Console messages always group, option is ignored

Status: UNCONFIRMED

(DevTools :: Console, defect, P3)

Description

[Yves Goergen [:ygoe]]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0

Steps to reproduce:

1. Deselect the F12 tools setting "group similar messages".
2. Execute console.log() with the same message multiple times.

Actual results:

The message appears only once, with a counter next to it.

Expected results:

The message should appear as often as it's triggered, each with its own timestamp.

This should have worked before, so somebody probably broke it recently.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:nchevobbe, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 3

[Nicolas Chevobbe [:nchevobbe]]

Thanks Yves!
The setting only drives what we call "warning groups", which so far group warning messages about tracking protection and same site cookie warning messages. I see how that can be confusing and that one could think it should have an effect on the "repeat" mechanism.

Harald, we had a few report like that where people expect the "Group similar message" to impact the "repeat" mechanism.
Do you think we should do it? or rename the setting?

Comment 4

[:Harald Kirschner :digitarald]

Alternatively, would it make sense to cover both groupings under the same UI setting? Assuming the user intent here is be to see the ungrouped raw output; this would be fulfilled.

Comment 5

[Nicolas Chevobbe [:nchevobbe]]

yes that's what I meant. Having the setting set to false would disable the repeat mechanism

Comment 6

[:Harald Kirschner :digitarald]

Sorry, I misread then. Sounds like we are on the same page then.

Comment 7

[Firefox Bug Husbandry Bot]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)