- From: <bugzilla@jessica.w3.org>
- Date: Sat, 22 Jan 2011 04:18:52 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10518 Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #12 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-01-22 04:18:52 UTC --- (In reply to comment #10) Thank you for adding the example. It is quite close to what I had in mind. But for one detail: the spec text uses the phrase "to ease maintenance". However, to really ease maintainance, I would have wrapped each anchor element around each corresponding <area> element, as this would make se even clearer what belongs together. Since the <area> element is not considered interactive in HTML5. there should be no problem in doing so, no? I am, in particular, interested in avoding to have to repeat the text of the anchor element inside the area element - that's a further simplification of the maintainance. <map name=map ><!--no alt here--> <a href="link"><area href=link coords="0,0,10,10" shape=rect >Lorem ipsum</a> </map> In HTML4, this was in theory not an issue: the <map> could contain both <area> and <a> but UAs would ignore the one or the other. Consider, text based web browsers: they treat an image map as an interactive list of links. We should avoid that they get a double set of of links. >From HTML4, section "13.6 Image maps" ]] When a MAP element contains mixed content (both AREA elements and block-level content), user agents must ignore the AREA elements. Authors should specify an image maps's geometry completely with AREA elements, or completely with A elements, or completely with both if content is mixed. Authors may wish to mix content so that older user agents will handle map geometries specified by AREA elements and new user agents will take advantage of richer block content. [[ -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Saturday, 22 January 2011 04:18:54 UTC