This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
+++ This bug was initially created as a clone of Bug #25501 +++ Some elements, such as AREA[1] are described as having an 'empty' content model. However, the section (3.2.4.1) which discusses the types of content models does not include 'empty' as one of the types. In fact, AREA is described under 'Flow' content, as are other elements which are void. It would be good if, under 3.2.4.1, there was a description of what the 'empty' content model is and what, if any, relationship this has with being a void element. 1 - http://www.w3.org/TR/html5/embedded-content-0.html#the-area-element
The spec says "Inter-element whitespace, comment nodes, and processing instruction nodes must be ignored when establishing whether an element's contents match the element's content model or not" so a definition of "empty" that reminds the above exception might actually be good to have.
Every time the word "empty" appears, it is next to the words "Content model", which are a link to a part of the spec that is within a dozen paragraphs of the one that talks about intra-element whitespace and comments and so on. Are we sure this would actually help anyone? The text in comment 0 seems to illustrate a rather more fundamental misunderstanding, confusing content models and categories, and suggesting that the material under "Element definitions" hasn't been read at all. It's not clear to me that an additional link would be helpful in that scenario.
It might not have helped the original reporter, but at least I think it is confusing whether empty means really-empty or if inter-element whitespace/comments/PIs are allowed.
Are there any cases where it means really-empty?
I made this clearer. Should be in the spec next time I regen it.