Closed Bug 578968 Opened 14 years ago Closed 14 years ago

Hover-state of buttons at the end of the tabstrip isn't cleared when moving mouse up to the window buttons with the new default layout

Categories

(Firefox :: Toolbars and Customization, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- -

People

(Reporter: pretzer, Unassigned)

References

Details

(Keywords: polish)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:2.0b1) Gecko/20100630 Firefox/4.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:2.0b1) Gecko/20100630 Firefox/4.0b1

When hovering with the mouse over the 'All tabs'-button the hover state isn't cleared when moving the mouse up to the window close button.

Reproducible: Always

Steps to Reproduce:
1. Hover over the 'All tabs'-button with your mouse (the button shows as hovered)
2. Move the mouse up to the window close button
Actual Results:  
The 'All tabs'-button still shows as hovered.

Expected Results:  
The 'All tabs'-button should not show as hovered.
menubar must be disabled (firefox-button instead) and tabs must be on-top.
blocking2.0: --- → ?
Blocks: 513162
Can someone with Win7 please confirm?
Keywords: qawanted
Would take a fix, I bet it's small.
blocking2.0: ? → -
This issue also applies to the TabCandy-button, which was added there recently by default.
In fact it applies to any button that's placed in the area at the end of the tabstrip.
Summary: 'All tabs'-button hover state isn't cleared when moving mouse up to the window close button → Hover-state of buttons at the end of the tabstrip isn't cleared when moving mouse up to the window buttons with the new default layout
now this seems to have been partly fixed in the latest nightly. when moving the mouse slowly upwards the issue doesn't occur anymore. however if you move the mouse quickly this still happens.
WFM, win7, bet5pre. Has this been fixed?
Attached image Screenshot of the issue
This is not fixed in todays nightly (beta 6 pre). Window has to be maximized and you have to move the mouse rather quickly.
This is a screenshot showing the issue (the cursor is missing, because it's automatically removed when taking a screenshot).
confirmed, you have to snap the cursor up quickly, only reproducible in maximized windows. Not a functionality issue though, marking as polish.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: qawantedpolish
This is probably a dupe of bug 613781, which has blocking.
(In reply to comment #9)
> This is probably a dupe of bug 613781, which has blocking.

confirmed. the landing of bug 613781 has fixed the issue.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: