W3C home > Mailing lists > Public > public-html@w3.org > July 2009

Re: Image maps: <a coords=""> - a new look

From: Leif Halvard Silli <lhs@malform.no>
Date: Thu, 16 Jul 2009 05:42:20 +0200
Message-ID: <4A5EA19C.3070303@malform.no>
To: Henri Sivonen <hsivonen@iki.fi>
CC: HTMLWG <public-html@w3.org>, scampa.giovanni@gmail.com
Leif Halvard Silli On 09-07-16 05.02:

> If we allow <area> as child of <a coords="">,
>       <map id="foo">
>          <a coords="..." href="..."><area coords="..." href="..."> ...</a>
>       </map>
> then we have a solution which  is
>     - Firefox compatible.
>     - easier to communicate
>     - in line with the HTML 5 pattern to allow <a> around  almost any 
> element
>     - a logical solution to the @alt attribute problem:   when <area> is 
> kept inside <a coords="">,  then one should be permitted to drop the 
> @alt attribute.
>     - a transition construct towards the goal that _all_ UAs support <a 
> coords=""> - any UA that understand <a coords=""> should ignore the 
> nested <area> element (as both Opera and Firefox do).
>     - "a better design because it has automatic full fallback" - without 
> the use of @alt attribute. [6]


Validator.nu already allows <area> as child of <a>. Is that an 
oversight w.r.t. what the draft says? Quote:

	"The a element may be wrapped around entire paragraphs, lists, 
tables, and so forth, even entire sections, so long as there is no 
interactive content within (e.g. buttons or other links). "

This seems to forbid <area> as child of <a>.

Having said that, the interactive /spot/ that the <area> points 
to, is located /outside/ the <a> element. Therefore it is not 
illogical, on the contrary. But the draft doesn't seem to allow 
it, yet.
leif halvard silli
Received on Thursday, 16 July 2009 03:43:02 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:48 UTC