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 14014 - area elements in map elements should be handled as if they were embedded content for the purpose of this requirement.
Summary: area elements in map elements should be handled as if they were embedded cont...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-03 08:17 UTC by contributor
Modified: 2011-10-19 22:25 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2011-09-03 08:17:13 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html
Multipage: http://www.whatwg.org/C#phrasing-content
Complete: http://www.whatwg.org/c#phrasing-content

Comment:
area elements in map elements should be handled as if they were embedded
content for the purpose of this requirement.

Posted from: 113.197.157.202
User agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Comment 1 Ian 'Hixie' Hickson 2011-09-04 20:52:27 UTC 
Which requirement?
Comment 2 Ian 'Hixie' Hickson 2011-09-04 20:59:06 UTC 
Assuming you mean the "paragraphs have to contain text" requirement, can you elaborate on why?
Comment 3 Ian 'Hixie' Hickson 2011-10-19 22:25:41 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: see comment 1 and comment 2