Closed
Bug 71162
Opened 24 years ago
Closed 23 years ago
An IMG whose src is changed reverts back to the original src when the mouse is over an area associated with the image via a map.
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
WORKSFORME
mozilla1.0.1
People
(Reporter: martin.honnen, Assigned: joki)
Details
Attachments
(4 files)
I have an IMG element whose src is changed onmouseover. This IMG is associated
with a client side MAP element and when the mouse goes over one of the AREAs the
IMG element reverts to the original source with Mozilla 0.8 while NN4 and IE4+
do that fine.
| Reporter | ||
Comment 1•24 years ago
|
||
| Reporter | ||
Comment 2•24 years ago
|
||
| Reporter | ||
Comment 3•24 years ago
|
||
Comment 4•24 years ago
|
||
Comment 5•24 years ago
|
||
I would guess the issue is that the image gets a mouseout event when we hover
over the area. Could be related to :hover not being hierarchical (bug 5693).
| Reporter | ||
Comment 6•24 years ago
|
||
Boris is right that the IMG gets an mouseout when the mouse moves over the AREA.
I checked with IE and that behaviour is the same, however the mouseover of the
AREA bubbles up to the A HREF element and that way the image is not swapped.
So Mozilla would need to bubble AREA events up to the associated IMG element to
prevent the problem from occuring.
I don't think that MAPs and AREAs belong into the A HREF element as the
workaround solves it. And that is not feasable when you directly use
<IMG ONMOUSEOVER
Comment 7•24 years ago
|
||
What happens if you use the same map in two images?
Comment 8•24 years ago
|
||
Talked to joki about this one and he agreed to take this bug.
Assignee: jst → joki
Trying to decide how important this is, since Joki is swamped. Does this break
some critical (or a large number of) web sites? If not, then we'd like to fix
it later. Marking for Moz 1.0 but not for nsbeta1
Comment 10•24 years ago
|
||
There are quite a few people who might get confused at this incorrect behavior
because most sites use image maps for their main entryway interface. If this
doesn't get fixed in time, I'd advise that it gets release noted.
Comment 11•24 years ago
|
||
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1
(you can query for this string to delete spam or retrieve the list of bugs I've
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Comment 12•23 years ago
|
||
WFM WinXP 2002122608. Reopen if you are still seeing this, but area has gotten
a number of fixes so I suspect it's gone.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•