Closed
Bug 414503
Opened 16 years ago
Closed 16 years ago
[proto] no hover state for tab close button
Categories
(Firefox :: Theme, defect)
Tracking
()
VERIFIED
FIXED
Firefox 3
People
(Reporter: asa, Unassigned)
References
Details
there's no hover state for the tab close button.
Updated•16 years ago
|
Hardware: PC → All
Version: unspecified → Trunk
Updated•16 years ago
|
Component: OS Integration → Theme
Target Milestone: --- → Firefox 3
Updated•16 years ago
|
QA Contact: os.integration → theme
Reporter | ||
Updated•16 years ago
|
Flags: blocking-firefox3?
Comment 1•16 years ago
|
||
Not too different from platform-native convention, so not going to block. To be clear, I agree with this report and some sort of hover indication would, IMO, make the control both easier and nicer to use. If Kevin and Stephen can get to it in time, that'd be great.
Flags: wanted-firefox3+
Flags: blocking-firefox3?
Flags: blocking-firefox3-
Comment 2•16 years ago
|
||
Shouldn't be very hard. Probably could use one on the tab scrolling buttons as well. I will try and get this into the next update.
Reporter | ||
Comment 3•16 years ago
|
||
looks great in proto .17. will verify after this hits the builds.
Comment 4•16 years ago
|
||
fixed by checkin of Proto 0.17 changes - bug 430202
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 5•16 years ago
|
||
Verified with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9pre) Gecko/2008042400 Minefield/3.0pre
Status: RESOLVED → VERIFIED
Updated•16 years ago
|
Flags: in-litmus?
Updated•15 years ago
|
Flags: in-litmus? → in-litmus-
Comment 6•15 years ago
|
||
A manual test should not be necessary but having an automated test would be the best solution. Is there already one in the testsuite?
Flags: in-testsuite?
Comment 7•15 years ago
|
||
No, we don't want an automated test for this.
Flags: in-testsuite? → in-testsuite-
You need to log in
before you can comment on or make changes to this bug.
Description
•