W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2007

[whatwg] <map id="">

From: Shadow2531 <shadow2531@gmail.com>
Date: Sat, 6 Jan 2007 19:47:14 -0500
Message-ID: <6b9c91b20701061647y7496258cyc73e82da837edce2@mail.gmail.com>
On 1/6/07, Anne van Kesteren <annevk at opera.com> wrote:
> I think that besides supporting <map name=""> it should also support <map
> id=""> to be referenced from usemap (not with an IDREF, but with an URI,
> mind you). This is compatible with what Opera does in both HTML and XHTML,
> Firefox in XHTML and Internet Explorer in HTML.
>
> See http://simon.html5.org/test/html/image-maps/ for some demos/testcases
>  from Simon Pieters on the subject.

As said:

In Opera, regardless of mime type, Opera can match usemap="#test" to
<map id="test">, <map name="test"> or <map name="test" id="test">.
Whether Opera uses the map element with the name or the map element
with the id depends on which one comes first in the document.

IE does the same.

For FF Minefield, it strictly only matches an id in
application/xhtml+xml and strictly only matches a name attribute in
text/html.

Allowing *both* id and name to match (in text/html at least ) per IE's
rules would be great for compatibility.

As for application/xhtml+xml and the name attribute, I don't have much
of an opinion.

Having to use name in text/html and id in application/xhtml+xml or
both if you're serving the page as text/html to some and
application/xhtml+xml to others means an extra tweak that could be
solved by allowing id to match in text/html.

Just being able to use id regardless of the mime type would be the way
to go and name can be left for just for text/html for compatibility if
we don't want to allow it for application/xhtml+xml too like Opera
does.

Now that the idref issue has been sorted out, we need to sort this
stuff out too.

-- 
burnout426
Received on Saturday, 6 January 2007 16:47:14 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:31 UTC