82204 - "My Sidebar" and "Tabs" text look grayed out on Win Classic

Status: RESOLVED WORKSFORME

(SeaMonkey :: Sidebar, defect)

Description

[scalkins]

Saw this all platforms:
Win32 2001-05-22-06trunk
Linux 2001-05-22-08trunk
Mac 2001-05-22-09trunk

1)Launch browser in New Modern or Classic
2)Look at text for following items in sidebar:
"My Sidebar" text
"Tabs"  text to right of My Sidebar

Actual results:
New Modern - 'My Sidebar' text looks "inactive" (gray), and "Tabs" looks active
as you'd expect it to look.

Classic - Both the 'Tabs' and 'My Sidebar' text look gray and inactive, when in
fact the sidebar and Tabs option are both accessible.

Though the My Sidebar text may be following the scheme of color used by the text
in the title bar on the browser, "Tabs" should not look gray because users will
think it's not acceissible and may miss using this feature because of the
"inactive text" look it has.
Nominating nsbeta1 for high visibility and confusing UI.

Comment 1

[Doron Rosenberg (IBM)]

For modern3, i would suggest making the text not black but perhaps white

Comment 2

[Doron Rosenberg (IBM)]

Attachment: patch

Comment 3

[Doron Rosenberg (IBM)]

ok, i changes it to use black, white did not look correct. Same thing for
classic. However, mac classic seems to not have any color attribute for
.sidebarheader-main. Should i define them in sidebar.css?

cc: hewitt/andreww, who take care of the skins 

Comment 4

[Viswanath Ramachandran]

Paul - can your team take this and triage it. 

Comment 5

[marlon bishop]

that area, as well as much of the sidebar, is still not fully resolved for
Modern. "My Sidebar" text isn't necessarily supposed to be "active" per se,
since it's just a static title.  the "tabs" button however should look active,
and we will definitely address this soon, but probably not until after 0.9.1.  Paul?

Comment 6

[hangas]

Marking 0.9.2 and sending to Marlon.  Marlon will be working out many issues
with the sidebar that will land in 0.9.2.  We decided not to spend time trying
to land partial fixes to the sidebar for 0.9.1 only to redo some of that for 0.9.2.

Comment 7

[Todd Pringle]

themes triage: moving to 0.9.3

Comment 8

[Blake Ross]

Missed 0.9.3.

Comment 9

[marlon bishop]

This is not a problem on Mac classic, nor Modern, which is why i was confused
initially.  Is it only a problem on Win Classic (linux?) ? I would rather
someone who is responsible for Win Classic take this bug over.  But there isn't
anything wrong with the color we have now.

Comment 10

[scalkins]

This problem now only occurs on Win and Linux Classic theme
Win32 2001-10-10-05  0.9.4 Branch
Linux 2001-10-10-04 0.9.4 Branch

Setting keywords pp, classic and all platforms

Mac OSx looked fine when I checked today
MacOSX 2001-10-10-04 0.9.4 Branch

Comment 11

[sujay]

cc: pmac

Comment 12

[Patty Mac]

Mac OS 9.2 works fine except windows 98 and Linux redhat 6.2
(branch build: 2001-10-10-03-0.9.4)

Comment 13

[marlon bishop]

sending to Gail - she owns the design for classic. 

Comment 14

[Ying-Lin Xia]

*** Bug 158411 has been marked as a duplicate of this bug. ***

Comment 15

[gail]

Attachment: before and after

I think this can be resolved by changing the text color to black and the base
color to #999999.

Comment 16

[timeless]

i'm sorry, but that contrast is *bad*.

We could change the arrow and x to use the same color as the sidebar/tabs text,
that'd be an improvement.

or we could redesign the sidebar to have less useless space, i'll see if i can
make a mockup for that

Comment 17

[Tracy Walker [:tracy]]

In Classic theme mousing over the Tabs button makes the text "Tabs" disappear. 
This seems to be because the mouseover color is the same color (or very nearly)
as the Tabs text.  Comments here suggest making Sidebar and Tabs text black.
Would that also solve this mouseover issue?

Comment 18

[Robert Kaiser]

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

Comment 19

[Robert Kaiser]

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

Comment 20

[Robert Kaiser]

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

Comment 21

[Robert Kaiser]

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

Comment 22

[Robert Kaiser]

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

Comment 23

[Robert Kaiser]

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

Comment 24

[Robert Kaiser]

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

Comment 25

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 26

[Karsten Düsterloh]

WFM SM 2.8a1 WinXP and Linux trunk.