1048287 - Option disable collapsing repeated messages

Status: RESOLVED DUPLICATE of bug 1615206

(DevTools :: Console, enhancement, P3)

Description

[vito.detullio]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 (Beta/Release)
Build ID: 20140803004002

Steps to reproduce:

This is a "reply" to https://bugzilla.mozilla.org/show_bug.cgi?id=611795 (as the summary is similar)
I, as James Edwards, find annoying and distracting the collapsing of repeated messages, and I would like to have an option on the toolbox, or at least in the about:config, to disable this feature.

To make an example, if I open the Console, and write

    > console.log("hi"); console.log("hi"); 



Actual results:

    < undefined
      "hi"                                                                             2



Expected results:

    < undefined
      "hi"                                                                             
      "hi"

Comment 1

[V@no]

Need ability see timestamp of each entry, if we could expand the collapsed data and see the time of each individual entry, it would help in many cases.

However ability collapse/expand the log inside the window itself, and having already existing log data be instantly affected (not just for new entries), would be most useful.

This feature used to be in Console²

Comment 2

[ffuser]

The ability to disable collapsing is extremely useful in debugging java script code, that you may or may not have written but have to fix. Enable-ing timestamps does not alter this behavior.

Comment 3

[Nicolas Chevobbe [:nchevobbe]]

A setting to disable the grouping was added in Bug 1615206

(In reply to V@no from comment #1)

Need ability see timestamp of each entry, if we could expand the collapsed
data and see the time of each individual entry, it would help in many cases.

However ability collapse/expand the log inside the window itself, and having
already existing log data be instantly affected (not just for new entries),
would be most useful.

This should be covered in Bug 704252