diff --git a/sections/attributes.include b/sections/attributes.include index 79d2dcffa4..6fadabf335 100644 --- a/sections/attributes.include +++ b/sections/attributes.include @@ -1,6 +1,6 @@ diff --git a/sections/dom.include b/sections/dom.include index d8135b7e7a..4cd3169ad3 100644 --- a/sections/dom.include +++ b/sections/dom.include @@ -1,20 +1,22 @@
+ diff --git a/sections/editing.include b/sections/editing.include index a8c1093008..bcebe55bb5 100644 --- a/sections/editing.include +++ b/sections/editing.include @@ -1,14 +1,18 @@
+ diff --git a/sections/iana.include b/sections/iana.include index fd0b33f926..f9cb02babc 100644 --- a/sections/iana.include +++ b/sections/iana.include @@ -1,4 +1,24 @@
+ + +

IANA considerations

text/html

diff --git a/sections/semantics-common-idioms.include b/sections/semantics-common-idioms.include index a65422468f..7bebe33b09 100644 --- a/sections/semantics-common-idioms.include +++ b/sections/semantics-common-idioms.include @@ -1,20 +1,20 @@
+ + It covers + - Subheadings and taglines + - "breadcrumb" navigation information + - Tag Clouds + - Conversations + - Footnotes +-->

Common idioms without dedicated elements

diff --git a/sections/semantics-document-metadata.include b/sections/semantics-document-metadata.include index 8d2e1ac9d5..1c45ce2bd3 100644 --- a/sections/semantics-document-metadata.include +++ b/sections/semantics-document-metadata.include @@ -1,20 +1,21 @@
+ + It covers elements in the head of the document: + - head + - title + - base + - meta + - link + - style +-->

Document metadata

diff --git a/sections/semantics-links.include b/sections/semantics-links.include index e7f66d1c17..140d3268de 100644 --- a/sections/semantics-links.include +++ b/sections/semantics-links.include @@ -1,6 +1,26 @@
+ + @@ -10,7 +30,6 @@ There are two kinds of links in HTML:
-
Links to external resources
These are links to resources that are to be used to augment the current document, @@ -28,7 +47,7 @@ <{link/rel}> attribute, as defined for those keywords in the link types section. Similarly, for <{a}> and <{area}> elements with an <{links/href}> attribute and a <{links/rel}> attribute, - links must be created for the keywords of the <{links/rel}> attribute as defined for those keywords in the + links must be created for the keywords of the <{links/rel}> attribute as defined for those keywords in the link types section. Unlike <{link}> elements, however, <{a}> and <{area}> elements with an <{links/href}> attribute that either do not have a <{links/rel}> attribute, or whose <{links/rel}> attribute has no keywords that are defined as specifying hyperlinks, must also create a hyperlink. @@ -81,7 +100,7 @@ The ping attribute, if present, gives the URLs of the resources that are interested in being notified if the user follows the hyperlink. The value must be a set of space-separated tokens, each of which must be a valid non-empty URL - whose scheme is an HTTP(S) scheme. The value is used by the user agent for hyperlink auditing. + whose scheme is an HTTP(S) scheme. The value is used by the user agent for hyperlink auditing. The rel attribute on <{a}> and <{area}> elements controls what kinds of links the elements create. The attribute's value @@ -654,9 +673,10 @@ - When a user follows a hyperlink created by an element - subject, optionally with a hyperlink suffix, the user agent must run the - following steps: + When a user + follows a hyperlink + created by an element subject, optionally with a hyperlink suffix, the + user agent must run the following steps:
    @@ -930,7 +950,7 @@ then run these steps for each resulting URL record ping URL (ignoring tokens that fail to parse): * If ping URL's scheme is not an HTTP(S) scheme, then return. - * Optionally, return + * Optionally, return (for example the user agent may ignore any or all ping URLs in accordance with the user's express preferences). * Let request be a new request, whose URL is ping URL, method is post, body is ping, client is the environment settings object of the document containing the hyperlink, destination is the empty string, credentials mode is include, referrer is "no-referrer", @@ -940,20 +960,20 @@
    If the URL of the document object containing the hyperlink being audited and the ping URL have the same origin
    -
    Or if the origins are different but the HTTPS state of the document containing the hyperlink being audited is +
    Or if the origins are different but the HTTPS state of the document containing the hyperlink being audited is "none"
    request must include a ping-from header with the URL of the document containing the hyperlink as its value, and a ping-to HTTP header with the target URL as its value.
    -
    Otherwise
    -
    request must must include a ping-to HTTP header with target URL as its value. +
    Otherwise
    +
    request must must include a ping-to HTTP header with target URL as its value. Note: request does not include a ping-from header.
    - + * Fetch request. This may be done in parallel with the primary fetch, and is independent of the result of that fetch. - User agents should allow the user to alter this behavior. + User agents should allow the user to alter this behavior. For example, in conjunction with a setting that disables the sending of HTTP referrer (sic) headers. Based on the user's preferences, user agents may ignore the <{links/ping}> attribute completely, or selectively ignore URLs (for example third party URLs); this is explicitly accounted for in the steps above. @@ -964,7 +984,7 @@ When the <{links/ping}> attribute is present, user agents should make it clear to the user that following the hyperlink will also cause secondary requests to be sent in the background. -
    +
    For example, a user agent could visually display the host names of the target ping URLs, and the hyperlink's actual URL, in a tooltip.
    @@ -1010,8 +1030,8 @@

    So 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 dns-prefetch, - external, preconnect, + allowed in the body. The body-ok keywords defined by this specification are dns-prefetch, + external, preconnect, prefetch, preload, prerender and <{link/stylesheet}>. Other specifications can also define body-ok keywords. @@ -1242,13 +1262,13 @@
    The following <{link}> element gives the syndication feed for the current page: - + <link rel="alternate" type="application/atom+xml" href="data.xml"> - + The following extract offers various different syndication feeds: - + <p>You can access the planets database using Atom feeds:</p> <ul> @@ -1359,7 +1379,7 @@ The <{link/dns-prefetch}> keyword may be used with <{link}>.This keyword is <a>body-ok</a>. -The <{link/dns-prefetch}> keyword is used to indicate an origin that will be used to fetch +The <{link/dns-prefetch}> keyword is used to indicate an origin that will be used to fetch required resources, and that the user agent SHOULD resolve as early as possible. See [[resource-hints]] for full definition. @@ -1608,46 +1628,46 @@ See [[resource-hints]] for full definition. <h5 id="link-type-preconnect">Link type "<dfn element-state for="link"><code>preconnect</code></dfn>"</h5> The <{link/preconnect}> keyword may be used with <{link}>.This keyword is <a>body-ok</a>. - -The <{link/preconnect}> keyword is used to initiate an early connection, which includes the DNS lookup, TCP handshake, - and optional TLS negotiation, allows the user agent to mask the - high latency costs of establishing a connection. + +The <{link/preconnect}> keyword is used to initiate an early connection, which includes the DNS lookup, TCP handshake, + and optional TLS negotiation, allows the user agent to mask the + high latency costs of establishing a connection. See [[resource-hints]] for full definition. <h5 id="link-type-prefetch">Link type "<dfn element-state for="link"><code>prefetch</code></dfn>"</h5> -The <{link/prefetch}> keyword may be used with <{link}>. This keyword creates an <a>external resource link</a>. +The <{link/prefetch}> keyword may be used with <{link}>. This keyword creates an <a>external resource link</a>. This keyword is <a>body-ok</a>. The <{link/prefetch}> keyword is used to identify a resource that might be required - by the next navigation, and that the user agent SHOULD fetch, - such that the user agent can deliver a faster response once the + by the next navigation, and that the user agent SHOULD fetch, + such that the user agent can deliver a faster response once the resource is requested in the future. See [[resource-hints]] for full definition. - + <h5 id="link-type-preload">Link type "<dfn element-state for="link"><code>preload</code></dfn>"</h5> The <{link/preload}> keyword may be used with <{link}>. This keyword creates an <a>external resource link</a>. This keyword is <a>body-ok</a>. The <{link/preload}> keyword indicates that the user agent must preemptively fetch and cache the specified resource according to the <a>potential destination</a> given by the <{link/as}> attribute (and the <a>priority</a> associated with the <a>corresponding</a> <a>destination</a>), as it is highly likely that the user will require this resource for current navigation. User agents must implement the processing model of the <{link/preload}> keyword described in the Preload specification. [[!Preload]] - + There is no default type for resources given by the <{link/preload}> keyword. <h5 id="link-type-prerender">Link type "<dfn element-state for="link"><code>prerender</code></dfn>"</h5> -The <{link/prerender}> keyword may be used with <{link}>. This keyword creates an <a>external resource link</a>. +The <{link/prerender}> keyword may be used with <{link}>. This keyword creates an <a>external resource link</a>. This keyword is <a>body-ok</a>. -The <{link/prerender}> keyword identifies a resource that might be required +The <{link/prerender}> keyword identifies a resource that might be required by the next navigation from the link context, and that the user agent ought - to fetch and execute, such that the user agent can deliver a faster + to fetch and execute, such that the user agent can deliver a faster response once the resource is requested in the future. See [[resource-hints]] for full definition. - + <h5 id="link-type-search">Link type "<dfn element-state for="link"><code>search</code></dfn>"</h5> diff --git a/sections/xhtml.include b/sections/xhtml.include index 70f8c69218..13edb0c3da 100644 --- a/sections/xhtml.include +++ b/sections/xhtml.include @@ -1,12 +1,17 @@ <section> + <!-- -██ ██ ██ ██ ██ ██████ ██ ██ ██ ██ ████████ ███ ██ ██ - ██ ██ ███ ███ ██ ██ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ - ██ ██ ████ ████ ██ ██ ████ ████ ██ ██ ██ ██ ██ ██ - ███ ██ ███ ██ ██ ██████ ██ ██ ██ ██ ██ ██ ██ ███ - ██ ██ ██ ██ ██ ██ ██ ██ ████ ██ █████████ ██ ██ - ██ ██ ██ ██ ██ ██ ██ ██ ██ ███ ██ ██ ██ ██ ██ -██ ██ ██ ██ ████████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ + + XML + + This source produces Chapter 9: The XML + https://w3c.github.io/html/xhtml.html + + It covers: + - Writing documents in the XML syntax + - Parsing XML documents + - Serializing and parsing XML + --> <h2 id="xhtml"><dfn>The XML syntax</dfn></h2>