703615 - [meta] Webconsole filters menus are confusing

Status: RESOLVED FIXED

(DevTools :: Console, defect, P3)

Description

[Sonny Piers [:sonny]]

I think there should be a discussion on making webconsole's filters menus clearer.

Here is my propositions:

Regarding the "Web Developer" menu I see two solutions:

1) Renaming it.
We talked about that on IRC and AFAIK you already agreed on "Logging" but it might be still (more?) confusing since others menus are about logging stuff too.
What about naming it something like "Console API" and menuitems's filters would become console.log/console.error/console.warn/console.info ? (simple and stupid but clear)

2) Delete it.
Removing the Web Developer menu and move/merge Web Developer's filters with JS's filters ?

I think the second solution is the best.

Regarding the dropdown menus I think we should give them the "unchecked state" only if all filters are unchecked.

Comment 1

[Sonny Piers [:sonny]]

The checked/unchecked behavior problem is likely to be fixed by bug 702342.

The Web Developer menu remains confusing.

Comment 2

[Heather Arthur [:harth]]

bug 703123 is to rename the 'Web Developer' button.

I was just about to comment in that bug about suggestion #2, another web developer suggested that also.

Putting the options under JS makes sense to me, since "console.log()" etc. are in fact called from JS.

One thing I do like about the current setup is that the logging is in grey, which reflects the notion of logging. Orange is not as "loggy" (I've always thought JS should be blue and CSS should be orange ... <.< that's just personal preference though).

Comment 3

[Rob Campbell [:rc] (:robcee)]

(In reply to Heather Arthur [:harth] from comment #2)
> bug 703123 is to rename the 'Web Developer' button.
> 
> I was just about to comment in that bug about suggestion #2, another web
> developer suggested that also.
> 
> Putting the options under JS makes sense to me, since "console.log()" etc.
> are in fact called from JS.

yeah, logically it makes sense, but...

> One thing I do like about the current setup is that the logging is in grey,
> which reflects the notion of logging. Orange is not as "loggy" (I've always
> thought JS should be blue and CSS should be orange ... <.< that's just
> personal preference though).

right. We have these nice color-schemes associated with the buttons which I think we should retain. The colors were initially chosen because "Blue" is not a warning color. It's informational. Same for light grey. Orange is a more of a warning color, hence it's chosen for JS warnings and errors.

For this reason, I don't think we should consolidate these two buttons and should consider renaming Web Developer to Logging or something else.

Comment 4

[Sonny Piers [:sonny]]

Ok I understand, I'm taking the renaming web developer menu bug. I will suggest something else later.

Comment 5

[Rob Campbell [:rc] (:robcee)]

I think we can safely close this meta bug. It's 3 years old. Since all the dependent bugs have been fixed, I'm going to mark this fixed. Reopen if this is incorrect.