From 6af972213146525aaa122b139e8c1ce8f202f56f Mon Sep 17 00:00:00 2001 From: Anne van Kesteren Date: Wed, 26 Aug 2020 09:28:14 +0200 Subject: [PATCH] Clarify the link types process --- source | 22 +++++----------------- 1 file changed, 5 insertions(+), 17 deletions(-) diff --git a/source b/source index 7adfd8de387..b043d1d5cc9 100644 --- a/source +++ b/source @@ -22726,19 +22726,6 @@ document.body.appendChild(wbr); data-x="concept-supported-tokens">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:

- - -

The rel attribute has no default value. If the attribute is omitted or if none of the values in the attribute are recognized by the user agent, then the document has no particular relationship with the destination resource other than there @@ -23780,8 +23767,7 @@ document.body.appendChild(wbr); data-x="">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 + allowed in the body. The body-ok keywords are dns-prefetch, modulepreload, pingback, @@ -23789,8 +23775,10 @@ document.body.appendChild(wbr); prefetch, preload, prerender, and - stylesheet. - Other specifications can also define body-ok keywords.

+ stylesheet.

+ +

New link types that are to be implemented by web browsers are to be added to this standard. The + remainder can be registered as extensions.