Closed
Bug 426734
Opened 17 years ago
Closed 17 years ago
Menu bar items hover colour
Categories
(Firefox :: Menus, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: igitur, Unassigned)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
This seems to be new in FF3b5.
According to my Windows XP theme, when I hover on menu bar items, the text should display in white with a dark blue background.
Firefox displays the white text, but ignores the blue background, thus displaying an ugly white text on a grey background. Not very readable.
I'll attach screenshots.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
| Reporter | ||
Comment 1•17 years ago
|
||
| Reporter | ||
Comment 2•17 years ago
|
||
Comment 3•17 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008040300 Minefield/3.0pre
I can't reproduce this; the default theme displays the correct background color on hover. You could try out the following trouble-shooting options:
- Firefox's safe-mode to exclude extension/theme problems
- a new profile
- a reinstall in a new empty folder
http://kb.mozillazine.org/Safe_Mode_(Firefox)
http://kb.mozillazine.org/Profile_Folder
| Reporter | ||
Comment 4•17 years ago
|
||
I admit I'm running custom theme with a patched uxtheme.dll
This is the theme:
http://themes.belchfire.net/index.php?automodule=downloads&showfile=5051
In the meantime, I'll try your suggestions.
| Reporter | ||
Comment 5•17 years ago
|
||
Ok, problem disappeared in safe mode.
I think this might be some Stylish stylesheets that are messing with the colours. Anyway, I'll sort it out.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 6•17 years ago
|
||
It was indeed due to this Stylish stylesheet: Toolbars - Buttons Closer for Firefox 2.0
Disabled it, and now it works fine - thanks.
You need to log in
before you can comment on or make changes to this bug.
Description
•