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 12349 - Should mention that anywhere that expects flow content implicitly also expects phrasing content, and so forth for embedded content.
Summary: Should mention that anywhere that expects flow content implicitly also expect...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 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-03-21 02:29 UTC by contributor
Modified: 2011-08-04 05:03 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-03-21 02:29:42 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#flow-content-0

Comment:
Should mention that anywhere that expects flow content implicitly also expects
phrasing content, and so forth for embedded content.

Posted from: 76.102.14.57 by ian@hixie.ch
User agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 Safari/534.16
Comment 1 Ian 'Hixie' Hickson 2011-05-07 18:09:14 UTC 
This doesn't seem necessary actually since all the phrasing elements actually _are_ flow elements.
Comment 2 Michael[tm] Smith 2011-08-04 05:03:56 UTC 
mass-moved component to LC1