Bug 14638
Summary: | Image maps unusable when using XHTML 1.1 | ||
---|---|---|---|
Product: | WebKit | Reporter: | Adam Read <aread> |
Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | ap, mrowe, seth |
Priority: | P2 | ||
Version: | 523.x (Safari 3) | ||
Hardware: | Mac | ||
OS: | OS X 10.4 |
Adam Read
Image maps are not usable when writing valid XHTML 1.1. In the img usemap attribute, the id of the map needs to be prefixed with a '#' if the image-map is to be useable. For valid XHTML, the '#' shouldn't be there.
e.g.
Valid XHTML:
<map id="foo" ...>
...
<img usemap="foo" ...>
Invalid, but working XHTML:
<map id="foo" ...>
...
<img usemap="#foo" ...>
I've posted examples at:
http://phcrack.ca/webkit_bug/valid.xhtml
http://phcrack.ca/webkit_bug/invalid.xhtml
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Adam Read
(In reply to comment #0)
Didn't know the comments weren't html.
The XHTML is obviously:
Valid XHTML:
<map id="foo" ...>
...
<img usemap="foo" ...>
Invalid, but working XHTML:
<map id="foo" ...>
...
<img usemap="#foo" ...>
Alexey Proskuryakov
We do not aim to fully implement XHTML 1.1 where it disagrees with XHTML 1.0 and HTML. In this particular case, XHTML 5 draft says that "the usemap attribute, if specified, must be a valid hashed ID reference to a map element" - so we treat this as an bug in the XHTML 1.1 spec.
Please note that Firefox 3 betas also no longer support non-hashed idrefs in usemap, so the map in <http://phcrack.ca/webkit_bug/valid.xhtml> doesn't work anymore.
Ian 'Hixie' Hickson
Actually this bug isn't just WONTFIX, it's INVALID. The XHTML working group has agreed several times to change usemap from IDREF to be compatible with HTML4, but they just haven't done it yet. For a history describing this issue, see this blog entry:
http://ln.hixie.ch/?start=1172653243&count=1
David Kilzer (:ddkilzer)
Reopening to change status per Comment #3.
Mark Rowe (bdash)
*** Bug 15323 has been marked as a duplicate of this bug. ***