Closed
Bug 194286
Opened 23 years ago
Closed 23 years ago
Usemap broken with XHTML 1.0 Strict compliant map tag
Categories
(Core :: XML, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 109445
People
(Reporter: matt.kerr, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
See the URL, it is rendering it all as one big link to nowhere. Similar to the
other bug reported about what happens when usemap is mistyped. This page passes
W3C's validator as XHTML 1.0 Strict. I viewed the page in Internet Explorer 6.0
SP1 and it renders fine in that.
Reproducible: Always
Steps to Reproduce:
1. Load the page's URL
2.
3.
Actual Results:
image is linked to nowhere for all of the image map coordinates
Expected Results:
two boxes, one on the left with a smaller rectangle linked to ex3.html and
another one towards the center with a link to ex1.html, within the coordinates
of the image map
| Reporter | ||
Comment 1•23 years ago
|
||
Sorry, I went dyslexic; expected results should read ex1 on the left and ex2 on
the right as per the html source file.
Comment 2•23 years ago
|
||
The page is being served as text/html, and thus is being treated as HTML (not
XHTML). If you validate the page as HTML though (using the extended validator
interface at http://validator.w3.org/detailed.html), you will see that it is
invalid in this context.
Most importantly, you need <map name="map1"> for the image map to work. Also
give the compatibility guidelines another read:
http://www.w3.org/TR/xhtml1/#guidelines
The "one big link to nowhere" effect is kind of weird though (covered by bug 90576).
Marking as a duplicate of bug 109445
*** This bug has been marked as a duplicate of 109445 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Component: Layout → XML
QA Contact: ian → petersen
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•