Andrés Delfino Reporter
	Description • 17 years ago

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b4pre) Gecko/2008022003 Minefield/3.0b4pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b4pre) Gecko/2008022003 Minefield/3.0b4pre

In /chrome/classic/skin/classic/global/console/console.css, the selected item background color is hard-coded to a provided image:

background-image: url("chrome://mozapps/skin/shared/itemSelected.png");

This makes the selection look like in the screen shot, which is awful.

Reproducible: Always

	Andrés Delfino Reporter
	Comment 2 • 17 years ago

Note that his is the only file which seems to use that image, so it could be deleted.

To check that, I did:

# This extracts every jar.
for i in `find . -name "*.jar"`; do unzip -d "${i%.jar}" "${i}"; done

# This greps every file for the image name.
grep -FIRi 'itemSelected.png' .

	Andrés Delfino Reporter
	Comment 3 • 17 years ago

Could someone please confirm this?

	Mike Beltzner [:beltzner, not reading bugmail]
	Comment 4 • 17 years ago

This will not block the final release of Firefox 3.

	Michael Monreal [:micmon]
	Comment 5 • 17 years ago

IIRC itemSelected was also used for the selected background for the category header icons in the preferences and addons dialogs. We removed it there and use the selection color from GTK now.

	Alex Faaborg [:faaborg] (Firefox UX)
	Comment 6 • 16 years ago

uiwanted: merge this with the other rich list view bugs (download manger, addons manager, awesome bar)  all should have the same appearance.

	Alex Faaborg [:faaborg] (Firefox UX)
	Comment 7 • 16 years ago

Duping to a central bug to get this figured out on all platforms for all rich list views.

	Andrés Delfino Reporter
	Comment 8 • 15 years ago

As per bug 426727 comment 17.

	Nochum Sossonko [:Natch]
	Comment 9 • 15 years ago

This work is being done in bug 305206, there's a patch there already for this.

	Dão Gottwald [:dao]
	Comment 10 • 15 years ago

(In reply to comment #9)
> This work is being done in bug 305206, there's a patch there already for this.

Then this bug depends on the other one.

	Brian Grinstead [:bgrins]
	Comment 11 • 8 years ago

The Error Console has been removed in favor of the Browser Console (see Bug 1278368), and the component is going to be removed.  If this bug is also relevant in the Browser Console, please reopen and move this into Firefox -> Developer Tools: Console.

	Zack Weinberg (:zwol)
	Comment 12 • 8 years ago

I am mass-reopening and re-componenting every single one of the Toolkit:Error Console bugs that appear to have been closed without anyone even *glancing* at whether they were relevant to the Browser Console.

If you want to close a whole bunch of old bugs -- FOR ANY REASON -- it is YOUR RESPONSIBILITY to check EVERY SINGLE ONE OF THEM and make sure they are no longer valid.  Do not push that work onto the bug reporters.

(It's okay to close bugs that haven't been touched in years when they don't have enough information for you to figure out whether the problem is still relevant to the current software - the reporter probably isn't coming back to clarify.  But that is the ONLY situation where it is okay.)

(I'm going to have to do this in two steps because of the way the "change several bugs at once" form works.  Apologies for the extra bugspam.)

	J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)
	Comment 13 • 8 years ago

Error console is gone now, and we want to remove XUL usage from DevTools is general, so WONTFIX here.