Closed
Bug 317346
Opened 19 years ago
Closed 19 years ago
entire image is clickable despite using <area> tags.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 109445
People
(Reporter: grabies, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12) Gecko/20050919 Firefox/1.0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12) Gecko/20050919 Firefox/1.0.7 Despite use of <area> tags entire image shows as a link, and the <area> links doesn't link to nowhere. code: <img src="img/ffs_final.jpg" width="1024" height="711" usemap="#map1" border=0 id="baggrund" alt="Baggrundsbillede - Silkelagener"> <map id="map1" name="Mail og countdown-links"> <area href="mailto:kontakt@forfuckssake.dk" shape="rect" coords="768,669,928,689" alt="Kontakt ForFucksSake"> <area href="#" onclick="PopUp('countdown.php');" shape="poly" coords="913,522,942,507,959,522,954,539,996,567,1000,604,980,637,955,646,917,637,898,607,901,566,923,548,913,538" alt="Nedtælling til launch"> </map> end of code note: i'm certain it's not the javascript that is causing trouble, as the it works perfectly on text-links. Reproducible: Always Expected Results: The e-mail field (bottom) and the watch (bottom right) should link to 2 different subpages, respectively. The background image shouldn't link to anywhere.
Comment 1•19 years ago
|
||
Works for me, using Mozilla1.7 and with current trunk build.
Comment 2•19 years ago
|
||
WFM on Firefox 1.5rc3 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5). Reporter, can you give any more details into this issue?
Product: Mozilla Application Suite → Firefox
(In reply to comment #2) > WFM on Firefox 1.5rc3 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) > Gecko/20051111 Firefox/1.5). > > Reporter, can you give any more details into this issue? > First, I looked into the code and changed the html-code from: <map id="map1" name="Mail og countdown-links"> to: <map name="map1"> which then makes it work in Mozilla/Firefox (1.0.7), and which is the reason it worked when you stopped by the page. Wasnt thinking clearly when i updated page, sorry for that. Both solutions gets verified by the w3c validator, and works in other browsers that I have tested.
Comment 4•19 years ago
|
||
I think this is a duplicate of bug 109445, not?
Comment 5•19 years ago
|
||
Yep, dupe. *** This bug has been marked as a duplicate of 109445 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•