Border receives onmouseover event of body has margin set

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
16 years ago
15 years ago

People

(Reporter: joshs, Assigned: saari)

Tracking

Trunk
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126

This is a weird one. It seems that in some cases, if an <a> has a mouseover
event and a border-bottom, and the cursor goes over the text and then the
border, the event will fire once for the text and again for the border. If the
cursor goes over the text and then over the body, this doesn't happen.

Reproducible: Always

Steps to Reproduce:
1. Go to http://josh.cc/jsbug.html. View the source and you'll see a function
that just counts how many times it's been called.
2. Roll your mouse over the text, and then off to the right (not over the
border). The status bar will say "1", indicating the function fired once.
3. Reload.
4. Roll your mouse over the text, and then slowly down over the border, and then
over the body. The status bar will say "2".

Now if you want to get really into it, download the file and remove the margin
attribute from the body CSS element. Then the problem goes away. It seems that
if any margin is there, then it breaks, but if there isn't, it's okay.
(Reporter)

Comment 1

16 years ago
Created attachment 113776 [details]
Test case for the bug

Just in case it gets deleted from the server.
(Reporter)

Comment 2

16 years ago
Actually, looking at it further, removing the body margin fixes it in this test
case, but doesn't in others. It may be unrelated.
The JS engine knows nothing about mice or events.
Assignee: rogerl → saari
Component: JavaScript Engine → DOM Events
QA Contact: pschwartau → desale

Comment 4

15 years ago
WORKSFORME with Mozilla 1.7b 2004032208 XP Pro.
I also created another testcase (with addEventListener) and all results were
expected.
Reporter, can you try again your testcase with a recent build? Is the problem
still there?
(Reporter)

Comment 5

15 years ago
Seems to work fine in Firefox 0.8, so I imagine it's fixed.

Comment 6

15 years ago
I'm RESOLVING this as WORKSFORME then
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.