diff --git a/sections/attributes.include b/sections/attributes.include index 3ecef73290..5807450d16 100644 --- a/sections/attributes.include +++ b/sections/attributes.include @@ -554,6 +554,14 @@
ping
placeholder
text/html
This registration is for community review and will be submitted to the IESG for review, + approval, and registration with IANA.
+ + + +charset
utf-8
". This parameter serves no purpose; it is only allowed for compatibility with legacy servers.text/ping
resources always consist of the four bytes 0x50 0x49 0x4E 0x47 (`PING
`).href
attribute and a
+ For <{link}> elements with an <{links/href}> attribute and a
<{link/rel}> attribute, links must be created for the keywords of the
<{link/rel}> attribute, as defined for those keywords in the link types section.
- Similarly, for <{a}> and <{area}> elements with an 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 link types section. Unlike <{link}> elements, however,
- <{a}> and <{area}> elements with an 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.
+ 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
+ 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.
This implied hyperlink has no special meaning (it has no link type)
beyond linking the element's node document to the resource given by the element's href
attribute.
- A hyperlink can have one or more hyperlink annotations that modify the processing semantics of that hyperlink.
+ A hyperlink can have one or more hyperlink annotations
+ that modify the processing semantics of that hyperlink.
download
attribute, and should be to download the
+ <{links/download}> attribute, and should be to download the
specified resource if it does.
Whether determined by the user's preferences or via the presence or absence of the attribute,
@@ -78,22 +76,22 @@
what punctuation is supported in file names, and user agents are likely to adjust file names
accordingly.
-
+
+ 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.
The rel
attribute on <{a}> and
<{area}> elements controls what kinds of links the elements create. The attribute's value
must be a set of space-separated tokens. The allowed keywords and their meanings are
defined below.
- <{links/rel}>'s
- supported tokens are the keywords defined in
- HTML link types which are allowed on <{a}> and
- <{area}> elements, impact the processing model, and are supported by the user agent. The
- possible supported tokens are
- <{link/noreferrer}>, and <{link/noopener}>.
- <{links/rel}>'s
- supported tokens must only include the tokens from
- this list that the user agent implements the processing model for.
+ <{links/rel}>'s supported tokens are the keywords defined in HTML link types which are allowed on
+ <{a}> and <{area}> elements, impact the processing model, and are supported by the user agent.
+ The possible supported tokens are <{link/noreferrer}>, and <{link/noopener}>.
+ <{links/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:
@@ -113,14 +111,14 @@
rev
attribute, which is used to describe
a reverse link relationship from the resource specified by the <{links/href}> to the
current document. If present, the value of this attribute must be a set of space-separated
- tokens. Like the <{links/rel}> attribute, [[#sec-link-types]] describes the allowed
+ tokens. Like the <{links/rel}> attribute, link types describes the allowed
keywords and their meanings for the <{links/rev}> attribute. Both the <{links/rel}> and
<{links/rev}> attributes may be present on the same element.
Reverse links are a way to express the reverse
directional relationship of a link. In contrast to the <{links/rel}> attribute, whose value
conveys a forward directional relationship ("how is the link related to me"), the <{links/rev}>
- attribute allows for similiar relationships to be expressed in the reverse direction ("how am I
+ attribute allows for similar relationships to be expressed in the reverse direction ("how am I
related to this link"). These values can enable user agents to build a more comprehensive map of
linked documents.
@@ -138,7 +136,7 @@
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
+ in the forward direction, and the "previous
" chapter in the reverse direction (from
chapter2.html to chapter1.html).
@@ -292,7 +290,7 @@
parsing them involves the StructuredSerialize
abstract operation.
- An element implementing the HTMLHyperlinkElementUtils
mixin has an associated reinitialise url algorithm, which runs these steps:
An element implementing the HTMLHyperlinkElementUtils
mixin has an associated reinitialize url algorithm, which runs these steps:
blob
", and its non-relative flag is set, terminate these steps.:
".The host
attribute's setter must run these steps:
The port
attribute's setter must run these steps:
The hash
attribute's setter must run these steps:
download
attribute, in
deciding where to store the resulting file in the user's file system.
+Thus, rel="next"
is the same as rel="NEXT"
.
So rel="next"
is the same as rel="NEXT"
.