Sidebar "Tabs" button hover color hard to read on Classic with Windows XP using Luna

NEW
Unassigned

Status

--
minor
17 years ago
10 years ago

People

(Reporter: timeless, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
winxp 2600 xp theme
moz Gecko/2002042808 classic theme

show sidebar, hover over tabs

compare hovering over tabs w/ hovering over mozilla (grouped) in taskbar.

actual: unreadable grey over light grey
expected: white on light blue
(Reporter)

Comment 1

17 years ago
Created attachment 81417 [details]
ie on left, moz on right

Comment 2

16 years ago
Updated summary to better describe. Now, for a more detailed summary of ths bug.
Here's how to reproduce:

1) You must be using Windows XP (or Server 2003) with a visual style (such as
Windows XP default [blue]).

2) Mozilla must be set on the Classic theme.

3) Open the sidebar.

4) Hover over the "Tabs" button. Notice that the hover color is hard to read
because it remains white while the background is a light tan/gray/off-white
similar to a Windows XP-style button. (The screenshot captures this well.)

The color should match that of the button text in Windows XP, or at least be
darker so it's easier to see. (The original report said it should match the
taskbar item colors; however, taskbar buttons are not related.)

As for the bug . . .

This problem is caused by the rule in sidebar.css in
skin\classic\communicator\sidebar.

One line (actually, I mean several) reads:

#sidebar-panel-picker {
  color: inherit;
  /** bugzilla 89144 - must be able to access tabs dropdown **/
  -moz-user-focus:normal !important;
}

There is no line that covers #sidebar-panel-picker:hover, though, so the color
remains on hover (and pressing, or :active). On XP, this problem can be solved
by adding something like this below the above rule:

#sidebar-panel-picker:hover {
  color: ButtonText;
}

However, then this messes things up when using the Windows Classic (no visual
style--or any earlier Windows version besides XP or Server 2003) in that now the
text turns *black* on hover, which is very had to read on the dark gray-ish color.

So the current behavior is right on Windows Classic but hard to read on Windows
XP Luna. And fixing it for Luna appears to break it on Windows Classic, unless
someone can come up with a better CSS value instead of ButtonText--or change
things so that it always works.
Severity: normal → minor
Summary: Siderbar tabs button hover (mo classic; xp xp) should match taskbar hover color → Sidebar "Tabs" button hover color had to read on Classic with Windows XP using Luna
(Reporter)

Updated

15 years ago
Summary: Sidebar "Tabs" button hover color had to read on Classic with Windows XP using Luna → Sidebar "Tabs" button hover color hard to read on Classic with Windows XP using Luna
(Assignee)

Updated

11 years ago
Product: Core → SeaMonkey
Assignee: shliang → nobody
QA Contact: pmac → themes

Comment 3

10 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Updated

10 years ago
Duplicate of this bug: 401421

Comment 5

10 years ago
Ughh, have confirmed the newer Bug, correct this now. There are two Screenshots added in Bug 401421, might be helpful to take a look there.
Status: UNCONFIRMED → NEW
You need to log in before you can comment on or make changes to this bug.