or . Why do we also need a body?
the namespace declaration mechanism, and an element cannot actually have
an xmlns attribute in the null namespace specified.
- 3.6. Document metadata
+ 3.7. Document metadata
Document metadata is represented by metadata
elements in the document's head
element.
-
3.6.1. The 3.7.1. The head element
-
- Contexts in which this element may be used:
@@ -6124,62 +6527,22 @@ class="main"> or . Why do we also need a body?
- Element-specific attributes:
-
profile
+ - None.
+
+
- Predefined classes that apply to this element:
+
+
- None.
- DOM interface:
-
-
-
interface HTMLHeadElement : HTMLElement {
- attribute DOMString profile;
-};
+ - No difference from
HTMLElement.
The head element collects the
document's metadata.
-
The profile
- attribute must, if specified, contain a list of zero or more URIs (or
- IRIs) representing definitions of classes, metadata names, and link
- relations. These URIs are opaque strings, like namespaces; user agents are
- not expected to determine any useful information from the resources that
- they reference.
-
-
profile should use a microsyntax
-
-
Each time a class, metadata, or link relationship name that is not
- defined by this specification is found in a document, the UA must check
- whether any of the URIs in the profile attribute are known (to the UA) to
- define that name. The class, metadata, or link relationship shall then be
- interpreted using the semantics given by the first URI that is known to
- define the name. If the name is not defined by this specification and none
- of the specified URIs defines the name either, then the class, metadata,
- or link relationship is meaningless and the UA must not assign special
- meaning to that name.
-
-
If two profiles define the same name, then the semantic is given by the
- first URI specified in the profile attribute. There is no way to use the
- names from both profiles in one document.
-
-
User agents must ignore all the URIs given in the profile attribute
- that follow a URI that the UA does not recognise. (Otherwise, if a name is
- defined in two profiles, UAs would assign meanings to the document
- differently based on which profiles they supported.)
-
-
If a profile's definition introduces new definitions over
- time, documents that use multiple profiles can change defined meaning over
- time. So as to avoid this problem, authors are encouraged to avoid using
- multiple profiles.
-
-
The profile
- DOM attribute must reflect the profile content
- attribute on getting and setting.
-
-
3.6.2. The 3.7.2. The title element
Metadata element.
@@ -6198,6 +6561,10 @@ class="main"> or
. Why do we also need a body?
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
or . Why do we also need a body?
agents should use the document's title when referring to the document in
their user interface.
- 3.6.3. The 3.7.3. The base element
Metadata element.
@@ -6263,6 +6630,10 @@ class="main"> or
. Why do we also need a body?
href
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
-
@@ -6301,7 +6672,7 @@ class="main"> or . Why do we also need a body?
in XML documents. Authors should instead use
the
xml:base attribute. [XMLBASE]
- 3.6.4. The 3.7.4. The link element
Metadata element.
@@ -6331,6 +6702,10 @@ class="main"> or
. Why do we also need a body?
href="#title3">title attribute has special semantics on this
element.
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
-
@@ -6549,7 +6924,7 @@ class="main"> or . Why do we also need a body?
return false and must do nothing on setting.
-
3.6.5. The 3.7.5. The meta element
Metadata element.
@@ -6572,6 +6947,10 @@ class="main"> or
. Why do we also need a body?
content
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
-
@@ -6594,18 +6973,6 @@ class="main"> or . Why do we also need a body?
id=content0 title=attr-meta-content>
content attribute
on the same element gives the value.
- To set metadata with meta elements,
- authors must first specify a profile that defines metadata names, using
- the profile
- attribute. The value of the name attribute must be defined by one of the
- profiles, and the value of the content attribute must conform to the syntax
- given by the profile.
-
-
How user agents handle metadata set in this way depends on the
- definitions of the profiles involved.
-
If a meta element has no name attribute, it does
not set document metadata. If a meta
@@ -6613,13 +6980,109 @@ class="main"> or
. Why do we also need a body?
href="#content0">content attribute, then the value part of the
metadata name/value pair is the empty string.
+ The value must not be a URI. Links must be represented using the
+ link element, not the meta element.
+
The DOM attributes name and content must reflect the respective content attributes of the same
name.
-
3.6.5.1. Specifying and
+ 3.7.5.1. Standard metadata names
+
+
This specification defines a few names for the name attribute of the
+ meta element.
+
+
+ - generator
+
+
- The value must be a free-form string that identifies the software used
+ to generate the document. This value must not be used on hand-authored
+ pages.
+
+
+ 3.7.5.2. Other metadata names
+
+ Extensions to the
+ predefined set of metadata names may be registered in the WHATWG Wiki
+ MetaExtensions page.
+
+
Anyone is free to edit the WHATWG Wiki MetaExtensions page at any time
+ to add a type. These new names must be specified with the following
+ information:
+
+
+ - Keyword
+
+
-
+
The actual name being defined. The name should not be confusingly
+ similar to any other defined name (e.g. differing only in case).
+
+
- Brief description
+
+
-
+
A short description of what the metadata name's meaning is, including
+ the format the value is required to be in.
+
+
- Link to more details
+
+
- A link to a more detailed description of the metadata name's semantics
+ and requirements. It could be another page on the Wiki, or a link to an
+ external page.
+
+
- Synonyms
+
+
-
+
A list of other names that have exactly the same processing
+ requirements. Authors should not use the names defined to be synonyms,
+ they are only intended to allow user agents to support legacy content.
+
+
- Status
+
+
-
+
One of the following:
+
+
+ - Proposal
+
+
- The name has not received wide peer review and approval. Someone has
+ proposed it and is using it.
+
+
- Accepted
+
+
- The name has received wide peer review and approval. It has a
+ specification that unambiguously defines how to handle pages that use
+ the name, including when they use it in incorrect ways.
+
+
- Unendorsed
+
+
- The metadata name has received wide peer review and it has been
+ found wanting. Existing pages are using this keyword, but new pages
+ should avoid it. The "brief description" and "link to more details"
+ entries will give details of what authors should use instead, if
+ anything.
+
+
+ If a metadata name is added with the "proposal" status and found to be
+ redundant with existing values, it should be removed and listed as a
+ synonym for the existing value.
+
+
+ Conformance checkers must use the information given on the WHATWG Wiki
+ MetaExtensions page to establish if a value not explicitly defined in this
+ specification is allowed or not. When an author uses a new type not
+ defined by either this specification or the Wiki page, conformance
+ checkers should offer to add the value to the Wiki, with the details
+ described above, with the "proposal" status.
+
+
This specification does not define how new values will get approved. It
+ is expected that the Wiki will have a community that addresses this.
+
+
3.7.5.3. Specifying and
establishing the document's character encoding
The meta element may also be used, in
@@ -6654,7 +7117,7 @@ class="main"> or
. Why do we also need a body?
- 3.6.6. The 3.7.6. The style element
Metadata element.
@@ -6679,6 +7142,10 @@ class="main"> or
. Why do we also need a body?
href="#title4">title attribute has special semantics on this
element.
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
-
@@ -6771,7 +7238,7 @@ class="main"> or . Why do we also need a body?
defined for the alternate style sheets
DOM.
-
3.7. Sections
+ 3.8. Sections
Sectioning elements are elements that divide
the page into, for lack of a better word, sections. This section describes
@@ -6787,7 +7254,7 @@ class="main"> or
. Why do we also need a body?
The processing of headings and sections is
defined in the processing models section of this specification.
-
3.7.1. The 3.8.1. The body element
Sectioning
@@ -6807,6 +7274,10 @@ class="main"> or . Why do we also need a body?
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
or . Why do we also need a body?
element in the DOM, as per the definition of the term, and not any
arbitrary body element.
- 3.7.2. The 3.8.2. The section element
Sectioning or . Why do we also need a body?
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
or . Why do we also need a body?
has a heading. See the section on headings and
sections for further details.
- 3.7.3. The 3.8.3. The nav element
Sectioning or . Why do we also need a body?
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
or . Why do we also need a body?
heading. See the section on headings and sections
for further details.
- 3.7.4. The 3.8.4. The article element
Sectioning or . Why do we also need a body?
XXX attributes to give the date authored, date published
-->
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
headings and
sections for further details.
- 3.7.5. The 3.8.5. The blockquote element
Sectioning cite
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
-
@@ -7031,7 +7518,7 @@ XXX attributes to give the date authored, date published
href="#blockquote0">blockquote
elements, but with the dialog element.
- 3.7.6. The 3.8.6. The aside element
Sectioning None.
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
headings and sections
for further details.
- 3.7.7. The 3.8.7. The h1, h2, h3, h4, h5, and h6
@@ -7095,6 +7586,10 @@ XXX attributes to give the date authored, date published
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
These elements must not be empty.
- 3.7.8. The 3.8.8. The header element
Block-level
@@ -7141,6 +7636,10 @@ XXX attributes to give the date authored, date published
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
header element is the same as for an h1 element (the highest rank).
- 3.7.9. The 3.8.9. The footer element
Block-level
@@ -7243,6 +7742,10 @@ XXX attributes to give the date authored, date published
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
address element.
- 3.7.10. The 3.8.10. The address element
Block-level
@@ -7292,6 +7795,10 @@ XXX attributes to give the date authored, date published
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
aside element, does not apply to its
ancestor elements, e.g. the page's body.
- 3.8. Prose
+ 3.9. Prose
- 3.8.1. The 3.9.1. The p element
Block-level
@@ -7368,6 +7875,10 @@ XXX attributes to give the date authored, date published
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
</section>
- 3.8.2. The 3.9.2. The hr element
Block-level
@@ -7457,6 +7968,10 @@ To move the error from the markup to the rhyming.</p>
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
in a story, or a transition to another topic within a section of a
reference book.
- 3.8.3. The 3.9.3. The dialog element
Block-level
@@ -7488,6 +8003,10 @@ To move the error from the markup to the rhyming.</p>
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
href="#blockquote0">blockquote elements for other ways to cite
or quote.
- 3.9. Preformatted text
+ 3.10. Preformatted text
- 3.9.1. The 3.10.1. The pre element
Block-level
@@ -7562,6 +8081,10 @@ To move the error from the markup to the rhyming.</p>
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
a block of computer output.
- 3.10. Lists
+ 3.11. Lists
- 3.10.1. The 3.11.1. The ol element
Block-level
@@ -7626,6 +8149,10 @@ To move the error from the markup to the rhyming.</p>
start
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
-
@@ -7672,7 +8199,7 @@ To move the error from the markup to the rhyming.</p>
-
3.10.2. The 3.11.2. The ul element
Block-level
@@ -7695,6 +8222,10 @@ To move the error from the markup to the rhyming.</p>
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
The items of the list are the li element
child nodes of the ul element.
-
3.10.3. The 3.11.3. The li element
-
- Contexts in which this element may be used:
@@ -7743,6 +8273,10 @@ To move the error from the markup to the rhyming.</p>
- If the element is not the child of an
ol element: None.
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
-
@@ -7810,7 +8344,7 @@ To move the error from the markup to the rhyming.</p>
attribute must reflect the value of the
value content attribute.
- 3.10.4. The 3.11.4. The dl element
Block-level
@@ -7835,6 +8369,10 @@ To move the error from the markup to the rhyming.</p>
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
speaker/line pair comes after the next). For an example of how to mark up
dialogue, see the dialog element.
- 3.10.5. The 3.11.5. The dt element
-
- Contexts in which this element may be used:
@@ -7937,6 +8474,10 @@ To move the error from the markup to the rhyming.</p>
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
that its contents are a term being defined, but this can be indicated
using the dfn element.
- 3.10.6. The 3.11.6. The dd element
-
- Contexts in which this element may be used:
@@ -7984,6 +8524,10 @@ To move the error from the markup to the rhyming.</p>
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
title="inline-level content">inline content or block-level elements.
- 3.11. Phrase elements
+ 3.12. Phrase elements
- 3.11.1. The 3.12.1. The a element
Interactive,
ping
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
-
@@ -8125,7 +8673,7 @@ To move the error from the markup to the rhyming.</p>
href="#reflect">reflect
the respective content attributes of the same
name.
-
3.11.2. The 3.12.2. The q element
Strictly inline-level content.
@@ -8148,6 +8696,10 @@ To move the error from the markup to the rhyming.</p>
cite
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- The
q element uses the
users to follow such citation links.
- 3.11.3. The 3.12.3. The cite element
Strictly inline-level content.
@@ -8185,6 +8737,10 @@ To move the error from the markup to the rhyming.</p>
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
...").
-->
- 3.11.4. The 3.12.4. The em element
Strictly inline-level content.
@@ -8244,6 +8800,10 @@ citations ("my favourite book is ...").
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
...").
-->
- 3.11.5. The 3.12.5. The strong element
Strictly inline-level content.
@@ -8327,6 +8887,10 @@ citations ("my favourite book is ...").
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
will destroy anything within
ten meters.</strong></strong> You have been warned.</p>
- 3.11.6. The 3.12.6. The small element
Strictly inline-level content.
@@ -8379,6 +8943,10 @@ ten meters.</strong></strong> You have been warned.</p>
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
<p><strong><small>Continued use of this service will result in a kiss.</small></strong></p>
- 3.11.7. The 3.12.7. The m element
Strictly inline-level content.
@@ -8443,6 +9011,10 @@ merger with Demo Group.</p>
- None.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
</pre>
these days. They're really cute. I think they like my garden!</p>
- 3.11.8. The 3.12.8. The dfn element
Strictly inline-level content.
@@ -8495,6 +9067,10 @@ these days. They're really cute. I think they like my garden!</p>
href="#title5">title
attribute has special semantics on this
element.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
attributes being bad, etc -->
- 3.11.9. The 3.12.9. The abbr element
Strictly inline-level content.
@@ -8599,6 +9175,10 @@ and so Hammond ordered the iris to be opened.</p>
href="#title6">title
attribute has special semantics on this
element.
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
<p>Jack used a <abbr>Zat</abbr> to make the boxes of evidence disappear.</p>
- 3.11.10. The 3.12.10. The t element
Strictly inline-level content.
@@ -8663,6 +9243,10 @@ Applications over the World Wide Web.</p>
href="#title0">title
attribute has special semantics on this
element when used with the dfn element.
+
- Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
- No difference from
...").
-->
- 3.11.11. The 3.12.11. The time element
Strictly inline-level content.
@@ -8716,6 +9300,10 @@ citations ("my favourite book is ...").
datetime
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
-
@@ -8846,7 +9434,7 @@ citations ("my favourite book is ...").
for marking event dates in hCalendar markup. Thus the DOM APIs are likely
to be used as ways to generate interactive calendar widgets or some such.
-
3.11.12. The 3.12.12. The meter element
Strictly inline-level content.
@@ -8875,6 +9463,10 @@ citations ("my favourite book is ...").
optimum
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
-
@@ -9175,7 +9767,7 @@ should we also look inside the title="" attribute?
should we make the contents accessible in some way, e.g. as a tooltip?
-->
-
3.11.13. The 3.12.13. The progress element
Strictly inline-level content.
@@ -9196,6 +9788,10 @@ should we make the contents accessible in some way, e.g. as a tooltip?
max
+ - Predefined classes that apply to this element:
+
+
- None.
+
- DOM interface:
-
@@ -9360,7 +9956,7 @@ should we make the contents accessible in some way, e.g. as a tooltip?
attribute must return -1. Otherwise, it must return the result of dividing
the current value by the maximum value.
-
3.11.14. The 3.12.14. The code element
Strictly inline-level content.
@@ -9409,7 +10005,7 @@ begin
end.</code></pre>
- 3.11.15. The 3.12.15. The var element
Strictly inline-level content.
@@ -9450,7 +10046,7 @@ cream factory then I expect at <em>least</em> <var>n</var>
flavours of ice cream to be available for purchase!</p>
- 3.11.16. The 3.12.16. The samp element
Strictly inline-level content.
@@ -9506,7 +10102,7 @@ Linux demo 2.6.10-grsec+gg3+e+fhs6b+nfs+gr0501+++p3+c4a+gr2b-reslog-v6.189 #1 SM
<samp class="prompt">jdoe@demo:~$</samp> <samp class="cursor">_</samp></samp></pre>
- 3.11.17. The 3.12.17. The kbd element
Strictly inline-level content.
@@ -9567,7 +10163,7 @@ Linux demo 2.6.10-grsec+gg3+e+fhs6b+nfs+gr0501+++p3+c4a+gr2b-reslog-v6.189 #1 SM
</p>
- 3.11.18. The 3.12.18. The sup and sub
elements
@@ -9639,7 +10235,7 @@ For example, the 10th point has coordinate
f(<var>x</var>, <var>n</var>) = log<sub>4</sub><var>x</var><sup><var>n</var></sup>
- 3.11.19. The 3.12.19. The span element
Strictly inline-level content.
@@ -9681,7 +10277,7 @@ For example, the 10th point has coordinate
href="#dfn0">dfn?
- 3.11.20. The 3.12.20. The bdo element
Strictly inline-level content.
@@ -9737,7 +10333,7 @@ For example, the 10th point has coordinate
[CSS21]
- 3.11.21. The 3.12.21. The br element
Strictly inline-level content.
@@ -9804,12 +10400,12 @@ Address: <input name="address"></p>
-
3.12. Edits
+ 3.13. Edits
The ins and del elements represent edits to the document.
-
3.12.1. The 3.13.1. The ins element
Block-level
@@ -9912,7 +10508,7 @@ Address: <input name="address"></p>
</aside>
- 3.12.2. The 3.13.2. The del element
- 3.12.3. Attributes common to
+ 3.13.3. Attributes common to
ins and del elements
@@ -10021,13 +10617,13 @@ Address: <input name="address"></p>
id=datetime2 title=dom-mod-datetime>datetime DOM
attributes must reflect the elements' content attributes of the same name.
- 3.13. Embedded content
+ 3.14. Embedded content
- 3.13.1. The 3.14.1. The img element
-
Strictly inline-level embedded
- content.
+
Strictly
+ inline-level embedded content.
- Contexts in which this element may be used:
@@ -10210,11 +10806,11 @@ Address: <input name="address"></p>
title=attr-img-src>src attribute, and it is a
valid image.
-
3.13.2. The 3.14.2. The iframe element
- Strictly inline-level embedded
- content.
+
Strictly
+ inline-level embedded content.
- Contexts in which this element may be used:
@@ -10301,11 +10897,11 @@ Address: <input name="address"></p>
title=dom-iframe-src>
src must reflect the content attribute of the same name.
- 3.13.3. The 3.14.3. The embed element
- Strictly inline-level embedded
- content.
+
Strictly
+ inline-level embedded content.
- Contexts in which this element may be used:
@@ -10439,11 +11035,11 @@ Address: <input name="address"></p>
rendered, and is being rendered to a visual medium, or 0 otherwise. [CSS21]
-
3.13.4. The 3.14.4. The object element
- Strictly inline-level embedded
- content.
+
Strictly
+ inline-level embedded content.
- Contexts in which this element may be used:
@@ -10712,7 +11308,7 @@ Address: <input name="address"></p>
href="#reflect">reflect the respective content attributes of the same
name.
-
3.13.5. The 3.14.5. The param element
@@ -10769,17 +11365,17 @@ Address: <input name="address"></p>
href="#reflect">reflect the respective content attributes of the same
name.
- 3.13.6. The 3.14.6. The canvas element [TBW]
- Strictly inline-level embedded
- content.
+
Strictly
+ inline-level embedded content.
This section will eventually contain the definition of
canvas (though not the APIs).
-
3.13.7. The 3.14.7. The map element
Block-level
@@ -10833,7 +11429,7 @@ Address: <input name="address"></p>
rooted at the map element, whose filter
matches only area elements.
- 3.13.8. The 3.14.8. The area element
@@ -10932,7 +11528,7 @@ Address: <input name="address"></p>
href="#reflect">reflect the respective content attributes of the same
name.
-
3.13.9. The 3.14.9. The figure element
Block-level
@@ -11007,9 +11603,9 @@ Address: <input name="address"></p>
fallback content.
- 3.14. Tabular data
+ 3.15. Tabular data
- 3.14.1. The 3.15.1. The table element
Block-level
@@ -11246,7 +11842,7 @@ Address: <input name="address"></p>
href="#rows">rows collection, the method must instead raise an
INDEX_SIZE_ERR exception.
-
3.14.2. The 3.15.2. The caption element
@@ -11280,7 +11876,7 @@ Address: <input name="address"></p>
The caption element takes part in
the table model.
-
3.14.3. The 3.15.3. The colgroup element
@@ -11337,7 +11933,7 @@ Address: <input name="address"></p>
same name, with the exception that on setting, if the new value is 0, then
an INDEX_SIZE_ERR exception must be raised.
- 3.14.4. The 3.15.4. The col element
@@ -11390,7 +11986,7 @@ Address: <input name="address"></p>
same name, with the exception that on setting, if the new value is 0, then
an INDEX_SIZE_ERR exception must be raised.
- 3.14.5. The 3.15.5. The tbody element
@@ -11474,7 +12070,7 @@ Address: <input name="address"></p>
href="#rows0">rows collection, the method must instead raise an
INDEX_SIZE_ERR exception.
- 3.14.6. The 3.15.6. The thead element
@@ -11515,7 +12111,7 @@ Address: <input name="address"></p>
The thead element takes part in the
table model.
-
3.14.7. The 3.15.7. The tfoot element
@@ -11565,7 +12161,7 @@ Address: <input name="address"></p>
The tfoot element takes part in the
table model.
-
3.14.8. The 3.15.8. The tr element
@@ -11678,7 +12274,7 @@ Address: <input name="address"></p>
href="#cells">cells collection, the method must instead raise
an INDEX_SIZE_ERR exception.
- 3.14.9. The 3.15.9. The td element
@@ -11748,7 +12344,7 @@ Address: <input name="address"></p>
title=dom-tr-cells>cells collection. If there
is no such parent element, then the attribute must return 0.
- 3.14.10. The 3.15.10. The th element
@@ -11822,7 +12418,7 @@ Address: <input name="address"></p>
therefore also has the DOM attributes defined above in the td section.
- 3.14.11. Processing model
+ 3.15.11. Processing model
The various table elements and their content attributes together define
the table model.
@@ -11925,7 +12521,7 @@ Address: <input name="address"></p>
represented by table elements and their
descendants. Documents must not have table model errors.
-
3.14.11.1. Forming a table
+ 3.15.11.1. Forming a table
To determine which elements correspond to which slots in a table associated with a
title=concept-cell>cell anchored to them, then this is a table model error.
- 3.14.11.2. Forming relationships
+ 3.15.11.2. Forming relationships
between data cells and header cells [TBW]
The algorithm for assigning header cells to data
@@ -12426,7 +13022,7 @@ Address: <input name="address"></p>
...
- 3.15. Forms 3.16. Forms [TBW]
@@ -12438,55 +13034,55 @@ Address: <input name="address"></p>
- 3.15.1. The form
+ 3.16.1. The form
element
- 3.15.2. The
+ 3.16.2. The
fieldset element
- 3.15.3. The input
+ 3.16.3. The input
element
- 3.15.4. The button
+ 3.16.4. The button
element
- 3.15.5. The label
+ 3.16.5. The label
element
- 3.15.6. The select
+ 3.16.6. The select
element
- 3.15.7. The
+ 3.16.7. The
datalist element
- 3.15.8. The
+ 3.16.8. The
optgroup element
- 3.15.9. The option
+ 3.16.9. The option
element
- 3.15.10. The
+ 3.16.10. The
textarea element
- 3.15.11. The output
+ 3.16.11. The output
element
- 3.15.12. Processing model
+ 3.16.12. Processing model
See WF2
for now
-
3.15.12.1. Form submission
+ 3.16.12.1. Form submission
[TBW]
See WF2
for now
-
3.16. Scripting
+ 3.17. Scripting
- 3.16.1. The 3.17.1. The script element
Block-level
@@ -12809,7 +13405,7 @@ Address: <input name="address"></p>
way as the textContent DOM
attribute.
- 3.16.1.1. Script languages
+ 3.17.1.1. Script languages
The following lists some MIME types and the languages to which they
refer:
@@ -12831,12 +13427,11 @@ Address: <input name="address"></p>
agents must not ignore unknown MIME parameters — types with unknown
parameters must be assumed to be unsupported.
-
3.16.2. The 3.17.2. The noscript element
Block-level
- element, strictly inline-level content, and metadata element.
+ element
, and strictly inline-level content.
- Contexts in which this element may be used:
@@ -12956,9 +13551,9 @@ Address: <input name="address"></p>
XML the parser is not affected by such state, and thus the element would
not have the desired effect.
-
3.17. Interactive elements
+ 3.18. Interactive elements
- 3.17.1. The 3.18.1. The details element
Interactive, 3.17.2. 3.18.2. [SCS] The datagrid
element
@@ -13119,7 +13714,7 @@ https://www.google.com/base/settings
disabled content attributes respectively.
-
3.17.2.1. The 3.18.2.1. The datagrid data model
This section is non-normative.
@@ -13161,12 +13756,12 @@ https://www.google.com/base/settings
href="#datagridClassSummary">affect the functionality of the datagrid element, and are also passed to the style system. They are similar
- in concept to the class
- attribute, except that they are not specified on elements but are given by
- scripted data providers.
+ in concept to the class attribute, except that they are not
+ specified on elements but are given by scripted data providers.
- 3.17.2.2. How rows are identified
+ 3.18.2.2. How rows are identified
The chains of numbers that give a row's path, or identifier, are
represented by objects that implement the GetChildAtPosition()
methods ever
get called with the empty path.
-
3.17.2.3. The data provider
+ 3.18.2.3. The data provider
interface
The conformance criteria in this section apply to any implementation
@@ -13663,7 +14258,7 @@ interface DataGridDataProvider {
-->
- 3.17.2.4. The default data
+ 3.18.2.4. The default data
provider
The user agent must supply a default data provider for the case where
@@ -13751,7 +14346,7 @@ interface DataGridDataProvider {
href="#thead1">thead element child has no tr element child, the default data provider must
not add any classes for any of the captions. Otherwise, each class in
- the class attribute
+ the class attribute
of the ith th
element child of the first tr element
child of the first thead element
@@ -13767,7 +14362,7 @@ interface DataGridDataProvider {
href="#reversed">reversed classes.
- If the
table element has a class attribute that
+ title=attr-class>class attribute that
includes the sortable class, add the sortable class.
@@ -13970,14 +14565,14 @@ interface DataGridDataProvider {
- If the row's corresponding element contains
other elements that are also in the view, and the element's
class attribute contains
+ title=attr-class>class attribute contains
the closed class: initially-closed
- If the row's corresponding element contains
other elements that are also in the view, and the element's
class attribute contains
+ title=attr-class>class attribute contains
the open class: initially-open
@@ -14105,14 +14700,14 @@ interface DataGridDataProvider {
- If the row's element contains other elements that are also in the
view, and the element's
class attribute contains the class attribute contains the closed class: initially-closed
- If the row's element contains other elements that are also in the
view, and the element's
class attribute contains the class attribute contains the open class: initially-open
@@ -14165,7 +14760,7 @@ interface DataGridDataProvider {
datagrid.
- 3.17.2.4.1.
+ 3.18.2.4.1.
Common default data provider method definitions for cells
These definitions are used for the cell-specific methods of the default
@@ -14305,7 +14900,7 @@ interface DataGridDataProvider {
- 3.17.2.5. Populating the
+ 3.18.2.5. Populating the
datagrid element
A datagrid must be disabled until
@@ -14745,7 +15340,7 @@ interface DataGridDataProvider {
-
3.17.2.6. Updating the 3.18.2.6. Updating the datagrid
Whenever the DataGridDataProvider {
href="#inconsistentDataProvider">likely to result in inconsistent
renderings, and the user agent is likely to disable the data grid.
- 3.17.2.7. Requirements for
+ 3.18.2.7. Requirements for
interactive user agents
This section only applies to interactive user agents.
@@ -14894,7 +15489,7 @@ interface DataGridDataProvider {
provider's method was invoked.
- 3.17.2.8. The selection
+ 3.18.2.8. The selection
This section only applies to interactive user agents. For other user
agents, the
relation to the Selection
interface.
- 3.17.2.9. Columns and captions
+ 3.18.2.9. Columns and captions
This section only applies to interactive user agents.
@@ -15072,7 +15667,7 @@ XXX selection ranges -->
define drag and drop in datagrids; selectiondraggable, etc.
-->
- 3.17.3. The 3.18.3. The command element
Metadata element, and
@@ -15284,7 +15879,7 @@ XXX selection ranges -->
command elements are not
rendered unless they form part of a menu.
-
3.17.4. The 3.18.4. The menu element
Block-level
@@ -15386,11 +15981,10 @@ XXX selection ranges -->
The processing model for menus is described in the
next section.
-
3.18. Miscellaneous elements
+ 3.19. Miscellaneous elements
- 3.18.1. The 3.19.1. The legend element
-
- Contexts in which this element may be used:
@@ -16517,7 +17111,7 @@ XXX selection ranges -->
the previous document in the series is the referenced document.
- searchsearchHyperlink
@@ -16934,15 +17528,15 @@ mpt says:
will require this resource.
4.4.3.14. Link type "search"
+ id=search2 title=rel-search>search"
- The search keyword
+
The search keyword
may be used with link, a, and area
elements. For link elements, it creates
a hyperlink.
-
The search keyword
+
The search keyword
indicates that the referenced document provides an interface specifically
for searching the document and its related resources.
@@ -17120,7 +17714,7 @@ mpt says:
-->
-
4.4.3.19. Other link types
+ 4.4.3.19. Other link types
Other than the types defined above, only types defined as extensions in
the WHATWG Wiki
@@ -32105,7 +32699,6 @@ normative classes:
* applies to elements:
* processing model:
* status:
- get rid of profile=""
vlad: you should define what the UA should do with out-of-order aDATs
@@ -32276,10 +32869,6 @@ section "rendering HTML" has to cope with:
and if you find one, carry on as if that was your data="".
-XMDP or something should be at the end of profile="".
-
-
-
should have some text talking about the fact that it's ok if your page
passes through a period of non-conformance while script is running,
but that in between scripts it should be compliant.