Hi,
All elements currently defined to be in the heading content category
(h1-h6 and header) are also included within the flow content category.
It seems that it would be easier and more consistent to state the
definition of heading content that:
All heading content is also flow content. Any content model that
expects flow content also expects heading content.
And then remove "Flow content" from category lists for those elements,
as it would be implied by "Heading content".
Additionally, to improve readability, it would be useful to add a note
to the definition of flow content that it includes all of heading
content, phrasing content and embedded content; and a similar note in
the definition of phrasing content that it includes embedded content.
Finally, it would be useful if the spec eventually included some kind of
diagram that illustrated the relationships between each of the categories.
http://www.whatwg.org/specs/web-apps/current-work/#kinds-of-content
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
