- From: <bugzilla@jessica.w3.org>
- Date: Sun, 30 Oct 2011 20:57:19 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14601 Summary: Investigate if support for <a> inside image maps should be brought back to HTML Product: HTML WG Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: Olli.Pettay@gmail.com QAContact: public-html-bugzilla@w3.org CC: bzbarsky@mit.edu, mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org, Ms2ger@gmail.com http://www.whatwg.org/specs/web-apps/current-work/#the-map-element has an example where <map> contains both <a> and <area> elements. That would become significantly simpler if image maps could handle anchor elements similarly (perhaps not exactly the same way) as in HTML4. I was actually writing a gecko patch to remove support for <a> in image maps, but had all the time the feeling that I'm removing something useful and decided to not to remove the support after all - at least not right now. The difference to HTML4 could be that area/a element handling could be simplified. All the area and a elements underneath map could be taken account. Or something like that. Whatever is most backward compatible (I don't feel really strong about this issue, but seems like the issue wasn't ever discussed properly.) -- 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 Sunday, 30 October 2011 20:57:21 UTC