diff --git a/sections/acknowledgements.include b/sections/acknowledgements.include index c9e3017956..91dbe6f4d1 100644 --- a/sections/acknowledgements.include +++ b/sections/acknowledgements.include @@ -72,6 +72,7 @@ Noel Gordon, Philippe Le Hégaret, + Richard Gibson, Richard Ishida, Ryosuke Niwa, Sailesh Panchang, diff --git a/sections/changes.include b/sections/changes.include index dc317489e1..3c61dd4700 100644 --- a/sections/changes.include +++ b/sections/changes.include @@ -7,7 +7,8 @@

Changes since the HTML 5.3 First Public Working Draft

- +
Add focusin and focusout events
+
Substantive change. Fixed issue 278
Add focusin and focusout events
Substantive change. Fixed issue 278
Allow fully internationalised email addresses in the <{input/E-mail}> type, as per [[RFC6531]].
diff --git a/sections/semantics-links.include b/sections/semantics-links.include index 8441df75db..f76dc910b9 100644 --- a/sections/semantics-links.include +++ b/sections/semantics-links.include @@ -1008,8 +1008,9 @@

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 - prefetch, preload, and <{link/stylesheet}>. Other specifications + 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. @@ -1052,7 +1053,15 @@ - + + + + + + + + + @@ -1116,7 +1125,15 @@ - + + + + + + + + + @@ -1124,13 +1141,21 @@ - + + + + + + + + + @@ -1328,7 +1353,22 @@ </body> ... - + Link type "dns-prefetch" + +The <{link/dns-prefetch}> keyword may be used with <{link}>.This keyword is body-ok. + +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. + + + + + The <{link/external}> keyword may be used with <{a}>, and <{area}> elements. + This keyword creates a hyperlink. The <{link/external}> keyword indicates that the referenced document is not part of the same site as the current document. It is informational, and requires no specific browser behaviour. @@ -1578,6 +1618,29 @@ behavior as <a href="..." rel="noreferrer noopener" target="_blank">.

+ + +The <{link/preconnect}> keyword may be used with <{link}>.This keyword is body-ok. + +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. + + + +The <{link/prefetch}> keyword may be used with <{link}>. This keyword creates an external resource link. +This keyword is body-ok. + +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 + resource is requested in the future. + +See [[resource-hints]] for full definition. + + The <{link/preload}> keyword may be used with <{link}>. This keyword creates an external resource link. This keyword is body-ok. @@ -1586,6 +1649,19 @@ There is no default type for resources given by the <{link/preload}> keyword. + + +The <{link/prerender}> keyword may be used with <{link}>. This keyword creates an external resource link. +This keyword is body-ok. + +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 + response once the resource is requested in the future. + +See [[resource-hints]] for full definition. + + The <{link/search}> keyword may be used with <{link}>,
external<{link/dns-prefetch}>not allowedhyperlink · Gives the origin for resources so the User Agent can resolve it as early as possible.
not allowed Annotation ·
prefetch<{link/preconnect}>External Resourcenot allowed Yes Specifies that the target resource should be preemptively cached and cache the target resource as it is likely to be required for a followup navigation.
<{link/prefetch}> External Resource not allowed Yes
preload<{link/prerender}> External Resource not allowed Yes Specifies that the user agent must preemptively fetch and cache the target resource for current navigation according to the potential destination given by the <{link/as}> attribute (and the priority associated with the corresponding destination).
<{link/prerender}>External Resourcenot allowed Yes Specifies that the target resource should be preemptively cached and cache the target resource as it is likely to be required for a followup navigation.
<{link/prev}> hyperlink