Closed
Bug 268547
Opened 20 years ago
Closed 19 years ago
HREF in image map AREA causes bad display of DIV SPAN nodevalue
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: adrian.pearce, Assigned: bugzilla)
References
()
Details
Attachments
(1 file)
|
1.54 KB,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
at www.domesday1986.com click on icon to enter main site. Then move mouse over
map at top left. The text labels move correctly but leave trailing characters
in the old locations. This problem is in Firefox but not Explorer or Netscape.
Also the problem in Firefox disappears if you F11 to fullscreen.
Reproducible: Always
Steps to Reproduce:
1.<MAP NAME="L0map">
<AREA NAME="Orkney" COORDS="0, 0,395, 49" HREF="javascript:A1();"
onMouseOver="OrkneyMouseOver();return false">
2.function OrkneyMouseOver() {
var m = document.getElementById("IMAGEFILEMAP");
if (m != null) m.src=Orkney.src;
var n = document.getElementById("LABELREGIONNAME");
if (n != null) {
n.childNodes[0].nodeValue="Orkney & Shetland";
n.style.top=25;
n.style.left=10;
}
}
3. Removing HREF="javascript:A1(); eliminates the problem
Actual Results:
The code snippets above show the problem.
HREF="javascript:A1(); causes the problem.
Full HTML code is attached.
Expected Results:
Clean display of text values.| Reporter | ||
Comment 1•20 years ago
|
||
| Reporter | ||
Comment 2•20 years ago
|
||
(In reply to comment #1) > Created an attachment (id=165259) > zip file of HTML demo with .BMP file > This bug did not appear in Netscape 7.1 but does in 7.2 (as well as Firefox)
Summary: HREF in image map AREA causes bad display of DIV SPAN nodevalue → HREF in image map AREA causes bad display of DIV SPAN nodevalue
Comment 3•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 4•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•