Specification
Contents
Previous
Next
A
ElementThe first few tests below will switch between this document and another document, which is unstyled, testing the BASE element (12.4 below).
This anchor points to the named anchor below the PRE.
1 - This is the PRE used for spacing 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
Here is the target anchor which has the name, but not in quotes (since it is only alphanumeric characters, quotes are not required).
id
AttributeThis anchor points to the anchor with id below the PRE.
This anchor points to the paragraph with id below the PRE.
1 - This is the PRE used for spacing 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
Here is the target anchor which has the name, but not in quotes (since it is only alphanumeric characters, quotes are not required).
This anchor points to the anchor named with character references below the PRE.
1 - This is the PRE used for spacing 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
Here is the target anchor which has the name, but using different forms of the character references, inside quotes, but should evaluate to the same sequence.
Here is a thoroughly unavailable anchor .
LINK
ElementThis element defines a link. Unlike A, it may only appear in the HEAD section of a document, although it may appear any number of times. Although LINK has no content, it conveys relationship information that may be rendered by user agents in a variety of ways (e.g., a tool-bar with a drop-down menu of links).
In the header of this document are the following LINK
s:
<link href="chp13.html" rel=next rev=prev> <link href="chp11.html" rel=prev rev=next>
(These links are separate from the "Specification", "Contents", "Previous", and "Next" anchors
at the beginning of the BODY
element).
In the implied header of this document are the following linked stylesheets:
<link rel=stylesheet media=screen href="screen.css"> <link rel=stylesheet media=tv href="tv.css"> <link rel=stylesheet media=tty href="tty.css"> <link rel=stylesheet media=print href="print.css">
If this document is being viewed on a screen
, it should have yellow text on a
teal background. If this document is being viewed on a tv
, it should have lime text
on a navy background. If this document is being viewed on a tty
, it should have white
text on a black background. If this document is printed, it should have maroon text on a white
background. (all mentioned colors are styles for the explicit BODY
element. If this
document is viewed on any other medium, it will use the User Agent's default colors. If the
media
attribute is ignored, this document will be maroon on white, since all
stylesheets use equal specificity and that one was defined last.
In the header of this document is the following alternate link:
<link lang=es title="Un documento en español" rel=alternate hreflang=es href="spanish.html">
Ian Hickson's Evil Tests expect the User Agent to make this available to the user, but this
is not mandatory. According to the W3C documentation, many of these LINK
elements are
intended for search engines to handle, not User Agents. However, it wouldn't hurt if a User Agent
gives access to the alternate document.
BASE
ElementThis document has the following in the header:
<base href="/html401/base1.html">
and that document has in its header:
<base href="/html401/chp12.html">
Since this document and "base1.html" have each other specified in the "base" element, relative anchors (section 12.2 above) should reach the other document from either. All the elements that have a name or id appear in both documents.