| 7
- | xxx-large
+ | ''xxx-large''
| see below
@@ -670,7 +668,7 @@ path: includes/cldr.include
ul[type=square i], li[type=square i] { list-style-type: square; }
- In the above stylesheet, the attribute selectors for the
+ In the above stylesheet, the attribute selectors for the
ol and <{li}> elements are expected to be treated as
case-sensitive.
@@ -1123,7 +1121,7 @@ path: includes/cldr.include
if that does not return an error, the user agent is expected to treat the attribute as a presentational hint setting the element's 'color' property to
the resulting color.
-The fieldset and <{legend}> elements
+The <{fieldset}> and <{legend}> elements
@namespace url(http://www.w3.org/1999/xhtml);
@@ -1157,15 +1155,15 @@ path: includes/cldr.include
A <{fieldset}> element's rendered legend, if any, is expected to be
- rendered over the top border edge of the <{fieldset}> element as a ''block'' box
+ rendered over the top border edge of the <{fieldset}> element as a block box
(overriding any explicit 'display' value). In the absence of an explicit width, the box should
- shrink-wrap. If the <{legend}> element in question has an align attribute, and its value is an ASCII
- case-insensitive match for one of the strings in the first column of the following table,
- then the legend is expected to be rendered horizontally aligned over the border edge
- in the position given in the corresponding cell on the same row in the second column. If the
- attribute is absent or has a value that doesn't match any of the cases in the table, then the
- position is expected to be on the right if the 'direction' property on this element has a computed
- value of ''rtl'', and on the left otherwise.
+ shrink-wrap. If the <{legend}> element in question has an <{legend/align}> attribute, and its
+ value is an ASCII case-insensitive match for one of the strings in the first column of the
+ following table, then the <{legend}> is expected to be rendered horizontally aligned over the
+ border edge in the position given in the corresponding cell on the same row in the second
+ column. If the attribute is absent or has a value that doesn't match any of the cases in the
+ table, then the position is expected to be on the right if the 'direction' property on this
+ element has a computed value of ''rtl'', and on the left otherwise.
@@ -1458,56 +1456,60 @@ path: includes/cldr.include
is expected to render as an ''inline-block'' box rendered as a button whose contents are the
contents of the element.
- When the <{button}> element's type attribute is
+ When the <{button}> element's <{button/type}> attribute is
in the Menu state, the user agent is expected to
indicate that activating the element will display a menu, e.g., by displaying a down-pointing
triangle after the button's label.
-The <{details}> element
+The <{details}> and <{summary}> elements
+
+
+ summary {
+ display: list-item;
+ list-style: disclosure-closed;
+ }
+ details[open] > summary {
+ list-style: disclosure-open;
+ }
+
When the details binding applies to a <{details}> element, the element
- is expected to render as a ''block'' box with its 'padding-left' property set to "40px" for
- left-to-right elements (LTR-specific) and with its 'padding-right' property set to
- "40px" for right-to-left elements. The element's shadow tree is expected to take the element's
- first child <{summary}> element, if any, and place it in a first ''block'' box container,
- and then take the element's remaining descendants, if any, and place them in a second ''block'' box
- container.
-
- The first container is expected to contain at least one line box, and that line box
- is expected to contain a disclosure widget (typically a triangle), horizontally positioned within
- the left padding of the <{details}> element. That widget is expected to allow the user to request
- that the details be shown or hidden.
-
- The second container is expected to have its 'overflow' property set to ''hidden''. When the
- <{details}> element does not have an <{details/open}>
- attribute, this second container is expected to be removed from the rendering.
+ is expected to render as a block box. The element's shadow tree is expected to take the
+ element's first child <{summary}> element, if any, and place it in a first block box
+ container, and then take the element's remaining descendants, if any, and place them in a second
+ block box container.
+
+ The first container is expected to allow the user to request the details be shown or hidden.
+
+ The second container is expected to be removed from the rendering when the <{details}> element
+ does not have an <{details/open}> attribute.
The <{input}> element as a text entry widget
When the input-textfield binding applies to an <{input}> element whose
- type attribute is in the Text, Search,
+ <{input/type}> attribute is in the Text, Search,
Telephone, URL,
or E-mail state, the element is expected to render as
an ''inline-block'' box rendered as a text field.
- When the input-password binding applies to an <{input}> element whose
- type attribute is in the Password state, the element is expected to render as an
- ''inline-block'' box rendered as a text field whose contents are obscured.
+ When the input-password binding applies to an <{input}> element whose <{input/type}>
+ attribute is in the Password state, the element is expected to
+ render as an ''inline-block'' box rendered as a text field whose contents are obscured.
- If these text fields provide a text selection, then, when the user changes the current
- selection in such a binding, the user agent is expected to queue a task to fire
- a simple event that bubbles named select at the element,
- using the user interaction task source as the task source.
+ If these text fields provide a text selection, then, when the user changes the current selection
+ in such a binding, the user agent is expected to queue a task to fire a simple event
+ that bubbles named select at the element, using the
+ user interaction task source as the task source.
- If an <{input}> element whose type attribute is
- in one of the above states has a size attribute, and parsing
+ If an <{input}> element whose <{input/type}> attribute is
+ in one of the above states has a <{input/size}> attribute, and parsing
that attribute's value using the rules for parsing non-negative integers doesn't
generate an error, then the user agent is expected to use the attribute as a presentational hint for the 'width' property on the element,
with the value obtained from applying the converting a character width to pixels
algorithm to the value of the attribute.
- If an <{input}> element whose type attribute is
- in one of the above states does not have a size
+ If an <{input}> element whose <{input/type}> attribute is
+ in one of the above states does not have a <{input/size}>
attribute, then the user agent is expected to act as if it had a user-agent-level style sheet rule
setting the 'width' property on the element to the value obtained from applying the
converting a character width to pixels algorithm to the number 20.
@@ -1525,31 +1527,31 @@ path: includes/cldr.include
The <{input}> element as domain-specific widgets
When the input-datetime binding applies to an <{input}> element whose
- type attribute is in the Date and Time state, the element is expected to render as
+ <{input/type}> attribute is in the Date and Time state, the element is expected to render as
an ''inline-block'' box depicting a Date and Time control.
When the input-date binding applies to an <{input}> element whose
- type attribute is in the Date state, the element is expected to render as an
+ <{input/type}> attribute is in the Date state, the element is expected to render as an
''inline-block'' box depicting a Date control.
When the input-month binding applies to an <{input}> element whose
- type attribute is in the Month state, the element is expected to render as an
+ <{input/type}> attribute is in the Month state, the element is expected to render as an
''inline-block'' box depicting a Month control.
When the input-week binding applies to an <{input}> element whose
- type attribute is in the Week state, the element is expected to render as an
+ <{input/type}> attribute is in the Week state, the element is expected to render as an
''inline-block'' box depicting a Week control.
When the input-time binding applies to an <{input}> element whose
- type attribute is in the Time state, the element is expected to render as an
+ <{input/type}> attribute is in the Time state, the element is expected to render as an
''inline-block'' box depicting a Time control.
When the input-datetime-local binding applies to an <{input}> element
- whose type attribute is in the Local Date and Time state, the element is expected
+ whose <{input/type}> attribute is in the Local Date and Time state, the element is expected
to render as an ''inline-block'' box depicting a Local Date and Time control.
When the input-number binding applies to an <{input}> element whose
- type attribute is in the Number state, the element is expected to render as an
+ <{input/type}> attribute is in the Number state, the element is expected to render as an
''inline-block'' box depicting a Number control.
These controls are all expected to be about one line high, and about as wide as necessary to
@@ -1569,7 +1571,7 @@ path: includes/cldr.include
Predefined suggested values (provided by the list
attribute) are expected to be shown as tick marks on the slider, which the slider can snap to.
- User agents are expected to use the used value of the 'direction' property on the element to
+ User agents are expected to use the used value of the 'direction' property on the element to
determine the direction in which the slider operates. Typically, a left-to-right (''ltr'')
horizontal control would have the lowest value on the left and the highest value on the right, and
vice versa.
@@ -1577,7 +1579,7 @@ path: includes/cldr.include
When the input-color binding applies to an <{input}> element whose
- type attribute is in the Color state, the element is expected to render as an
+ <{input/type}> attribute is in the Color state, the element is expected to render as an
''inline-block'' box depicting a color well, which, when activated, provides the user with a color
picker (e.g., a color wheel or color palette) from which the color can be changed.
@@ -1588,27 +1590,27 @@ path: includes/cldr.include
When the input-checkbox binding applies to an <{input}> element whose
- type attribute is in the Checkbox state, the element is expected to render as an
+ <{input/type}> attribute is in the Checkbox state, the element is expected to render as an
''inline-block'' box containing a single checkbox control, with no label.
When the input-radio binding applies to an <{input}> element whose
- type attribute is in the Radio Button state, the element is expected to render as an
+ <{input/type}> attribute is in the Radio Button state, the element is expected to render as an
''inline-block'' box containing a single radio button control, with no label.
When the input-file binding applies to an <{input}> element whose
- type attribute is in the File Upload state, the element is expected to render as an
+ <{input/type}> attribute is in the File Upload state, the element is expected to render as an
''inline-block'' box containing a span of text giving the file name(s) of the selected files, if any, followed by a button that,
when activated, provides the user with a file picker from which the selection can be changed.
When the input-button binding applies to an <{input}> element whose
- type attribute is in the submit button, Reset Button, or Button state, the element is
+ <{input/type}> attribute is in the submit button, Reset Button, or Button state, the element is
expected to render as an ''inline-block'' box rendered as a button, about one line high, containing
- the contents of the element's value attribute, if any, or
- text derived from the element's type attribute in a
+ the contents of the element's <{input/value}> attribute, if any, or
+ text derived from the element's <{input/type}> attribute in a
user-agent-defined (and probably locale-specific) fashion, if not.
The <{marquee}> element
@@ -2232,7 +2234,7 @@ path: includes/cldr.include
This means that even an empty block can have the caret inside it, and that when
- the caret is in such an element, it prevents
+ the caret is in such an element, it prevents
margins from collapsing through the element.
Text rendered in native user interfaces
@@ -2384,7 +2386,7 @@ path: includes/cldr.include
- The {{Document}} has no author style sheets (whether referenced by HTTP headers, processing instructions, elements like <{link}>, inline elements like <{style}>, or any other mechanism).
- None of the elements in the {{Document}} have any presentational hints.
-
- None of the elements in the {{Document}} have any CSS styling attributes.
+
- None of the elements in the {{Document}} have any style attributes.
- None of the elements in the {{Document}} are in any of the following namespaces: HTML namespace, SVG namespace, MathML namespace
- The {{Document}} has no focusable area (e.g., from XLink) other than the viewport.
- The {{Document}} has no hyperlinks (e.g., from XLink).
diff --git a/sections/semantics-document-metadata.include b/sections/semantics-document-metadata.include
index d214599ac6..e11b38cef7 100644
--- a/sections/semantics-document-metadata.include
+++ b/sections/semantics-document-metadata.include
@@ -133,17 +133,16 @@
- title .
text [ = value ]
-
- Returns the contents of the element, ignoring child nodes that aren't
Text nodes.
+ Returns the child text content of the element.
Can be set, to replace the element's children with the given value.
- The IDL attribute text must return a concatenation of the contents of
- all the Text nodes that are children of the title element (ignoring
- any other nodes such as comments or elements), in tree order. On setting, it must act the
- same way as the {{Node/textContent}} IDL attribute.
+ The IDL attribute text must return the
+ child text content of the title element. On
+ setting, it must act the same way as the {{Node/textContent}} IDL attribute.
@@ -447,8 +446,8 @@
<link href="chapter1.html" rel="prev" rev="next">
<link href="chapter3.html" rel="next" rev="prev">
- From chapter1.html, the link to chapter2.html is the "next" chapter in the series in the
- forward direction, and the "previous" chapter in the reverse diretion (from
+ From chapter1.html, the link to chapter2.html is the "next" chapter in the series in
+ the forward direction, and the "previous" chapter in the reverse diretion (from
chapter2.html to chapter1.html).
@@ -468,8 +467,8 @@
- The crossorigin attribute is a CORS settings attribute. It is
- intended for use with external resource links.
+ The crossorigin attribute is a
+ CORS settings attribute. It is intended for use with external resource links.
The exact behavior for links to external resources depends on the exact relationship, as defined
for the relevant link type. Some of the attributes control whether or not the external resource is
@@ -477,8 +476,8 @@
For external resources that are represented in the DOM (for example, style sheets), the DOM
representation must be made available (modulo cross-origin restrictions) even if the resource is
- not applied. To obtain the resource, the user agent must
- run the following steps:
+ not applied. To obtain the resource, the user agent
+ must run the following steps:
1. If the <{link/href}> attribute's value is the empty string, then abort these steps.
@@ -526,10 +525,10 @@
* The relationship between this document and the resource (given by the <{link/rel}>
attribute)
- * The title of the resource (given by the title attribute).
+ * The title of the resource (given by the <{link/title}> attribute).
* The address of the resource (given by the <{link/href}> attribute).
- * The language of the resource (given by the hreflang attribute).
- * The optimum media for the resource (given by the media attribute).
+ * The language of the resource (given by the <{link/hreflang}> attribute).
+ * The optimum media for the resource (given by the <{link/media}> attribute).
User agents could also include other information, such as the type of the resource (as given by
the type attribute).
@@ -541,11 +540,11 @@
link's location within the document.
- The media attribute says which media the resource applies to. The value
- must be a valid media query list.
+ The media attribute says which media the resource
+ applies to. The value must be a valid media query list.
- If the link is a hyperlink then the media attribute is purely advisory, and
+ If the link is a hyperlink then the <{link/media}> attribute is purely advisory, and
describes for which media the document in question was designed.
However, if the link is an external resource link, then the media attribute
@@ -563,25 +562,25 @@
The default, if the media attribute is omitted, is " all", meaning that
by default links apply to all media.
- The hreflang attribute on the <{link}> element has the same
- semantics as the hreflang attribute on the <{a}> element.
-
- The type attribute gives the MIME type of the linked resource. It
- is purely advisory. The value must be a valid mime type.
-
- For external resource links, the type attribute is used as a hint to user
- agents so that they can avoid fetching resources they do not support. If the
- attribute is present, then the user agent must assume that the resource is of the given type (even
- if that is not a valid mime type, e.g., the empty string). If the attribute is omitted, but
- the external resource link type has a default type defined, then the user agent must assume that
- the resource is of that type. If the user agent does not support the given MIME type for the given
- link relationship, then the user agent should not obtain the resource; if the user agent does support the
- given MIME type for the given link relationship, then the user agent should obtain the
- resource at the appropriate time as specified for the external resource link's particular
- type. If the attribute is omitted, and the external resource link type does not have a default
- type defined, but the user agent would obtain the resource if the type was known and
- supported, then the user agent should obtain the resource under the assumption that it will
- be supported.
+ The hreflang attribute on the <{link}> element has
+ the same semantics as the {{HTMLLinkElement/hreflang}} attribute on the <{a}> element.
+
+ The type attribute gives the MIME type of
+ the linked resource. It is purely advisory. The value must be a valid mime type.
+
+ For external resource links, the <{link/type}> attribute is used as a hint to user agents
+ so that they can avoid fetching resources they do not support. If the attribute is present, then
+ the user agent must assume that the resource is of the given type (even if that is not a
+ valid mime type, e.g., the empty string). If the attribute is omitted, but the external
+ resource link type has a default type defined, then the user agent must assume that the resource
+ is of that type. If the user agent does not support the given MIME type for the given link
+ relationship, then the user agent should not obtain the resource; if the user agent does
+ support the given MIME type for the given link relationship, then the user agent should
+ obtain the resource at the appropriate time as specified for the
+ external resource link's particular type. If the attribute is omitted, and the external
+ resource link type does not have a default type defined, but the user agent would obtain
+ the resource if the type was known and supported, then the user agent should obtain the
+ resource under the assumption that it will be supported.
User agents must not consider the type attribute authoritative — upon
@@ -589,16 +588,16 @@
actual type. Only the actual type (as defined in the next paragraph) is used to determine
whether to apply the resource, not the aforementioned assumed type.
- If the external resource link type defines rules for processing the resource's
- Content-Type metadata, then those rules apply. Otherwise, if the resource is expected to
- be an image, user agents may apply the image sniffing rules, with the
- official type being the type determined from the resource's
- Content-Type metadata, and use the resulting computed type of the resource as if it was
- the actual type. Otherwise, if neither of these conditions apply or if the user agent opts not
- to apply the image sniffing rules, then the user agent must use the resource's
- Content-Type metadata to determine the type of the resource. If there is no type
- metadata, but the external resource link type has a default type defined, then the user agent
- must assume that the resource is of that type.
+ If the external resource link type defines
+ rules for processing the resource's Content-Type metadata, then those rules apply.
+ Otherwise, if the resource is expected to be an image, user agents may apply the
+ image sniffing rules, with the official type being the type determined from
+ the resource's Content-Type metadata, and use the resulting
+ computed type of the resource as if it was the actual type. Otherwise, if neither of
+ these conditions apply or if the user agent opts not to apply the image sniffing rules, then the
+ user agent must use the resource's Content-Type metadata to determine the type of the
+ resource. If there is no type metadata, but the external resource link type has a default type
+ defined, then the user agent must assume that the resource is of that type.
The stylesheet link type defines rules for processing the resource's
@@ -618,9 +617,9 @@
<link rel="stylesheet" href="C">
- ...then a compliant user agent that supported only CSS style sheets would fetch the B and C files, and
- skip the A file (since text/plain is not the MIME type for CSS style
- sheets).
+ ...then a compliant user agent that supported only CSS style sheets would fetch the B and C
+ files, and skip the A file (since text/plain is not the MIME type for CSS
+ style sheets).
For files B and C, it would then check the actual types returned by the server. For those that
are sent as text/css, it would apply the styles, but for those labeled as
@@ -633,14 +632,14 @@
title attribute gives the title of the link. With one exception, it is
- purely advisory. The value is text. The exception is for style sheet links, where the
- title attribute defines alternative style sheet sets.
+ The title attribute gives the title of the link.
+ With one exception, it is purely advisory. The value is text. The exception is for style sheet
+ links, where the <{link/title}> attribute defines alternative style sheet sets.
- The title attribute on <{link}> elements differs from the global
- title attribute of most other elements in that a link without a title does not
- inherit the title of the parent element: it merely has no title.
+ The <{link/title}> attribute on <{link}> elements differs from the global <{global/title}>
+ attribute of most other elements in that a link without a title does not inherit the title of
+ the parent element: it merely has no title.
The sizes attribute is used with the icon link type. The attribute must
@@ -664,37 +663,42 @@
and thus their semantics can be different from same-named HTML types.
- The IDL attributes href, rel,
- rev, media, hreflang,
- type, and sizes each must reflect the
+ The IDL attributes href,
+ rel,
+ rev,
+ media,
+ hreflang,
+ type, and
+ sizes each must reflect the
respective content attributes of the same name.
- The crossOrigin IDL attribute must reflect the
- crossorigin content attribute.
+ The crossOrigin IDL attribute must
+ reflect the <{link/crossorigin}> content attribute.
- The IDL attribute relList must reflect
- the <{link/rel}> content attribute.
+ The IDL attribute relList must
+ reflect the <{link/rel}> content attribute.
- relList's DOMTokenList's supported tokens are the keywords
- defined in HTML link types which are allowed on link elements and supported
+ relList's {{DOMTokenList}}'s supported tokens are the keywords
+ defined in HTML link types which are allowed on <{link}> elements and supported
by the user agent.
- <{link/rel}>'s
- supported tokens are the keywords defined in
- HTML link types which are allowed on link elements, impact
- the processing model, and are supported by the user agent. The possible supported tokens are
- alternate, dns-prefetch, icon, preconnect, prefetch,
- prerender, and stylesheet.
- <{link/rel}>'s supported tokens must only include the tokens from
- this list that the user agent implements the processing model for.
-
- Other specifications may add HTML link types as
- defined in Other link types, such as [[!RESOURCE-HINTS]]. These specifications may require
- that their link types be included in <{link/rel}>'s supported
- tokens.
+ <{link/rel}>'s supported tokens are the keywords defined in HTML link types which
+ are allowed on <{link}> elements, impact the processing model, and are supported by the user
+ agent. The possible supported tokens are alternate,
+ dns-prefetch, icon, preconnect,
+ prefetch, prerender, search,
+ stylesheet and next. <{link/rel}>'s supported tokens must only
+ include the tokens from this list that the user agent implements the processing model for.
+
+ Other specifications may add HTML link types as defined in Other link types, with
+ the following additional requirements:
+
+ * Such specifications may require that their link types be included in <{link/rel}>'s supported
+ tokens.
+ * Such specifications may specify that their link types are body-ok.
- The LinkStyle interface is also implemented by this element. [[!CSSOM]]
+ The {{LinkStyle}} interface is also implemented by this element. [[!CSSOM]]
Here, a set of <{link}> elements provide some style sheets:
@@ -1209,12 +1213,12 @@
urlRecord be the resulting URL record.
26. End: Perform one or more of the following steps:
* After the refresh has come due (as defined below), if the user has not canceled the
- redirect and if the <{meta}> element's node document's active
- sandboxing flag set does not have the sandboxed automatic features browsing
- context flag set, navigate the {{Document}}'s
- browsing context to urlRecord, with replacement enabled,
- and with the {{Document}}'s browsing context as the
- source browsing context.
+ redirect and if the <{meta}> element's node document's
+ active sandboxing flag set does not have the
+ sandboxed automatic features browsing context flag set, navigate the
+ {{Document}}'s browsing context to urlRecord, with
+ replacement enabled, and with the {{Document}}'s browsing context as
+ the source browsing context.
For the purposes of the previous paragraph, a refresh is said to have come due as
soon as the later of the following two conditions occurs:
@@ -1546,10 +1550,9 @@
XML parser, and one of its child nodes is modified by a script,
For styling languages that consist of pure text (as opposed to XML), a style
- element's style data is the concatenation of the contents of all the Text
- nodes that are children of the <{style}> element (not any other nodes such as comments
- or elements), in tree order. For XML-based styling languages, the style data
- consists of all the child nodes of the <{style}> element.
+ element's style data is the child text content of the <{style}> element (not any
+ other nodes such as comments or elements), in tree order. For XML-based styling
+ languages, the style data consists of all the child nodes of the <{style}> element.
The update a style block algorithm for CSS ( text/css) is as
follows:
diff --git a/sections/semantics-embedded-content.include b/sections/semantics-embedded-content.include
index 31c6cbb9b4..ad410ee205 100644
--- a/sections/semantics-embedded-content.include
+++ b/sections/semantics-embedded-content.include
@@ -297,7 +297,7 @@
These sizes do not necessarily have to match up exactly with the actual image width as specified in the CSS.
The user agent will pick a width from the sizes attribute,
- using the first item with a <media-condition> (the part in parentheses) that evaluates to true,
+ using the first item with a < > (the part in parentheses) that evaluates to true,
or using the last item (calc(33vw - 100px)) if they all evaluate to false.
For example, if the viewport width is 29em,
@@ -720,7 +720,7 @@
<source-size-list> = <source-size># [ , <source-size-value> ]? | <source-size-value>
- <source-size> = <media-condition> <source-size-value>
+ <source-size> = <> <source-size-value>
<source-size-value> = <length>
@@ -787,7 +787,7 @@
An image request is initially unavailable.
When an <{img}> element is available,
- it provides a paint source
+ it provides a paint source
whose width is the image's
density-corrected intrinsic width (if any),
whose height is the image's
@@ -1813,9 +1813,9 @@
that is a parse error.
- Parse the remaining component values in unparsed size
- as a <media-condition>.
+ as a <>.
If it does not parse correctly,
- or it does parse correctly but the <media-condition> evaluates to false,
+ or it does parse correctly but the <> evaluates to false,
continue to the next iteration of this algorithm. [[!MEDIAQ]]
- Return size and exit this algorithm.
@@ -1840,7 +1840,7 @@
While a valid source size list only contains a bare <source-size-value>
- (without an accompanying <media-condition>)
+ (without an accompanying <>)
as the last entry in the <source-size-list>,
the parsing algorithm technically allows such at any point in the list,
and will accept it immediately as the size
@@ -5246,7 +5246,7 @@ attribute's value is a type that a plugin supports, then the value of the
data itself.
When a <{video}> element's media resource has a video channel, the
- element provides a paint source whose width is the media resource's
+ element provides a paint source whose width is the media resource's
intrinsic width, whose height is the
media resource's intrinsic height, and whose appearance is
the frame of video corresponding to the current playback position, if that is available, or else
diff --git a/sections/semantics-forms.include b/sections/semantics-forms.include
index 2203c5ebb6..adf0868532 100644
--- a/sections/semantics-forms.include
+++ b/sections/semantics-forms.include
@@ -8242,7 +8242,8 @@ You cannot submit this form when the field is incorrect.
- Content model:
- If the element has a <{option/label}> attribute and a <{option/value}> attribute: Nothing.
- If the element has a <{option/label}> attribute but no <{option/value}> attribute: Text.
- - If the element has no <{option/label}> attribute: Text.
+ - If the element has no <{option/label}> attribute: and is not a child of a <{datalist}> element: Text that is not inter-element whitespace.
+ - If the element has no <{option/label}> attribute and is a child of a <{datalist}> element: Text.
- Tag omission in text/html:
- An <{option}> element's end tag may be omitted if
the <{option}> element is immediately followed by another <{option}> element, or
@@ -8398,8 +8399,8 @@ You cannot submit this form when the field is incorrect.
element's index.
The
text IDL attribute, on getting, must
- return the result of stripping and collapsing whitespace from the concatenation of
- data of all the {{Text}} node descendants of the <{option}> element, in tree order,
+ return the result of stripping and collapsing whitespace from the child text content
+ of the <{option}> element, in tree order,
excluding any that are descendants of descendants of the <{option}> element that are themselves
<{script}> elements in the HTML namespace or <{script}> elements in the
SVG namespace.
diff --git a/sections/semantics-interactive-elements.include b/sections/semantics-interactive-elements.include
index 92311a09ce..9e65ead5f7 100644
--- a/sections/semantics-interactive-elements.include
+++ b/sections/semantics-interactive-elements.include
@@ -1356,7 +1356,7 @@
When an element subject is placed in centered alignment mode,
and when it is in that mode and has new rendering boxes created, the user agent must set up the
- element such that its top static position, for the purposes of calculating the used value of the
+ element such that its top static position, for the purposes of calculating the used value of the
'top' property, is the value that would place the element's top margin edge as far from the top of
the viewport as the element's bottom margin edge from the bottom of the viewport, if the element's
height is less than the height of the viewport, and otherwise is the value that would place the
@@ -1369,7 +1369,7 @@
This top static position of a <{dialog}> element with centered alignment
must remain the element's top static position until its boxes are recreated. (The element's static
- position is only used in calculating the used value of the 'top' property in certain situations;
+ position is only used in calculating the used value of the 'top' property in certain situations;
it's not used, for instance, to position the element if its 'position' property is set to
''static''.)
diff --git a/sections/semantics-links.include b/sections/semantics-links.include
index 9f5e0a8f97..d832493dfe 100644
--- a/sections/semantics-links.include
+++ b/sections/semantics-links.include
@@ -857,9 +857,9 @@
Link types
- The following table summarizes the link types that are defined by this specification. This
- table is non-normative; the actual definitions for the link types are given in the next few
- sections.
+ The following table summarizes the link types that are defined by this specification, by their
+ coresponding keywords. This table is non-normative; the actual definitions for the link types are
+ given in the next few sections.
In this section, the term referenced document refers to the resource identified by the
element representing the link, and the term current document refers to the resource within
@@ -867,23 +867,30 @@
To determine which link types apply to a <{link}>, <{a}>, or <{area}> element, the element's
<{links/rel}> attribute must be split on spaces. The
- resulting tokens are the link types that apply to that element.
+ resulting tokens are the keywords for the link types that apply to that element.
Except where otherwise specified, a keyword must not be specified more than once per <{link/rel}>
attribute.
- Link types are always ASCII case-insensitive, and must be compared as such.
+ Some of the sections that follow the table below list synonyms for certain keywords. The indicated
+ synonyms are to be handled as specified by user agents, but must not be used in documents (for
+ example, the keyword "copyright").
- Certain keywords are said to be body-ok. This affects whether <{link}>
- elements are allowed in the body
+ Keywords are always ASCII case-insensitive, and must be compared as such.
Thus, rel="next" is the same as rel="NEXT".
+ Keywords that are body-ok affect whether <{link}> elements are
+ allowed in the body. The body-ok keywords defined by this specification are
+ prefetch, and stylesheet. Other specifications
+ can also define body-ok keywords.
+
| Link type |
Effect on... |
+ body-ok |
Brief description |
@@ -897,6 +904,7 @@
alternate |
hyperlink |
hyperlink |
+ · |
Gives alternate representations of the current document. |
@@ -904,6 +912,7 @@
author |
hyperlink |
hyperlink |
+ · |
Gives a link to the author of the current document or article. |
@@ -911,13 +920,23 @@
bookmark |
not allowed |
hyperlink |
+ · |
Gives the permalink for the nearest ancestor section. |
+
+ external |
+ not allowed |
+ Annotation |
+ · |
+ Indicates that the referenced document is not part of the same site as the current document. |
+
+
help |
hyperlink |
hyperlink |
+ · |
Provides a link to context-sensitive help. |
@@ -925,6 +944,7 @@
icon |
External Resource |
not allowed |
+ · |
Imports an icon to represent the current document. |
@@ -932,6 +952,7 @@
license |
hyperlink |
hyperlink |
+ · |
Indicates that the main content of the current document is covered by the copyright license described by the referenced document. |
@@ -939,6 +960,7 @@
next |
hyperlink |
hyperlink |
+ · |
Indicates that the current document is a part of a series, and that the next document in the series is the referenced document. |
@@ -946,6 +968,7 @@
nofollow |
not allowed |
Annotation |
+ · |
Indicates that the current document's original author or publisher does not endorse the referenced document. |
@@ -953,13 +976,31 @@
noreferrer |
not allowed |
Annotation |
+ · |
Requires that the user agent not send an HTTP Referer (sic) header if the user follows the hyperlink. |
+
+ noopener |
+ not allowed |
+ Annotation |
+ · |
+ Requires that any browsing context created by following the hyperlink must not have an opener browsing context. |
+
+
+
+ prefetch |
+ External Resource |
+ External Resource |
+ Yes |
+ Specifies that the target resource should be preemptively cached. |
+
+
prev |
hyperlink |
hyperlink |
+ · |
Indicates that the current document is a part of a series, and that the previous document in the series is the referenced document. |
@@ -967,6 +1008,7 @@
search |
hyperlink |
hyperlink |
+ · |
Gives a link to a resource that can be used to search through the current document and its related pages. |
@@ -974,6 +1016,7 @@
stylesheet |
External Resource |
not allowed |
+ · |
Imports a stylesheet. |
@@ -981,19 +1024,13 @@
tag |
not allowed |
hyperlink |
+ · |
Gives a tag (identified by the given address) that applies to the current document. |
-
-
- Some of the types described below list synonyms for these values. These are to be handled as specified by user agents, but must not be used
- in documents.
-
-
-
Link type "alternate"
The alternate keyword may be used with <{link}>,
diff --git a/sections/semantics-scriptings.include b/sections/semantics-scriptings.include
index 247f6b9e38..fdfb1e0262 100644
--- a/sections/semantics-scriptings.include
+++ b/sections/semantics-scriptings.include
@@ -436,8 +436,8 @@ o............A....e
attribute with any leading or trailing sequences of space characters removed.
Otherwise, the element has a non-empty <{script/language}> attribute; let
- the script block's type string for this <{script}> element be the concatenation of
- the string "`text/`" followed by the value of the <{script/language}> attribute.
+ the script block's type string for this <{script}> element be the
+ child text content of the <{script/language}> attribute.
The <{script/language}> attribute is never conforming, and is always ignored
if there is a <{script/type}> attribute present.
@@ -1139,8 +1139,7 @@ o............A....e
2. Make a list of every <{noscript}> element in the document. For every <{noscript}> element
in that list, perform the following steps:
- 1. Let s be the concatenation of all the {{Text}} node children of the
- <{noscript}> element.
+ 1. Let s be the child text content of the <{noscript}> element.
2. Set the outerHTML attribute of the <{noscript}> element to the value of
s. (This, as a side-effect, causes the <{noscript}> element to be removed
from the document.) [[!DOMPARSING]]
@@ -1643,8 +1642,8 @@ o............A....e
attribute, those values being interpreted in CSS pixels, and being updated as the attributes are
set, changed, or removed.
- When a <{canvas}> element represents embedded content, it provides
- a paint source whose width is the element's intrinsic width, whose height is
+ When a <{canvas}> element represents embedded content, it provides
+ a paint source whose width is the element's intrinsic width, whose height is
the element's intrinsic height, and whose appearance is the element's bitmap.
Whenever the width and height content attributes are set, removed, changed, or
diff --git a/sections/semantics-tabular-data.include b/sections/semantics-tabular-data.include
index 66508de2fe..e3f9dd3c29 100644
--- a/sections/semantics-tabular-data.include
+++ b/sections/semantics-tabular-data.include
@@ -529,7 +529,7 @@ side in the right column.</p>
-
-<figure aria-labelledby="caption">
+<figure aria-labelledby="caption">
<p>Characteristics are given in the second column, with the
negative side in the left column and the positive side in the right
column.</p>
@@ -552,16 +552,16 @@ side in the right column.</p>
</table>
</figure>
The <{figure}> in this example has been labeled by the table <{caption}>
- using aria-labelledby.
+ The <{figure}> in this example has been labeled by the table <{caption}>
+ using aria-labelledby.
Authors may also use other techniques, or combinations of the above techniques, as
- appropriate.
-
- Regardless of the method used to provide additional descriptive information for a
- table, if a <{table}> needs a caption, authors should use a <{caption}> element
+ appropriate.
+
+ Regardless of the method used to provide additional descriptive information for a
+ table, if a <{table}> needs a caption, authors should use a <{caption}> element
as it is the most robust method for providing an accessible caption for a table.
The best option, of course, rather than writing a description explaining the way the table is
@@ -1521,15 +1521,15 @@ the cell that corresponds to the values of the two dice.
A table consists of cells aligned on a two-dimensional grid of
slots with coordinates (x, y). The grid is finite, and
- is either empty or has one or more slots. If the grid has one or more slots, then
- the x coordinates are always in the range
+ is either empty or has one or more slots. If the grid has one or more slots, then
+ the x coordinates are always in the range
0 ≤ x < xwidth,
and the y coordinates are always in the range
0 ≤ y < yheight.
If one or both of xwidth and yheight are zero,
then the table is empty (has no slots). Tables correspond to <{table}> elements.
- A cell is a set of slots anchored at a slot
+ A cell is a set of slots anchored at a slot
(cellx, celly), and with
a particular width and height such that the cell covers
all the slots with coordinates (x, y) where
@@ -1833,7 +1833,7 @@ the cell that corresponds to the values of the two dice.
Rows: While the current element is not one of the following
elements, advance the current
- element to the next child of the table:
+ element to the next child of the <{table}>:
- <{thead}>
@@ -1850,7 +1850,7 @@ the cell that corresponds to the values of the two dice.
If the current element is a <{tfoot}> and the value of
table footer is null, then run the following substeps:
-
+
-
@@ -1868,7 +1868,7 @@ the cell that corresponds to the values of the two dice.
If the current element is a <{thead}> and the value of
table header is null, then run the following substeps:
-
+
-
diff --git a/sections/semantics-textlevel.include b/sections/semantics-textlevel.include
index 4b45eb15cd..b086c1d533 100644
--- a/sections/semantics-textlevel.include
+++ b/sections/semantics-textlevel.include
@@ -1876,9 +1876,8 @@ affected by the heat source (upper left) and the food source (lower right).</
descendants.
The datetime value of a <{time}> element is the value of the element's
- <{time/datetime}> content attribute, if it has one, otherwise the concatenation of the contents of
- all the {{Text}} nodes that are children of the <{time}> element (ignoring any other
- nodes such as comments or elements), in tree order.
+ <{time/datetime}> content attribute, if it has one, otherwise the child text content of
+ the <{time}> element.
The datetime value of a <{time}> element must match one of the following
diff --git a/sections/semantics.include b/sections/semantics.include
index f098229f88..c0f29f781d 100644
--- a/sections/semantics.include
+++ b/sections/semantics.include
@@ -121,7 +121,7 @@ path: sections/semantics-common-idioms.include
when compared to other attributes must be compared according to its original case. In both cases,
the comparison is case-sensitive.
- Attribute selectors on an HTML element in an HTML document must treat the
+ Attribute selectors on an HTML element in an HTML document must treat the
values of attributes with the following names as ASCII case-insensitive, with one
exception as noted in [[#rendering]]:
diff --git a/sections/webappapis.include b/sections/webappapis.include
index b0c9677cfb..e373ca5498 100644
--- a/sections/webappapis.include
+++ b/sections/webappapis.include
@@ -1208,22 +1208,26 @@
docs all {{Document}} objects whose browsing context's top-level
browsing context is B.
-
Whether a top-level browsing context would benefit from having
- its rendering updated depends on various factors, such as the update frequency. For
- example, if the browser is attempting to achieve a 60 Hz refresh rate, then these steps
- are only necessary every 60th of a second (about 16.7ms). If the browser finds that a
- top-level browsing context is not able to sustain this rate, it might drop to a
- more sustainable 30Hz for that set of {{Document}}s, rather than occasionally dropping
- frames. (This specification does not mandate any particular model for when to update the
- rendering.) Similarly, if a top-level browsing context is in the background, the
- user agent might decide to drop that page to a much slower 4Hz, or even less.
-
- Another example of why a browser might skip updating the rendering is to
- ensure certain tasks are executed immediately after each other, with only
- microtask checkpoints interleaved (and without, e.g.,
- animation frame callbacks interleaved).
- For example, a user agent might wish to coalesce timer callbacks together, with no
- intermediate rendering updates.
+
+ Whether a top-level browsing context would benefit from having its rendering
+ updated depends on various factors, such as the update frequency. For example, if the
+ browser is attempting to achieve a 60 Hz refresh rate, then these steps are only
+ necessary every 60th of a second (about 16.7ms). If the browser finds that a
+ top-level browsing context is not able to sustain this rate, it might drop to a
+ more sustainable 30Hz for that set of {{Document}}s, rather than occasionally dropping
+ frames. (This specification does not mandate any particular model for when to update the
+ rendering.) Similarly, if a top-level browsing context is in the background, the
+ user agent might decide to drop that page to a much slower 4Hz, or even less.
+
+
+
+ Another example of why a browser might skip updating the rendering is to ensure certain
+ tasks are executed immediately after each other, with only
+ microtask checkpoints interleaved (and without, e.g.,
+ animation frame callbacks interleaved).
+ For example, a user agent might wish to coalesce timer callbacks together, with no
+ intermediate rendering updates.
+
4. If there are a nested browsing contexts B that the user agent believes
would not benefit from having their rendering updated at this time, then remove from
docs all {{Document}} objects whose browsing context is in B.
diff --git a/single-page.bs b/single-page.bs
index 419a4fba77..1ddf6342e8 100644
--- a/single-page.bs
+++ b/single-page.bs
@@ -230,7 +230,7 @@ urlPrefix: https://www.w3.org/TR/css3-syntax/; type: dfn; spec: css3-syntax;
url: https://www.w3.org/TR/css3-syntax/#typedef-whitespace-token; type: type; spec: css3-syntax;
text: whitespace
url: https://www.w3.org/TR/css-style-attr/#syntax; type: dfn; spec: css-style-attr;
- text: CSS styling attribute
+ text: style attribute
url: https://www.khronos.org/registry/webgl/specs/1.0/#WEBGLRENDERINGCONTEXT; type: interface; spec: webgl;
text: WebGLRenderingContext
url: https://www.w3.org/TR/jlreq/#positioning_of_jukugoruby; type: dfn; spec: jlreq;
diff --git a/styles/styles-html.css b/styles/styles-html.css
index 635e8befb6..c10ab45961 100644
--- a/styles/styles-html.css
+++ b/styles/styles-html.css
@@ -2,7 +2,8 @@
.applies thead code { display: block; }
.applies tbody th { white-space: nowrap; }
.applies td { text-align: center; }
-.applies .yes { background: yellow; }
+.applies .yes, .yesno .yes { background: yellow; }
+.yesno .yes, .yesno .no { text-align: center; }
td.eg { border-width: thin; text-align: center; }
|