Support for console.group

firebug / firebug.next

Next Firebug generation built on top of native Firefox developer tools

Other

229 stars 37 forks source link

Support for console.group #354

Open EvHaus opened 9 years ago

EvHaus commented 9 years ago

Looks like Firebug 3.0.0.alpha9 is missing support for console.group and console.groupEnd. In Firebug 2 it would create a collapsed/expanded grouping item in the console, but right now it still displays every line.

fflorent commented 9 years ago

Reported DevTools-side here: https://bugzilla.mozilla.org/show_bug.cgi?id=755534

I don't know what is the best solution here :

wait for an implementation DevTools-side (or propose a patch to them)
do it Firebug-side, if in every case that's the same effort

I don't know what is the output in Firebug.next (I can't test that right know).

Florent

EvHaus commented 9 years ago

This may be the wrong place to ask this, but what is the general thinking around Firebug 3 vs. DevTools? How does the Firebug team decide which features to implement in Firebug 3 vs. which features get passed off to the Firefox DevTools team?

For example -- I think the entire aesthetic of the Console tab in Firefox DevTools is horrendous compared to Firebug 2. It's very difficult to read (due to the awful text wrapping and lack of create separators) and is lacking a lot of features. Does Firebug intend on extending/replacing this layout at all?

fflorent commented 9 years ago

This may be the wrong place to ask this, but what is the general thinking around Firebug 3 vs. DevTools? How does the Firebug team decide which features to implement in Firebug 3 vs. which features get passed off to the Firefox DevTools team?

That's the kind of questions we still are asking to ourselves.

Does Firebug intend on extending/replacing this layout at all?

Among other things, we're customizing the appearance of the DevTools to look like Firebug, yes.

Florent

janodvarko commented 9 years ago

This may be the wrong place to ask this, but what is the general thinking around Firebug 3 vs. DevTools? How does the Firebug team decide which features to implement in Firebug 3 vs. which features get passed off to the Firefox DevTools team?

We have some rules in place, roughly:

Features that are generally useful for everyone should be fixed on the platform
Features related to theme/layout (to make DevTools look like Firebug 2) belongs to Firebug3
Features related to 3rd party can be implemented in Firebug 3
Features that represents alternatives (and make DevTools closer to Firebug 2) belongs to Firebug 3
Features that can't be implemented in the platform can be considered for Firebug 3

So, console.group and console.groupEnd API should be implemented on the platform (sometimes we can impl it in FB3 if the platform ETA is tool long).

Honza