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 10266 - "contexts in which this element may be used:" should read "where flow content or phrasing content is expected"
Summary: "contexts in which this element may be used:" should read "where flow content...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (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: 2010-07-29 21:22 UTC by contributor
Modified: 2010-10-04 14:45 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-07-29 21:22:30 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-a-element

Comment:
"contexts in which this element may be used:" should read "where flow content
or phrasing content is expected"

Posted from: 222.147.252.201 by w3.org@boblet.net
Comment 1 Oli Studholme 2010-07-29 22:02:21 UTC 
alternatively if thats not correct, this text should explain the a element can also be used in elements whose content model is flow content
Comment 2 Ian 'Hixie' Hickson 2010-09-09 22:50:26 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: Partially Accepted
Change Description: see diff given below
Rationale: This is intentional, but I've tried to clarify it. I've also fixed some other problems I ran into around this.