352001 - Hard to tell which category is active in the Error Console

Status: RESOLVED DUPLICATE of bug 254002

(Firefox :: General, defect)

Description

[Marek Stępień [:marcoos, inactive]]

The icons from the new time are almost the same for the active and inactive state, making it almost impossible to know which category (All, Errors, Warnings, Messages) is currently chosen.

If we're not going to change the icons, the solution may be to make each button look "pressed" when the category is selected (like in SeaMonkey/Modern).

Comment 1

[Marek Stępień [:marcoos, inactive]]

Attachment: Screenshot showing the problem

screenshot from the latest Firefox tinderbox build with SeaMonkey for comparison.

Comment 2

[Marek Stępień [:marcoos, inactive]]

This happens on Linux. It's OK on Windows Vista.

Updating the OS field accordingly.

Comment 3

[Marek Stępień [:marcoos, inactive]]

As there apparently is no implementation of a permanently pressed button in the Gtk version (compare "This is another toolbar" here: http://www.hevanet.com/acorbin/xul/top.xul between Win and Gtk), there is no elegant solution for this, that could get in for 2.0.

The possible solutions for 2.0 would be:

1) better differentiation of the icons (maybe destaurate the inactive ones?)

2) add some craptastic CSS to console.css - for Linux only, like this:

toolbar#ToolbarMode toolbarbutton[checked="true"] {
    -moz-appearance: none !important;
    outline: 1px solid inset !important;
}

3) make tabs out of these 4 buttons 

Comment 4

[Marek Stępień [:marcoos, inactive]]

Attachment: Screenshot of the proposed solution #2

Solution #2 looks like this.

Kinda crappy, but at least you know what you're viewing there.

Comment 5

[Marek Stępień [:marcoos, inactive]]

The best solution would be to fix bug 254002 which already has a patch for <toolbarbutton type="radio" /> with GTK.

Comment 6

[Marek Stępień [:marcoos, inactive]]

After giving it some thought, this bug is in fact a dupe of 254002, resolving as such, sorry for the bugspam. :)


*** This bug has been marked as a duplicate of 254002 ***