If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

when mouseover event is supposed to be finished, it doesn't terminate

RESOLVED WORKSFORME

Status

Toolkit Graveyard
Error Console
RESOLVED WORKSFORME
12 years ago
a year ago

People

(Reporter: Dale Becker, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

on a button with a mouseover event when you move the mouse over it changes like
normal, but when you move it to another button and that button executes its
mouseover event, the previous button doesn't terminate it's mouseover event.  It
works fine in Internet Explorer so it is not a problem with the html code.

Reproducible: Always

Steps to Reproduce:
1.Move mouse over the news button then wait for it to change on the mouseover event
2.Move the mouse downward so that it goes over the products, resources, and
contact buttons
3.

Actual Results:  
The News, products, reasources, and contact button all stay on the mouseover image.

Expected Results:  
When moving from the news to products button, the news button should return to
it's mouseout image instead of the mouseover image.

Comment 1

12 years ago
WFM - Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050803
Firefox/1.0+

Comment 2

12 years ago
I am seeing this in the Firefox 1.0.x releases but it won't get fixed on that
branch as it is not a security or crash.

In other words this will be taken care of by the next major Firefox release
which is 1.5.
WFM with current trunk build. Marking WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

9 years ago
Product: Firefox → Toolkit
(Assignee)

Updated

a year ago
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.