Closed Bug 183541 Opened 22 years ago Closed 22 years ago

Unable to follow href link specified in <area> tag

Categories

(Core :: Layout: Images, Video, and HTML Frames, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1882

People

(Reporter: ngrier, Assigned: pavlov)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 In the page http://apps.dot.state.nc.us/tims/PiedmontRegion.asp there is series of shapes (via the <map> tag) defined (via the <area> tag) over the single image. Clicking within the area should result in following the link (opening up the county-specific page). Instead, mozilla does nothing. Reproducible: Always Steps to Reproduce: 1. Open the above web page. 2. Click on one of the counties (i.e. pieces of the image). Actual Results: Mozilla does nothing. Expected Results: Should have followed the link to the page specified by the href label in the <area> tag. Bug occurred in 1.1, 1.2b and 1.2.1 on Win2k/WinXP. IE performs correctly. I'm not familiar enough with the html spec to know if this is instead an issue of malformed html. The source is: [SNIP...] <map NAME="PiedmontRegion"> [SNIP...] <area SHAPE="POLY" COORDS="209,78,208,47,211,47,210,13,128,10,127,37,131,42,130,76,209,78" HREF="RoadsByCounty.asp?County=STOKES" ALT="STOKES"> [SNIP...] </map> <img src="Graphics/PiedmontRegion.gif" usemap="PiedmontRegion.asp#PiedmontRegion" border="0" WIDTH="600" HEIGHT="507"> [SNIP...]
The usemap lists a full URI instead of just a fragment identifier; removing the filename from it makes it work fine. *** This bug has been marked as a duplicate of 1882 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Summary: Unable to follow href link specified in <area> tag
fixing breakage
Summary: Unable to follow href link specified in <area> tag
Product: Core → Core Graveyard
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.