322384 - Image maps - application/xhtml+xml - usemap value now incorrectly requires #

Status: RESOLVED DUPLICATE of bug 290422

(Firefox :: General, defect)

Description

[Michael A. Puls II]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060104 Firefox/1.6a1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060104 Firefox/1.6a1

Image maps in xml documents no longer work. The usemap attribute now requires the presence of # in the usemap value as if it was text/html. This is a regression.

Reproducible: Always

Steps to Reproduce:

Actual Results:  
The image maps do not work. The link in each image is not present. The hand cursor in the first 2 images is present over the whole image instead of just the part where the link is supposed to be. This behavior usually happens in Firefox when Firefox can't find what the usemap value references.

Comment 1

[Michael A. Puls II]

Attachment: Test case

Comment 2

[Michael A. Puls II]

Attachment: Workaround

Comment 3

[Martijn Wargers (dead)]

This behavior changed with bug 290422.
As you can see in that bug, the presence of # is/should be required.

*** This bug has been marked as a duplicate of 290422 ***

Comment 4

[Michael A. Puls II]

Thanks.

This is crazy.  First XHTML 1.1 is correct. Then XHTML 1.1 is incorrect. Then I contact W3C and they say that the usemap attribute being type IDREF is definitely not a mistake; although it will be changed back to URI in XHTML 2. 

Then, I notice that Firefox instead goes by mime type instead of doctype and I was told that was because XML handling overrules the doctype and XML mime type requires IDREF for the usemap and that it should match an id attribute. Then, I was told text/html rules require that usemap must be of type URI and match a name attribute. Those were the reasons why Firefox went by mime type and bug reports here can back those reasons.

Now, I see that XHTML 1.1 is incorrect (which is fine) and Firefox's previous mime type behavior is not being used anymore even though there was valid reasons for doing it.

Crazy, but O.K., I see the rule is now (for now at least) that usemap is of type URI in *all* situations and must contain #. If it's text/html, the UA should look for the name attribute. If it's an xml doc, the UA should look for the id attribute.

Comment 5

[Michael A. Puls II]

For information purposes, here are some of the references, which brought about the filing of this bug:

http://lists.w3.org/Archives/Public/www-validator/2004Dec/0096.html
http://lists.w3.org/Archives/Public/www-validator/2004Dec/0106.html
http://hades.mn.aptest.com/cgi-bin/voyager-issues/Modularization-abstractions?id=8502
http://hades.mn.aptest.com/cgi-bin/voyager-issues/Modularization-abstractions?id=8502#followups
https://bugzilla.mozilla.org/show_bug.cgi?id=203315#c4
http://hades.mn.aptest.com/cgi-bin/voyager-issues/XHTML-1.1-text?id=650;expression=usemap;user=guest#followups
http://lxr.mozilla.org/mozilla1.7/source/content/shared/src/nsImageMapUtils.cpp#82