This bug affects both the emerged firefox (last several versions) and the binary downloaded version from mozilla.org. About Firefox says: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040914 Firefox/0.10 Mouse over one of the tool bar menus and pull down, then use the mouse to highlight individual menu items. The highlighted menu items get displayed with white-on-white text, making them unreadable. Non-highlighted menu items look fine. Note that other Gtk apps don't seem to suffer this problem. Specifically Evolution, gnome-terminal, Mozilla all seem fine. Even the emerged thunderbird seems fine. Reproducible: Always Steps to Reproduce: 1. 2. 3.
You have a theme issue. Use default themes and you won't have the problem.
I'm pretty sure I am using the default themes. I certainly haven't knowingly changed any Firefox theme, and I'm using the default Gnome theme, as near as I can tell.
Try this for me... I think it will force Gtk+ to the default theme, so we can make sure. 1. exit firefox 2. :> ~/empty_file 3. env GTK_RC_FILES=$HOME/empty_file firefox
I tried this and I still get white-on-white menu items. The favicons show up fine though.
Created attachment 45281 [details] Fragment of a "userChrome.css" file This problem pertains to both Thunderbird and Firefox. Here is a fix for the problem: Add the contents of the attached file to "userChrome.css" in the chrome directory for the application. I don't know enough about the situation to say whether this is a desirable permanent fix, or whether this should just be a temporary solution until a real solution is found.
There's a small typo in the userChrome.css file you posted (menubutoon -> menubutton). But the fix does seem to work for me, although I only tested it with Firefox.
I'd just like to add this I get this when I use the GTK+ theme 'Simple' and the default FireFox theme. Using any other GTK+ theme or any other Firefox theme cures the problem.
I have the same problem, the userChrome.css fixes it for me as well. this seems to be a GTK issue, doesn't it?
Stale bug, reopen if this still an issue with up-to-date FF versions.