This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21673 - <area> says it can be used "Where phrasing content is expected, but only if there is a map element ancestor", but there doesn't seem to actually be a normative requirement to that effect?
Summary: <area> says it can be used "Where phrasing content is expected, but only if t...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-11 23:09 UTC by contributor
Modified: 2013-04-13 17:18 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2013-04-11 23:09:45 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#the-area-element
Complete: http://www.whatwg.org/c#the-area-element

Comment:
<area> says it can be used "Where phrasing content is expected, but only if
there is a map element ancestor", but there doesn't seem to actually be a
normative requirement to that effect?

Posted from: 216.239.45.75
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.12 Safari/537.36
Comment 1 contributor 2013-04-13 17:18:09 UTC 
Checked in as WHATWG revision r7829.
Check-in comment: I couldn't find a normative statement requiring that <area> only be inside <map>.
http://html5.org/tools/web-apps-tracker?from=7828&to=7829