Closed
Bug 137708
Opened 22 years ago
Closed 22 years ago
[modern] close tab button shouldn't hover when disabled
Categories
(SeaMonkey :: Themes, defect)
SeaMonkey
Themes
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: john.p.baker, Assigned: hewitt)
References
Details
(Keywords: useless-UI, Whiteboard: [adt3 rtm])
Attachments
(1 file, 2 obsolete files)
2.69 KB,
patch
|
hewitt
:
review+
hewitt
:
superreview+
|
Details | Diff | Splinter Review |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9+) Gecko/20020411 BuildID: 2002041111 The tabs close button shouldn't glow on hover when it is disabled (ie only have one tab open), ideally it should have a disabled image with the x greyed out Reproducible: Always Steps to Reproduce: 1. "Hide the tab bar when only one tab is open" off 2. browser window with only one tab 3. mouse over close tab button Actual Results: button glows Expected Results: button should be recognisably 'disabled'.
Comment 1•22 years ago
|
||
Reporter | ||
Comment 2•22 years ago
|
||
Trying the equivalent to attachment 80340 [details] [diff] [review] in userChrome.css works fine, so patch looks good to me.
Reporter | ||
Comment 3•22 years ago
|
||
The disabled close button is also getting some !important styles for .toolbarbutton[disabled="true"] which would appear to be the cause of bug 137057
Comment 4•22 years ago
|
||
Comment on attachment 80340 [details] [diff] [review] patch Does that need !important? Many other [disabled="true"] styles seem to.
Comment 5•22 years ago
|
||
*** Bug 133685 has been marked as a duplicate of this bug. ***
Comment 6•22 years ago
|
||
*** Bug 145406 has been marked as a duplicate of this bug. ***
Comment 7•22 years ago
|
||
nominating. this is an incredible usability problem -- a button that looks and acts like it should do something but does nothing. The !important is needed, because otherwise the :hover:active rule will have higher weight than the rule you are introducing. Which is bad -- it'll look disabled till you click on it.
Comment 8•22 years ago
|
||
Instead of disabling it, it should either: 1. Clear the current page and load start page/empty page. 2. Or close the window completely. The logic is: you have a group of tabs open, you want to close all of them one by one, so you keep hitting the close tab button but on the last tab it doesn't close! Which is why it should do one of the above. Just trying to get my point in Bug 145406 across.
Comment 9•22 years ago
|
||
Attachment #80340 -
Attachment is obsolete: true
Reporter | ||
Comment 10•22 years ago
|
||
Can we not correct the padding margin border problem (bug 137057) at the same time? .tabs-closebutton[disabled="true"] { margin: 0px 4px !important; padding: 4px 2px !important; border: none !important; list-style-image: url("chrome://global/skin/icons/close-dis.gif") !important; }
Assignee | ||
Comment 11•22 years ago
|
||
The right way to fix this is to cut out interference from the toolbarbutton styles, which are wrongfully setting the border width and style for the hover/active/disabled states, when all that changes is the color. The rest of the patch is pretty much the same as what neil did with a tweak to the padding.
Attachment #84240 -
Attachment is obsolete: true
Assignee | ||
Updated•22 years ago
|
Status: NEW → ASSIGNED
Comment 13•22 years ago
|
||
Comment on attachment 84677 [details] [diff] [review] patch r=sgehani
Attachment #84677 -
Flags: review+
Assignee | ||
Comment 14•22 years ago
|
||
Comment on attachment 84677 [details] [diff] [review] patch sr=jag
Attachment #84677 -
Flags: review+ → superreview+
Assignee | ||
Updated•22 years ago
|
Attachment #84677 -
Flags: review+
Comment 15•22 years ago
|
||
Removing adt1.0.0, as this has not been nsbeta1+, nor given an ADT impact by the Nav triage team. Pls work with the Nav Triage team to get this plussed, and approved for submission to the 1.0 branch. thanks!
Keywords: adt1.0.0
Whiteboard: [Need Impact]
Comment 16•22 years ago
|
||
Nav triage team: nsbeta1+, adt3 rtm
Keywords: adt1.0.0
Whiteboard: [Need Impact] → [adt3 rtm]
Updated•22 years ago
|
Assignee | ||
Comment 17•22 years ago
|
||
fixed
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Comment 18•22 years ago
|
||
Mass removing adt1.0.0, and adding adt1.0.1 because, we are now on 1.0.1.
Keywords: adt1.0.0
Comment 20•22 years ago
|
||
Talked to Jack, this one is fixed on netscape trunk build (2002-08-07-08-TRUNK)
Status: RESOLVED → VERIFIED
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•