Added a preference called extensions.firebug.console.groupLogMessages for this purpose. Will be in Firebug 1.12.1.
Sebastian On Monday, August 26, 2013 9:46:57 PM UTC+2, Andrea Giorgetta wrote: > > I don't think anyone has created the issue yet (at least I couldn't find > it), so I did: > #6703<http://code.google.com/p/fbug/issues/detail?id=6703&thanks=6703&ts=1377546175> > > Sorry if my English is not very good or if the issue is repeated. > > Thanks. > Best regards. > Andrea. > > > > On Thursday, August 22, 2013 9:30:57 AM UTC-3, Jan Honza Odvarko wrote: >> >> > I gain what I had before! Firebug is unique. The best. >> > If it goes around copying other tools we're in real trouble! >> Absolutely agree. >> >> Btw. don't forget to cross post the bug number here (as soon as it >> exists), thanks. >> >> Honza >> >> On Thursday, August 22, 2013 11:10:27 AM UTC+2, pd wrote: >>> >>> I gain what I had before! Firebug is unique. The best. If it goes around >>> copying other tools we're in real trouble! >>> >>> If i wanted to switch to another dev tool, I'd engage with the >>> rewriting-the-wheel project that is the Firefox DevTools. Planet Mozilla >>> contains a new article every month mentioning how Mozilla has employed yet >>> another handful of dev tools people who seemingly *do not* work on >>> Firebug! Hell, if Mozilla ever gave Firebug even a one month's worth of new >>> appointees, it'd be incredible what could be achieved! Regardless, I'm >>> sticking with Firebug when it performs (see the 5 second delay post). >>> >>> I think I explained the benefit pretty well though: A new line is lot >>> more obvious to me than a smail incremented integer character all the way >>> across the other side of the screen on a 24 inch setup! There may be a few >>> options to improve the situation: >>> >>> - Move the counter to a left 'column' of the console tab. >>> - Pulse the background of the repeated error to make it more obvious >>> that the error has re-occured >>> >>> Frankly though, I'd really appreciate at least an about:config toggle >>> option to disable the 'feature'. That way you don't have to put any more >>> work into creating a maintaining an toggle option in the Firebug UI at >>> least. >>> >>> On Friday, August 16, 2013 9:14:56 AM UTC+10, Sebastian Zartner wrote: >>>> >>>> I often use Firebug maximized on a second screen that is quite wide. I >>>>> look at the left side of the console tab for output I am expecting and >>>>> nothing appears! It actually took me quite a while to realise it was a >>>>> 'feature' not a bug and that the incrementing glass circle was on the RHS! >>>>> >>>> Sounds like you're using our beta releases of Firebug 1.12 but don't >>>> read about the new features it has. :-) >>>> >>>> Other dev tools do the same and the reason for this is simply to avoid >>>> cluttering the console with equal messages. So my question is, what do you >>>> gain by disabling the message grouping? Why do you want to see all logged >>>> messages even when they are the same? >>>> >>>> Sebastian >>>> >>> > > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/f7b0d0ba-fe6b-47a6-af48-2d6268d1ceab%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
