Original Source can be found at Sandia National Laboratories
http://www.sandia.gov/sci_compute/elements.html
Last Modified: 7 December 1995
A, ABBREV, ACRONYM, ADDRESS, APP, APPLET, AREA, AU, B,
BANNER, BASE, BASEFONT, BDO, BGSOUND, BIG, BLINK, BLOCKQUOTE, BODY, BQ, BR,
CAPTION, CENTER, CITE, CODE, COL, COLGROUP, CREDIT, DD, DEL, DFN, DIR, DIV, DL, DT,
EM, EMBED, FN, FIG, FONT, FORM, FRAME, FRAMESET, H1, H2,
H3, H4, H5,
H6, HEAD, HP, HR,
HTML, I, IMG,
INPUT, INS, ISINDEX, KBD, LANG, LH, LI,
LINK, LISTING, MAP, MARQUEE, MENU, META, NEXTID, NOBR, NOEMBED, NOFRAMES, NOTE, OL, OPTION, OVERLAY, P, PARAM, PERSON, PLAINTEXT, PRE, Q, S,
SAMP, SELECT, SMALL, SPAN, STRIKE, STRONG, SUB, SUP, TAB, TABLE, TBODY, TD, TEXTAREA, TFOOT, TH, THEAD, TITLE, TR, TT,
U, UL, VAR, WBR, XMP
To shorten the lists in each element to describe the "Elements Allowed Within..." and "Allowed In Content Of..." various elements are defined by RFC 1866 as members of a group. These group names are used throughout the RFC 1866. Since group names can be defined to contain other group names, this mechanism makes nesting and recursion more obvious. Note that these element groups only deal with entities defined in RFC 1866 and do not include any of the entities in proposed extensions.
block block.forms, list, preformatted
and the entities DL
and P block
block.forms BLOCKQUOTE, FORM and ISINDEX body.content block, heading, text and the entities
HR and ADDRESS block, heading and the
entities HR, ADDRESS and IMG This recommended
change in the members of this group means that all text
within a body should be enclosed in some kind of block.
This means thatfont TT,
B and I heading H1,
H2, H3,
H4, H5
and H6
list UL,
OL, DIR
and MENU
DL which is identified
separately. phrase EM,
STRONG, CODE, SAMP, KBD,
VAR and CITE preformated PRE, XMP
and LISTING
PRE text phrase
and font
and the entities A, IMG and BR and parsed character
data. Parsed character data is any valid character data
after the data has been parsed and all special character
entities have been replaced with their character data.
The internationalization proposal also includes in group text
the entities BDO, Q, SPAN,
SUB, SUP
#name. This will load the document, but
will position the display starting at the location of
this NAME tag. An A element with an HREF attribute can
also be constructed to jump directly to this destination
tag within the same document by a URL consisting solely
of #name The presence of REL=relation
in document A with HREF to document/object B identifies a
relationship that B has to A that A
recognizes/authorizes/verifies. The presence of REV=relation
of the identical relation in document B with
HREF to document/object A identifies a
desired/expected/claimed relationship that B has to A,
but must be verified by checking with A. <A HREF="..." >characters...
</A><A NAME="..." >characters...
</A><A HREF="..." NAME="..."
REL="..." REV="..."
URN="..." TITLE="..."
METHODS="..." LANG="..." DIR=ltr|rtl
CHARSET="..." ID="..."
CLASS="..." MD="..."
TARGET="..."
SHAPE="...">characters... </A> heading
text but not
element <A>
text http://www.w3.org/hypertext/WWW/MarkUp/RegistrationAuthority.html,
but that link no longer responds. The entire topic of
link relationships is under active discussion and change.
Early examples of relationship names are UseIndex,
UseGlossary, Annotation, Reply, Embed, Precedes,
Subdocument, Present, Search, Supersedes, History, Made,
Owns, Approves, Supports, Refutes, Includes, Interested.
URN is for a Universal Resource Number, and is not
currently used or supported, and is a Level 1 attribute.
RFC 1866 describes it as a preferred, more persistent
identifier than the value of HREF. TITLE is little used
or supported, and is a Level 1 attribute, but is expected
to be the title of the HREF document. RFC 1866 suggests
TITLE can be displayed as a margin note or on a small box
while the mouse is over the anchor. (ed. I am
unaware of any browser that has implemented this
feature.) METHODS is little used or supported, but is
expected to be a white-space-separated list of HTTP
METHODS supported by the object and accessible to the
user. RFC 1866 suggests that the content of the A element
may be rendered differently depending upon the HTTP
method. TARGET is a Netscape 2.0 extension to define a
window name for use by the retrieved hyperlink. If the
named window is not already open, Netscape 2.0 will open
a new window and assign it that name. See also the FRAME element for naming a
window. SHAPE is proposed to provide a mechanism to
define multiple A elements and corresponding
"hotzones" within the proposed FIG element, to perform the
equivalent function of ISMAP without the need for writing
a responding cgi-bin program. For an alternate proposal,
see the MAP element. A is a
Level 0 element. <ABBREV>characters... </ABBREV> <ABBREV LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</ABBREV> -In progress, to be determined- -In progress, to be determined- <ACRONYM>characters... </ACRONYM>
<ACRONYM LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</ACRONYM> -In progress, to be determined- -In progress, to be determined- <ADDRESS>characters... </ADDRESS>
<ADDRESS LANG="..." DIR=ltr|rtl
ALIGN=center|left|right|justify ID="..."
CLASS="..."
CLEAR=left|right|all|"..."
NOWRAP>characters... </ADDRESS> text
or element <P>
body.content ALIGN=center|left|right|justify
The CLEAR and NOWRAP attributes are proposed in Version
3. ADDRESS is a Level 0 element. See the element APPLET
<APPLET CODE="..."
WIDTH="..."
HEIGHT="...">characters... </APPLET>
<APPLET CODE="..."
WIDTH="..." HEIGHT="..."
CODEBASE="..." ALT="..."
NAME="..."
ALIGN=left|right|top|texttop|middle|absmiddle|baseline|bottom|absbottom
VSPACE="..."
HSPACE="...">characters... </APPLET>
<PARAM>
and any other elements which would have been allowed at
this point in the document. -In progress, to be determined- <AREA COORDS="..."> <AREA COORDS="..."
SHAPE=rect|circle|polygon HREF="..." NOHREF
ALT="..."> <MAP> <AU>characters... </AU> <AU LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</AU> -In progress, to be determined- -In progress, to be determined- <B>characters... </B> <B LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</B> text
font <BANNER>characters... </BANNER> <BANNER LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</BANNER> -In progress, to be determined- <BODY> <BASE HREF="..."> <BASE HREF="..."
TARGET="..."> <HEAD> <BASEFONT SIZE=1|2|3|4|5|6|7> <BASEFONT SIZE=1|2|3|4|5|6|7> -In progress, to be determined- -In progress, to be determined- <BDO DIR=ltr|rtl>characters... </BDO>
<BDO DIR=ltr|rtl
LANG="...">characters... </BDO>
text
text <BGSOUND SRC="..."> <BGSOUND SRC="..."
LOOP="..."> -In progress, to be determined- <BIG>characters... </BIG> <BIG LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</BIG> -In progress, to be determined- -In progress, to be determined- <BLINK>characters... </BLINK> <BLINK>characters... </BLINK> -In progress, to be determined- -In progress, to be determined- <BLOCKQUOTE> </BLOCKQUOTE> <BLOCKQUOTE LANG="..." DIR=ltr|rtl
ALIGN=center|left|right|justify> </BLOCKQUOTE>
body.content
block.forms ALIGN=center|left|right|justify
Version 3 proposes replacing the BLOCKQUOTE element with
the BQ element. BLOCKQUOTE is
a Level 0 element. <BODY LANG="..." DIR=ltr|rtl
ID="..." CLASS="..."
BACKGROUND="..." BGCOLOR="..."
BGPROPERTIES=fixed TEXT="#rrggbb"
LINK="#rrggbb" VLINK="#rrggbb"
ALINK="#rrggbb"> </BODY> body.content
<HTML> Black, Maroon,
Green, Olive, Navy, Purple, Teal, Gray, Silver, Red,
Lime, Yellow, Blue, Fuchsia, Aqua, White. The
TEXT, LINK, VLINK, and ALINK attributes are Netscape 1.1
extensions, and also appear to work with MS Internet
Explorer 2.0. BGPROPERTIES is an MS Internet Explorer 2.0
extension and currently only accepts the value of
"fixed" which provides a watermark
(non-scrolling) background image. <BQ> </BQ> <BQ LANG="..." DIR=ltr|rtl
ID="..." CLASS="..."
CLEAR=left|right|all|"..." NOWRAP>
</BQ> <CREDIT>
-others to be determined- <BQ>
-others to be determined- <BR> <BR CLEAR=left|right|all|"..."
ID="..." CLASS="..."> text <CAPTION>characters... </CAPTION>
<CAPTION ALIGN=top|bottom|left|right
LANG="..." DIR=ltr|rtl ID="..."
CLASS="...">characters... </CAPTION>
-In progress, to be determined- <FIG> <TABLE> <CENTER>characters... </CENTER> <CENTER>characters... </CENTER> -In progress, to be determined- <A> -In progress,
to be determined- ALIGN="center"
proposed new attribute for all the text block elements
such as the <P> paragraph and <H?>
header elements and the new <DIV>
element. Both RFC 1866 and the current Version 3
specification only include the ALIGN attribute, not the
CENTER element, and Netscape 2.0 has added the ALIGN="center"
attribute. <CITE>characters... </CITE> <CITE LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</CITE> text
phrase <CODE>characters... </CODE> <CODE LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</CODE> text
phrase <COL> <COL LANG="..." DIR=ltr|rtl
ID="..." CLASS="..." SPAN=nn
WIDTH="..."
ALIGN=left|center|right|justify|char CHAR="."
CHAROFF="..."
VALIGN=top|middle|bottom|baseline> COLGROUP TABLE pt=points,
pi=picas, in=inches, cm=centimeters,
mm=millimeters, em=em units, px=screen
pixels. In addition, the special suffix of an asterisk
may be used to specify a number to be used as a
multiplier of a "standard" column width. This
is used to specify the widths of columns proportionately
relative to each other. If a number does not accompany
the asterisk it defaults to one. Specifying
WIDTH="0*" forces the column to its minimum
width. ALIGN and VALIGN define the alignment of text
within a table cell. If ALIGN=char, CHAR specifies the
alignment character which defaults to the decimal point
for the current language. CHAROFF is a decimal number
that specifies the offset for the alignment character
from the beginning of the table cell in the DIR
direction. Units may be specified using the standard
defined units suffixes plus the special suffix of the
percent sign indicating the percentage of offset within
the cell from the beginning of the cell. <COLGROUP> <COLGROUP LANG="..." DIR=ltr|rtl
ALIGN=left|center|right|justify|char ID="..."
CLASS="..." CHAR="."
CHAROFF="..."
VALIGN=top|middle|bottom|baseline>characters...
</COLGROUP> COL TABLE pt=points,
pi=picas, in=inches, cm=centimeters,
mm=millimeters, em=em units, px=screen
pixels. In addition, the special suffix of the percent
sign may be used to indicate the percentage of offset
within the cell from the beginning of the cell. <CREDIT>characters... </CREDIT> <CREDIT LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</CREDIT> -In progress, to be determined- <BQ> <FIG> <DD>characters... <DD LANG="..."
DIR=ltr|rtl>characters... </DD> block
text <DL> <DT> or another <DD>
or the </DL> element to end the list,
and thus do not require the ending tag. The LANG and DIR
attributes are introduced with the internationalization
proposal. All list elements are Level 0. <DEL>characters... </DEL> <DEL LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</DEL> -In progress, to be determined- -In progress, to be determined- <DFN>characters... </DFN> <DFN LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</DFN> -In progress, to be determined- -In progress, to be determined- <LI> elements. <DIR></DIR> <DIR COMPACT LANG="..." DIR=ltr|rtl
ALIGN=center|left|right|justify> </DIR> <LI>
but not any member of group block list <UL PLAIN
WRAP=HORIZ> is proposed in Version 3 as a
replacement for the DIR element. The exclusion in RFC
1866 of group block within DIR implies
(among other things) that DIR can contain no nested
lists, nor any paragraphs even though the LI element
normally would allow this. Some browsers do not enforce
this exclusion. The LANG and DIR attributes are
introduced with the internationalization proposal. The
internationalization proposal also includes ALIGN=center|left|right|justify
All list elements are Level 0. <DIV>characters... </DIV> <DIV LANG="..." DIR=ltr|rtl
ALIGN=left|center|right|justify ID="..."
CLASS="..." NOWRAP
CLEAR=left|right|all|"...">characters...
</DIV> -In progress, to be determined- <BODY> <DIV
ALIGN=center> is the proposed replacement for
the non-standard CENTER
element. This is a Netscape 2.0 extension but it only
recognizes ALIGN=left|right|center. <DT> and <DD>
elements. <DL></DL> <DL COMPACT LANG="..." DIR=ltr|rtl
ID="..." CLASS="..."
CLEAR=left|right|all|"..."> </DL>
<LH> <DT> <DD> block <DT>characters... <DT LANG="..."
DIR=ltr|rtl>characters... </DT> text
<DL> <DD>
or another <DT> or the </DL>
element to end the list, and thus do not require the
ending tag. The LANG and DIR attributes are introduced
with the internationalization proposal. All list elements
are Level 0. <EM>characters... </EM> <EM LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</EM> text
phrase <EMBED SRC="..."> <EMBED SRC="..."
HEIGHT="..." WIDTH="..."
attribute_1="..." attribute_2="..."
...>characters... </EMBED> <NOEMBED>
-In progress, to be determined- <FIG SRC="..."></FIG> <FIG SRC="..." LANG="..."
DIR=ltr|rtl ID="..." CLASS="..."
CLEAR=left|right|all|"..." NOFLOW
MD="..."
ALIGN=left|right|center|justify|bleedleft|bleedright
WIDTH=value HEIGHT=value UNITS="..."
IMAGEMAP="..."></FIG> <OVERLAY> <CAPTION> <CREDIT>
-In progress, to be determined- (ed: all
normal markup elements?) -In progress, to be determined- <FN ID="...">characters...
</FN> <FN LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</FN> -In progress, to be determined- -In progress, to be determined- <FONT SIZE=[+|-]1|2|3|4|5|6|7> <FONT SIZE=[+|-]1|2|3|4|5|6|7
COLOR="..." FACE="..."> -In progress, to be determined- -In progress, to be determined-
Black, Maroon, Green, Olive, Navy, Purple, Teal, Gray,
Silver, Red, Lime, Yellow, Blue, Fuchsia, Aqua, White.
The FACE attribute is a MS Internet Explorer 2.0
extension to specify a font style, but the permitted
values are not defined. QUERY_STRING. METHOD=POST (the
preferred) sends the input information in a data body
which is available on stdin with the data
length set in the environment variable CONTENT_LENGTH.
Form data is a stream of name=value pairs
separated by the & character. Each
name=value pair is URL encoded, i.e. spaces are changed
into the plus character and some characters are encoded
into hexadecimal. At least one of the following is
expected inside the FORM contents: INPUT, SELECT,
TEXTAREA. <FORM></FORM> <FORM ACTION="..." METHOD=GET|POST
ENCTYPE="..." LANG="..." DIR=ltr|rtl
ACCEPT-CHARSET="..." SCRIPT="...">
</FORM> body.content
and elements <INPUT>
<SELECT> <TEXTAREA>
but not element <FORM>
block.forms application/x-www-form-urlencoded
for the ENCTYPE attribute. RFC 1867 adds the value of multipart/form-data
for this attribute to permit a FORM to upload one or more
files in addition to the FORM data. METHOD=POST is
required with this value of ENCTYPE. This file upload
extension is implemented in Netscape 2.0. Most current
browsers only handle ACTION for the http:
access type, but proposals for handling the mailto:
access type are being discussed. The LANG, DIR, and
ACCEPT-CHARSET attributes are introduced with the
internationalization proposal. The ACCEPT-CHARSET
attribute is to provide a hint as to the character set or
sets that the receiving URL is prepared to handle.
Version 3 proposes the SCRIPT attribute to specify a URL
which contains a limited syntax script to be downloaded
to the browser for execution to preprocess the FORM
output before sending it to the ACTION destination. This
SCRIPT proposal may change as part of the new proposals
concerning APPLET and EMBED. All elements concerning FORM
are Level 2. <FRAME> <FRAME SRC="..." NAME="..."
MARGINWIDTH="..." MARGINHEIGHT="..."
SCROLLING=yes|no|auto NORESIZE> <FRAMESET>
_blank, _self, _parent, _top.
These values must begin with the underbar character and
have the following respective meanings: new unnamed
window, load in the same window, load in the parent
window (if none use self), load in the top window (if
none use self). Netscape 2.0 defines the units for
MARGINWIDTH and MARGINHEIGHT as pixels. <FRAMESET>characters... </FRAMESET>
<FRAMESET ROWS="..."
COLS="...">characters... </FRAMESET>
<FRAME> <FRAMESET> <NOFRAMES> <HTML>
<H1>characters... </H1> <H1 LANG="..." DIR=ltr|rtl
ALIGN=left|center|right|justify ID="..."
CLASS="..."
CLEAR=left|right|all|"..." SEQNUM=nnn SKIP=nnn
DINGBAT=entity-name SRC="..."
MD="..." NOWRAP>characters... </H1>
text
heading ALIGN=center|left|right|justify
Netscape 2.0 implements ALIGN=center|left|right
The ID attribute was proposed in HTML+ and Version 3 to
replace the NAME attribute in the A element to establish
internal hyperlink destinations. With the expected use of
ID for style sheets, this is likely to change. All other
attributes are proposed in Version 3. RFC 1866 states
typical rendering is bold, very large font, centered;
when printed causes a page break. Headings are Level 0
elements. <H2>characters... </H2> <H2 LANG="..." DIR=ltr|rtl
ID="..." CLASS="..."
ALIGN=left|center|right|justify
CLEAR=left|right|all|"..." SEQNUM=nnn SKIP=nnn
DINGBAT=entity-name SRC="..."
MD="..." NOWRAP>characters... </H2>
text
heading ALIGN=center|left|right|justify
Netscape 2.0 implements ALIGN=center|left|right
The ID attribute was proposed in HTML+ and Version 3 to
replace the NAME attribute in the A element to establish
internal hyperlink destinations. With the expected use of
ID for style sheets, this is likely to change. All other
attributes are proposed in Version 3. RFC 1866 states
typical rendering is bold, large font, flush left.
Headings are Level 0 elements. <H3>characters... </H3> <H3 LANG="..." DIR=ltr|rtl
ALIGN=left|center|right|justify ID="..."
CLASS="..."
CLEAR=left|right|all|"..." SEQNUM=nnn SKIP=nnn
DINGBAT=entity-name SRC="..."
MD="..." NOWRAP>characters... </H3>
text
heading ALIGN=center|left|right|justify
Netscape 2.0 implements ALIGN=center|left|right
The ID attribute was proposed in HTML+ and Version 3 to
replace the NAME attribute in the A element to establish
internal hyperlink destinations. With the expected use of
ID for style sheets, this is likely to change. All other
attributes are proposed in Version 3. RFC 1866 states
typical rendering is italic, large font, slightly
indented. Headings are Level 0 elements. <H4>characters... </H4> <H4 LANG="..." DIR=ltr|rtl
ALIGN=left|center|right|justify ID="..."
CLASS="..."
CLEAR=left|right|all|"..." SEQNUM=nnn SKIP=nnn
DINGBAT=entity-name SRC="..."
MD="..." NOWRAP>characters... </H4>
text
heading ALIGN=center|left|right|justify
Netscape 2.0 implements ALIGN=center|left|right
The ID attribute was proposed in HTML+ and Version 3 to
replace the NAME attribute in the A element to establish
internal hyperlink destinations. With the expected use of
ID for style sheets, this is likely to change. All other
attributes are proposed in Version 3. RFC 1866 states
typical rendering is bold, normal font, indented more
than H3. Headings are Level 0 elements. <H5>characters... </H5> <H5 LANG="..." DIR=ltr|rtl
ALIGN=left|center|right|justify ID="..."
CLASS="..."
CLEAR=left|right|all|"..." SEQNUM=nnn SKIP=nnn
DINGBAT=entity-name SRC="..."
MD="..." NOWRAP>characters... </H5>
text
heading ALIGN=center|left|right|justify
Netscape 2.0 implements ALIGN=center|left|right
The ID attribute was proposed in HTML+ and Version 3 to
replace the NAME attribute in the A element to establish
internal hyperlink destinations. With the expected use of
ID for style sheets, this is likely to change. All other
attributes are proposed in Version 3. By default,
Netscape uses a font size for H5 that is smaller than
default text. For most other browsers, the font size for
all headers is at least as large as the default text. RFC
1866 states typical rendering is italic, normal font,
indented as H4. Headings are Level 0 elements. <H6>characters... </H6> <H6 LANG="..." DIR=ltr|rtl
ALIGN=left|center|right|justify ID="..."
CLASS="..."
CLEAR=left|right|all|"..." SEQNUM=nnn SKIP=nnn
DINGBAT=entity-name SRC="..."
MD="..." NOWRAP>characters... </H6>
text
heading ALIGN=center|left|right|justify
Netscape 2.0 implements ALIGN=center|left|right
The ID attribute was proposed in HTML+ and Version 3 to
replace the NAME attribute in the A element to establish
internal hyperlink destinations. With the expected use of
ID for style sheets, this is likely to change. All other
attributes are proposed in Version 3. By default,
Netscape uses a font size for H6 that is smaller than
default text. For most other browsers, the font size for
all headers is at least as large as the default text. RFC
1866 states typical rendering is bold, normal font, not
indented. Headings are Level 0 elements. <HEAD LANG="..." DIR=ltr|rtl>
</HEAD> <TITLE> <ISINDEX> <BASE> <META> <LINK> <NEXTID> <HTML> <HPn>characters... </HPn> <HPn>characters... </HPn> <HR> <HR DIR=ltr|rtl ALIGN=left|right|center|justify
ID="..." CLASS="..."
CLEAR=left|right|all|"..." SRC="..."
MD="..." SIZE=number WIDTH=number|percent
NOSHADE> body.content ALIGN=center|left|right|justify
The CLEAR, SRC, and MD attributes are proposed in Version
3. SRC is proposed to specify a custom image for the
rule. Some browsers draw the line only within the current
text margins (which may be indented on left and/or right
due to lists, etc.) SIZE, WIDTH, ALIGN, and NOSHADE
attributes are Netscape extensions, but Netscape 2.0 only
implements ALIGN=center|left|right The HR
element is Level 0. <HTML VERSION="..."
LANG="..." DIR=ltr|rtl> </HTML>
<HEAD> <BODY> <PLAINTEXT>
<I>characters... </I> <I LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</I> text
font <IMG SRC="..."> <IMG SRC="..." ALT="..."
ISMAP LANG="..." DIR=lrt|rtl ID="..."
CLASS="..." MD="..."
ALIGN=bottom|middle|top|left|right|texttop|absmiddle|baseline|absbottom
HEIGHT=value WIDTH=value UNITS="..."
BORDER=value LOWSRC="..." HSPACE=value
VSPACE=value USEMAP="..."
DYNSRC="..." START=fileopen|mouseover CONTROLS
LOOP=number|INFINITE|-1 LOOPDELAY=number> text bottom|middle|top
as values for the ALIGN attribute. The additional values
for the ALIGN attribute are Netscape extensions, and
include the capability to define floating images. Version
3 proposes adding only the (left|right)
values for ALIGN to identify images that imply that text
can float around the image. Some image capable browsers
will display the ALT text until the full image is
retrieved. RFC 1866 states that Level 0 conformance must
accept the element, but Level 1 conformance is required
before it displays the image. Version 3 proposes the
UNITS attribute for use by the WIDTH and HEIGHT
attributes to define units other than pixels. RFC 1866
states that an IMG element with an ISMAP element must
only exist in the content of an A element with an HREF
attribute. Version 3 proposes a FIG
element as an advanced alternative to the IMG element,
for more sophisticated multi-part overlay images, more
control over text that is the equivalent of ALT, and with
a proposed SHAPE attribute on the A element a method to
perform the common use of the ISMAP attribute without the
need for a responding cgi-bin program. The USEMAP is part
of an alternate proposal for client-side image mapes. It
is implemented as a Netscape 2.0 extension. USEMAP
specifies a URL with a "#NAME" suffix to
identify a file and MAP name, and is used with the MAP
element. DYNSRC is defined by MS Internet Explorer 2.0 as
the address of a video clip or VRML world to be displayed
if your browser is capable, otherwise display SRC. START
is defined by MS Internet Explorer 2.0 as when the
videoclip or VRML world is to be displayed. If START=mouseover,
the SRC image is displayed until the mouse cursor is over
that image. CONTROLS is defined by MS Internet Explorer
2.0 as displaying a set of controls under the animation.
LOOP is defined by MS Internet Explorer 2.0 as how many
times a video clip will loop when activated. If LOOP=-1
or LOOP=INFINITE, it will loop indefinately.
LOOPDELAY is defined by MS Internet Explorer 2.0 as how
long, in milliseconds, a video clip will wait between
replays. TYPE=text
is default. NAME defines the symbolic name
of the field returned to the server on submission and
must be present for all but TYPE=submit|reset.
For TYPE=checkbox|radio, multiple INPUT
elements may have the same NAME value. TYPE=radio
insures that exactly one choice amongst INPUT elements
with the same NAME value is selected at all times. VALUE
is used to specify a default. For TYPE=text|password
VALUE defines default text to be returned, which normally
is null. For TYPE=password the value should
be obscured as it is entered. For TYPE=checkbox|radio
VALUE defines the value returned when the checkbox or
radio is selected, which defaults to "on" For TYPE=submit|reset
VALUE defines the label for the pushbutton. Multiple TYPE=submit
should have different NAME values to identify which
submission button was selected. CHECKED
defaults the specific checkbox or radio INPUT to
selected. For TYPE=radio the default element
checked is the first among those with the same NAME
value. TYPE=image defines an image, whose URLis identified by the SRC
attribute, which, when clicked, performs the form
submission and sends the X,Y coordinates of the click,
similar to ISMAP in the IMG element. SIZE
and MAXLENGTH are only used with TYPE=text|password.
SIZE is the physical size of the displayed
input field expressed in characters or characters,rows. MAXLENGTH
is the maximum number of characters that are accepted as
input. <INPUT> <INPUT TYPE="text | password | checkbox |
radio | submit | reset | hidden | image | file | range |
scribble | jot" LANG="..." DIR=ltr|rtl
ID="..." CLASS="..."
NAME="..." VALUE="..."
SRC="..." CHECKED SIZE="..."
MAXLENGTH=number ALIGN=top|middle|bottom|left|right
ACCEPT="..." DISABLED ERROR="..."
MIN=number MAX=number MD="..."> <FORM> text|password|checkbox|radio|submit|reset|hidden|image
The <TEXTAREA>
element should be used instead of this INPUT element for
multiline input areas. TYPE=hidden
VALUE="..." is recognized by some
browsers, and is used to submit fixed information not
entered by the user. Note that RFC 1866 sets a max limit
of 1024 characters on VALUE. RFC 1866 only defines ALIGN=top|middle|bottom
RFC 1867 defines a mechanism for FORM-based file
upload. It defines the value file for the
TYPE attribute and defines a new ACCEPT attribute.
Specifying TYPE=file permits attaching one
or more local files to the submitted output. The browser
may permit the user to specify multiple file names in
response to a single INPUT element with TYPE=file
ACCEPT is a list of media types or type patterns allowed
for input. The valid ACCEPT values and meaning of those
values is platform dependent. The value for the VALUE
attribute specifies a default file name. The browser must
ask for confirmation before sending any file based on the
default file name. A value for the SIZE attribute of
"width,height" would specify a
default filename width for the input display and height
sufficient to show some number of files. A value for the
MAXLENGTH attribute specifies a maximum Content-Length
(in bytes) which the responding server is likely to
accept for transferred files. Including an INPUT element
with TYPE=file requires also specifying ENCTYPE="multipart/form-data"
METHOD=post on the enclosing FORM element. If the
FORM does not specify this ENCTYPE, the behavior is
unspecified and the file transfer is likely to be
rejected by the responding server. Netscape 2.0
implements FORM-based file upload.
The LANG and DIR attributes are introduced with the
internationalization proposal. Version 3 proposes the
additional TYPE attribute values of range|scribble.
A beta version of Netscape includes a TYPE attribute
value of jot which is similar to scribble.
Version 3 proposes the additional DISABLED, ERROR, MIN,
MAX, and MD attributes. The Version 3 proposed TYPE=range
uses the proposed MIN and MAX attributes to specify
limits to numeric (real or integer) input. The proposed
default value is halfway between MIN and MAX. The Version
3 proposed TYPE=scribble is to allow the
user to scribble with a pointing device on top of the
image specified with the SRC attribute. The Version 3
proposed DISABLED attribute would display this INPUT, but
prohibit user entry/modification. The Version 3 proposed
ERROR attribute defines text to be displayed in the event
that the entered value for this INPUT is invalid. All
elements concerning FORM are Level 2.
<INS>characters... </INS> <INS LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</INS> -In progress, to be determined- -In progress, to be determined- <FORM>
element which has more features. When placed in the BODY
of the document, it requires the ACTION attribute to
point to a cgi-bin program which can handle the query,
and produces a simple INPUT field with a prompt of:
"This is a searchable index. Enter search
keywords:" When placed in the HEAD of the
document, it informs the browser that the document is an
index document and can be examined using a keyword
search. The ISINDEX element is usually generated
automatically by a server-side script. <ISINDEX> <ISINDEX LANG="..." DIR=ltr|rtl
ACTION="..." PROMPT="..."> <HEAD>
and any element that permits members of the group block.forms <KBD>characters... </KBD> <KBD LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</KBD> text
phrase <LANG>characters... </LANG> <LANG ID="..."
CLASS="...">characters... </LANG>
-In progress, to be determined- -In progress, to be determined- <LH>characters... </LH> <LH LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</LH> -In progress, to be determined- <DL> <OL> <UL> <LI>characters... <LI LANG="..." DIR=ltr|rtl
ALIGN=center|left|right|justify within UL
TYPE=disk|circle|square within OL
TYPE=A|a|I|i|i within OL
VALUE=n>characters...</LI> text
block <DIR> <MENU> <OL> <UL> ALIGN=center|left|right|justify
The TYPE and VALUE attributes are Netscape extensions.
The validity of their presence and possible values
depends on the particular list entity of which this is a
list item. Most browsers assume the list item ends with
the beginning of the next list item or the end of the
list and do not require the closing tag </LI>
All list elements are Level 0. REL=relation
identifies a relationship that B has to A that A
recognizes/authorizes/verifies. A LINK in document B with
an HREF to document/object A with REV=relation
that is the identical relation identifies a
desired/expected/claimed relationship of B to
document/object A, but must be verified by checking with
A. For further description of the LINK attributes, see
the A element. <LINK HREF="..." > <LINK HREF="..." REL="..."
REV="..." LANG="..." DIR=ltr|rtl
CHARSET="..." URN="..."
TITLE="..." METHODS="..." >
<HEAD> Home, ToC, Index, Glossary, Copyright, Up,
Next, Previous, Help, Bookmark. Version 3 also
discusses relations for a document banner and style
sheets. LINK is a Level 0 element. <LINK REV="owns" TITLE="Full
Name"
HREF="mailto:owner-e-mail@sandia.gov">
LINK elements are also recommended to identify other
individuals and their relationships to this document. The
REV value of made should be used to identify
the author of the document. Suggested values for REV in
additional LINK elements are: approves, editor,
publisher.
Large documents which are separated into smaller HTML
subdocuments should use the LINK element with the REL
attribute to identify these relationships. The parent
document should identify all subdocuments by:
<LINK REL="Subdocument"
TITLE="Subdoc Name"
HREF="link-url">
The subdocument may identify its parent by:
<LINK REV="Subdocument"
TITLE="Maindoc Name"
HREF="link-url">
Any Sandia document which is part of a set of HTML
subdocuments which form a sequence or hierarchy should
include two specific LINK elements identifying the REL
values of next and previous.
Only one next and one previous
relationship may be specified in a document.
Any of the other document relationships mentioned in this Reference Manual may also be used.
<LISTING>characters... </LISTING>
<LISTING WIDTH="..." >characters...
</LISTING> block <PRE> element. RFC
1866 states that the content of the LISTING element
should be rendered so that at least 132 characters fit on
a line. RFC 1866 has declared LISTING as deprecated and
some current browsers no longer recognize it. <MAP NAME="..."></MAP>
<MAP NAME="..."></MAP>
<AREA>
-In progress, to be determined- <MARQUEE>characters... </MARQUEE>
<MARQUEE ALIGN=top|middle|bottom
BEHAVIOR=scroll|slide|alternate BGCOLOR=#rrggbb|colorname
DIRECTION=left|right HEIGHT=number|number% HSPACE=number
LOOP=number|INFINITE|-1 SCROLLAMOUNT=number
SCROLLDELAY=number VSPACE=number>characters...
</MARQUEE> -In progress, to be determined- -In progress, to be determined- scroll
completely in and completely off (the default), slide
in and stay, or bounce between alternate
sides of the marquee. The BGCOLOR attribute defines the
background color for the marquee, which is specified as
an "#rrggbb" number, or the following color
names: Black, Maroon, Green, Olive, Navy, Purple,
Teal, Gray, Silver, Red, Lime, Yellow, Blue, Fuchsia,
Aqua, White. The DIRECTION attribute specifies the
direction towards which the text should flow. The HEIGHT
attribute specifies the height of the marquee, either in
pixels or with a percentsign character suffix to define a
percentage of the entire screen height. The HSPACE and
VSPACE attributes are specified in pixels and define the
amount to separate the marquee from surrounding text. The
LOOP attribute specifies how many times the text will
loop. If LOOP=-1 or LOOP=INFINITE,
the text will loop indefinately. The SCROLLAMOUNT
specifies the number of pixels and the SCROLLDELAY
specifies the number of milliseconds between each
successive draw of the marquee text. <LI>
elements which may or may not be marked by a bullet or
similar symbol. <MENU></MENU> <MENU COMPACT LANG="..." DIR=ltr|rtl
ALIGN=center|left|right|justify> </MENU> <LI>
but not any member of group block list block
within MENU implies (among other things) that MENU can
contain no nested lists, nor any paragraphs even though
the LI element normally would allow this. Some browsers
do not enforce this exclusion. The LANG and DIR
attributes are introduced with the internationalization
proposal. The internationalization proposal also includes
ALIGN=center|left|right|justify By adding
the PLAIN attribute to eliminate the bullets to the UL element, Version 3 proposes
to remove the MENU element. All list elements are Level
0. <META CONTENT="..." > <META HTTP-EQUIV="..."
NAME="..." CONTENT="..."
URL="..." > <HEAD> "REFRESH", the
CONTENT attribute to a number of seconds, and the URL
attribute to the file to load which defaults to reloading
the same file. Netscape 1.1 also recognizes placing the
URL inside the quotes which define the CONTENT value by
using a semicolon following the number of seconds, then
the URL=http://... text. <META NAME="REVIEW" CONTENT="DD
MMM YYYY"><META HTTP-EQUIV="KEYWORDS"
CONTENT="key1, key2, key3">N= provides the next
available identifier for use by automatic hypertext
editors. If the NEXTID element is manually entered, it
should be alphabetical to avoid conflict with such
editors. <NEXTID N="..." > <NEXTID N="..." > <HEAD> NOBR
elements cannot have line breaks inserted between them. <NOBR>characters... </NOBR> <NOBR>characters... </NOBR> -In progress, to be determined- -In progress, to be determined- <NOEMBED>characters... </NOEMBED>
<NOEMBED>characters... </NOEMBED>
-In progress, to be determined- <EMBED>
<NOFRAMES>characters... </NOFRAMES>
<NOFRAMES>characters... </NOFRAMES>
-In progress, to be determined- <FRAMESET>
body.content
in the content of the NOFRAMES element. <NOTE>characters... </NOTE> <NOTE LANG="..." DIR=ltr|rtl
ID="..." CLASS="..."
CLEAR=left|right|all|"..." SRC="..."
MD="..."</NOTE> -In progress, to be determined- -In progress, to be determined- <LI>
elements, and ordered numerically in some way. <OL></OL> <OL COMPACT LANG="..." DIR=ltr|rtl
ALIGN=center|left|right|justify ID="..."
CLASS="..."
CLEAR=left|right|all|"..." CONTINUE
SEQNUM=value START=value TYPE=A|a|I|i|1></OL>
<LH> <LI> list ALIGN=center|left|right|justify
Version 3 proposes the CLEAR attribute. The CONTINUE
attribute is proposed by Version 3 to continue the
numbering from where the previous OL list left off. The
SEQNUM attribute is proposed by Version 3 to define a
starting number for the list. START is a Netscape
extension to do the same thing as SEQNUM. The TYPE
attribute is a Netscape extension. Version 3 proposes
using associated style sheets and the CLASS attribute to
handle these, and other, options to numbering style. All
list elements are Level 0. <OPTION>characters... <OPTION SELECTED VALUE="..."
LANG="..." DIR=ltr|rtl ID="..."
CLASS="..." DISABLED ERROR="..."
SHAPE="..." >characters... </OPTION>
<SELECT>
"default", "circle
x,y,r", "rect x,y,w,h",
and "polygon x1,y1,x2,y2,...". All
elements concerning FORM are Level 2. <OVERLAY SRC="..."> <OVERLAY SRC="..." MD="..."
UNITS=pixels|en X=value Y=value WIDTH=value HEIGHT=value
IMAGEMAP="..."> <FIG> <P>characters... <P ALIGN=center|left|right|justify|indent
WRAP=on|off NOWRAP CLEAR=left|right|all|"..."
LANG="..." DIR=ltr|rtl ID="..."
CLASS="...">characters... </P> text
block <P> element was a
separator and the </P> element was not
defined. RFC 1866 changed the concept to a container and
introduced the optional </P> element.
The LANG and DIR attributes are introduced with the
internationalization proposal. HTML+ introduced the ALIGN
attribute and is the only proposal to mention the indent
value. The internationalization proposal includes ALIGN=center|left|right|justify
Netscape 2.0 implements ALIGN=center|left|right
and MS Internet Explorer 2.0 implements ALIGN=center|left|right|justify
Version 3 does not currently include indent
as an option for ALIGN. The CLEAR attribute is proposed
in Version 3 to deal with text able to float around an
image defined with the IMG element. HTML+ introduced the ID
attribute to replace the NAME attribute in the A element
to establish internal hyperlink destinations. With the
expected use of ID for style sheets, this is likely to
change. HTML+ proposed WRAP to turn off automatic word
wrap, making it possible to leave text as it appears in
the source. Version 3 replaces the WRAP attribute and
values with the NOWRAP attribute. The P element is Level
0. getParameter()
method. <PARAM NAME="..."
VALUE="..."> <PARAM NAME="..."
VALUE="..."> <APPLET>
<PERSON>characters... </PERSON> <PERSON LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</PERSON> -In progress, to be determined- -In progress, to be determined- <PLAINTEXT>characters... </PLAINTEXT>
<PLAINTEXT WIDTH="..."
LANG="..." DIR=ltr|rtl>characters...
</PLAINTEXT> <HTML>
<PRE>
element. RFC 1866 has declared PLAINTEXT as deprecated
and some current browsers no longer recognize it. The
LANG and DIR attributes are introduced with the
internationalization proposal. <PRE>characters... </PRE> <PRE WIDTH=number LANG="..."
DIR=ltr|rtl ID="..." CLASS="..."
CLEAR=left|right|all|"..." >characters...
</PRE> <A> <HR> <BR> and parsed
character data block <Q>characters... </Q> <Q LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</Q> text
text <S>characters... </S> <S LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</S> -In progress, to be determined- -In progress, to be determined- <SAMP>characters... </SAMP> <SAMP LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</SAMP> text
phrase <SELECT NAME="...">characters...
</SELECT> <SELECT NAME="..." SIZE=value MULTIPLE
LANG="..." DIR=ltr|rtl ID="..."
CLASS="..." ALIGN=top|middle|bottom|left|right
DISABLED ERROR="..." SRC="..."
MD="..." WIDTH=value HEIGHT=value
UNITS=pixels|em>characters... </SELECT> <OPTION>
Note that the elements <INPUT> <SELECT> <TEXTAREA>
are expressly prohibited by RFC 1866 from being nested
within the SELECT element content <FORM> <SMALL>characters... </SMALL> <SMALL LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</SMALL> -In progress, to be determined- -In progress, to be determined- <SPAN>characters... </SPAN> <SPAN LANG="..."
DIR=ltr|rtl>characters... </SPAN> text
text <STRIKE>characters... </STRIKE> <STRIKE>characters... </STRIKE> -In progress, to be determined- -In progress, to be determined- <STRONG>characters... </STRONG> <STRONG LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</STRONG> text
phrase <SUB>characters... </SUB> <SUB LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</SUB> text <SUP>characters... </SUP> <SUP LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</SUP> text <TAB>characters... <TAB ID="..." INDENT=ens
TO="..." ALIGN=left|center|right|decimal
DP="...">characters... -In progress, to be determined- -In progress, to be determined- <TABLE></TABLE> <TABLE LANG="..." DIR=ltr|rtl
ID="..." CLASS="..."
ALIGN=left|right|center|justify|bleedleft|bleedright
WIDTH="..." COLS=number BORDER="..."
FRAME=void|above|below|hsides|lhs|rhs|vsides|box|border
RULES=none|basic|rows|cols|all
CELLSPACING="..." CELLPADDING="..."
CLEAR=left|right|all|"..." NOFLOW
UNITS=en|relative|pixels COLSPEC="..."
DP="..." NOWRAP></TABLE> <CAPTION> <COL> <COLGROUP> <THEAD> <TFOOT> <TBODY> <TR> block
The ALIGN attribute specifies the table position relative
to the window. The WIDTH attribute specifies the entire
table width, and defaults to 100%. The default units is
pixels, but may be specified by a suffix on the number.
The standard defined units suffixes include: pt=points,
pi=picas, in=inches, cm=centimeters,
mm=millimeters, em=em units, px=screen
pixels. In addition the suffix of a percentsign may be
used to specify the percentage width of the space between
the current left and right margins. The COLS attribute
specifies the total number of columns in the table and
aids the browser in determining the initial display and
layout of the table. The BORDER attribute controls frame
width around the table and FRAME defines which parts of
the frame to include. For BORDER, the default units is
pixels, but may be specified by one of the standard
defined units suffixes. BORDER=0 implies FRAME=none, and
BORDER without a value implies FRAME=border. The RULES
attribute defines the presence or absence of rulings
between all rows and columns in this table. The
CELLSPACING attribute defines spacing between cells and
CELLPADDING defines spacing within cells.
The TABLE element has been partially implemented in
Netscape 1.1 and MS Internet Explorer 2.0. The COL,
COLGROUP, THEAD, and TFOOT elements are new and not yet
implemented. The FRAME and RULES attributes are new and
not yet implemented. The values justify|bleedleft|bleedright
for the ALIGN attribute are Netscape 1.1 extensions. The
attribute COLSPEC was from an earlier version of the
proposal and is replaced by the COL and COLGROUP
elements. The attribute DP is from an earlier version of
the proposal and was used with a value of decimal
on the ALIGN attribute. It has been replaced with the
CHAR and CHAROFF attributes used when ALIGN=char
which are defined for all table grouping elements except
TABLE. The attributes CLEAR, NOFLOW, UNITS, and NOWRAP
are Netscape 1.1 extensions. Netscape 1.1 defines WIDTH
as having a value of either a number of pixels or a
number followed by a percentsign to define a desired
width of the table which may be overridden by the
browser. It defines percentsign to specify the percentage
of the entire window, instead of the current margins.
<TBODY> <TBODY LANG="..." DIR=ltr|rtl
ID="..." CLASS="..."
ALIGN=left|right|center|justify|char CHAR="..."
CHAROFF="..."
VALIGN=top|middle|bottom|baseline>characters...</TBODY>
TR TABLE
The table proposal states that a browser may display ALIGN=justify
the same as the default ALIGN=left if it
lacks support for text justification. The CHAR and
CHAROFF attributes are used when ALIGN=char.
CHAR specifies a single character to be used for
alignment, and defaults to the decimal point in the
current language. CHAROFF specifies the offset, in the
DIR direction, to the first occurrence of the CHAR
character on each line. If a line doesn't include the
CHAR character, it is to end at the CHAROFF position. The
default value for CHAROFF is either 50% or whatever will
cause the CHAR characters in all cells with a declared
CHAR in a column to align. The default units is pixels,
but may be specified by a suffix on the number. The
standard defined units suffixes include: pt=points,
pi=picas, in=inches, cm=centimeters,
mm=millimeters, em=em units, px=screen
pixels. In addition the suffix of a percentsign may be
used to specify the percentage offset within the cell.
The VALIGN attribute defines the vertical alignment of
the cell contents. The ALIGN, CHAR and CHAROFF attribute
values may be inherited from other table elements in the
following order: cells < columns < column groups
< rows < row groups < default. The VALIGN, LANG
and DIR attribute values may be inherited from other
table elements in the following order: cells < rows
< row groups < columns < column groups <
table < default.
<TD> <TD LANG="..." DIR=ltr|rtl
ID="..." CLASS="..."
AXIS="..." AXES="..." NOWRAP
ROWSPAN=value COLSPAN=value
ALIGN=left|right|center|justify|char|decimal
CHAR="..." CHAROFF="..."
DP="..." VALIGN=top|middle|bottom|baseline
WIDTH=value
BGCOLOR="...">characters...</TD>
body.content
TR The values justify|char
for the ALIGN attribute are new and are not widely
implemented. The table proposal states that a browser may
display ALIGN=justify the same as the
default ALIGN=left if it lacks support for
text justification. The AXIS and AXES attributes for
cells provide a means for defining concise labels for
cells, either for speech rendering, or for database field
names. The attribute AXIS defaults to the cell contents.
The AXES is a comma separated list of axis names which
together identify the row and column headers that pertain
to this cell. The NOWRAP attribute will suppress word
wrap in the cell. The ROWSPAN and COLSPAN attributes
define the integer number of rows and columns spanned by
the cell. A value of zero for either implies the cell
spans from this cell to the end of the table. The
attribute DP is from an earlier version of the proposal
and was used with a value of decimal on the
ALIGN attribute. It has been replaced with the CHAR and
CHAROFF attributes used when ALIGN=char.
CHAR specifies a single character to be used for
alignment, and defaults to the decimal point in the
current language. CHAROFF specifies the offset, in the
DIR direction, to the first occurrence of the CHAR
character on each line. If a line doesn't include the
CHAR character, it is to end at the CHAROFF position. The
default value for CHAROFF is either 50% or whatever will
cause the CHAR characters in all cells with a declared
CHAR in a column to align. The default units is pixels,
but may be specified by a suffix on the number. The
standard defined units suffixes include: pt=points,
pi=picas, in=inches, cm=centimeters,
mm=millimeters, em=em units, px=screen
pixels. In addition the suffix of a percentsign may be
used to specify the percentage offset within the cell.
The VALIGN attribute defines the vertical alignment of
the cell contents. The ALIGN, CHAR and CHAROFF attribute
values may be inherited from other table elements in the
following order: cells < columns < column groups
< rows < row groups < default. The VALIGN, LANG
and DIR attribute values may be inherited from other
table elements in the following order: cells < rows
< row groups < columns < column groups <
table < default.
The WIDTH attribute is a Netscape extension. The
BGCOLOR attribute is a MS Internet Explorer 2.0
extension. Internet Explorer accepts either an
"#rrggbb" number or the following color names:
Black, Maroon, Green, Olive, Navy, Purple, Teal, Gray,
Silver, Red, Lime, Yellow, Blue, Fuchsia, Aqua, White.
NAME
defines the symbolic name of the field returned to the
server on submission. The characters between the opening
and closing tags define the text to be initially
displayed in the textarea, and the default text to be
returned, normally null. Only ASCII text is allowed as
characters, and newlines are respected. ROWS
and COLS define the physical size of the
displayed input field in numbers of characters. <TEXTAREA NAME="..."
ROWS="..." COLS="...">
</TEXTAREA> <TEXTAREA NAME="..."
ROWS="..." COLS="..."
LANG="..." DIR=ltr|rtl ID="..."
CLASS="..." WRAP=off|virtual|physical
ALIGN=top|middle|bottom|left|right DISABLED
ERROR="...">characters... </TEXTAREA>
<INPUT> <SELECT> <TEXTAREA>
are expressly prohibited by RFC 1866 from being nested
within the TEXTAREA element content <FORM> off is default and
lines are sent exactly as typed. The value virtual
wraps in the display but are sent exactly as typed. The
value physical wraps in the display and
sends new-lines at the wrap points as if new-lines had
been entered. The early Version 3 proposal added the
ALIGN, DISABLED, and ERROR attributes. The Version 3
proposed DISABLED attribute would display this TEXTAREA,
but prohibit user entry/modification. The Version 3
proposed ERROR attribute defines text to be displayed in
the event that the entered value for this TEXTAREA is
invalid. All elements concerning FORM are Level 2. <TFOOT> <TFOOT LANG="..." DIR=ltr|rtl
ID="..." CLASS="..."
ALIGN=left|right|center|justify|char CHAR="..."
CHAROFF="..."
VALIGN=top|middle|bottom|baseline>characters...</TFOOT>
TR TABLE The
table proposal states that a browser may display ALIGN=justify
the same as the default ALIGN=left if it
lacks support for text justification. The CHAR and
CHAROFF attributes are used when ALIGN=char.
CHAR specifies a single character to be used for
alignment, and defaults to the decimal point in the
current language. CHAROFF specifies the offset, in the
DIR direction, to the first occurrence of the CHAR
character on each line. If a line doesn't include the
CHAR character, it is to end at the CHAROFF position. The
default value for CHAROFF is either 50% or whatever will
cause the CHAR characters in all cells with a declared
CHAR in a column to align. The default units is pixels,
but may be specified by a suffix on the number. The
standard defined units suffixes include: pt=points,
pi=picas, in=inches, cm=centimeters,
mm=millimeters, em=em units, px=screen
pixels. In addition the suffix of a percentsign may be
used to specify the percentage offset within the cell.
The VALIGN attribute defines the vertical alignment of
the cell contents. The ALIGN, CHAR and CHAROFF attribute
values may be inherited from other table elements in the
following order: cells < columns < column groups
< rows < row groups < default. The VALIGN, LANG
and DIR attribute values may be inherited from other
table elements in the following order: cells < rows
< row groups < columns < column groups <
table < default.
<TH> <TH LANG="..." DIR=ltr|rtl
ID="..." CLASS="..."
AXIS="..." AXES="..." NOWRAP
ROWSPAN=value COLSPAN=value
ALIGN=left|right|center|justify|char|decimal
CHAR="..." CHAROFF="..."
DP="..." VALIGN=top|middle|bottom|baseline
WIDTH=value
BGCOLOR="...">characters...</TH>
body.content
TR The values justify|char
for the ALIGN attribute are new and are not widely
implemented. The table proposal states that a browser may
display ALIGN=justify the same as the
default ALIGN=left if it lacks support for
text justification. The AXIS and AXES attributes for
cells provide a means for defining concise labels for
cells, either for speech rendering, or for database field
names. The attribute AXIS defaults to the cell contents.
The AXES is a comma separated list of axis names which
together identify the row and column headers that pertain
to this cell. The NOWRAP attribute will suppress word
wrap in the cell. The ROWSPAN and COLSPAN attributes
define the integer number of rows and columns spanned by
the cell. A value of zero for either implies the cell
spans from this cell to the end of the table. The
attribute DP is from an earlier version of the proposal
and was used with a value of decimal on the
ALIGN attribute. It has been replaced with the CHAR and
CHAROFF attributes used when ALIGN=char.
CHAR specifies a single character to be used for
alignment, and defaults to the decimal point in the
current language. CHAROFF specifies the offset, in the
DIR direction, to the first occurrence of the CHAR
character on each line. If a line doesn't include the
CHAR character, it is to end at the CHAROFF position. The
default value for CHAROFF is either 50% or whatever will
cause the CHAR characters in all cells with a declared
CHAR in a column to align. The default units is pixels,
but may be specified by a suffix on the number. The
standard defined units suffixes include: pt=points,
pi=picas, in=inches, cm=centimeters,
mm=millimeters, em=em units, px=screen
pixels. In addition the suffix of a percentsign may be
used to specify the percentage offset within the cell.
The VALIGN attribute defines the vertical alignment of
the cell contents. The ALIGN, CHAR and CHAROFF attribute
values may be inherited from other table elements in the
following order: cells < columns < column groups
< rows < row groups < default. The VALIGN, LANG
and DIR attribute values may be inherited from other
table elements in the following order: cells < rows
< row groups < columns < column groups <
table < default.
The WIDTH attribute is a Netscape extension. The
BGCOLOR attribute is a MS Internet Explorer 2.0
extension. Internet Explorer accepts either an
"#rrggbb" number or the following color names:
Black, Maroon, Green, Olive, Navy, Purple, Teal, Gray,
Silver, Red, Lime, Yellow, Blue, Fuchsia, Aqua, White.
<THEAD> <THEAD LANG="..." DIR=ltr|rtl
ID="..." CLASS="..."
ALIGN=left|right|center|justify|char CHAR="..."
CHAROFF="..."
VALIGN=top|middle|bottom|baseline>characters...</THEAD>
TR TABLE The table proposal states that a browser may display ALIGN=justify
the same as the default ALIGN=left if it
lacks support for text justification. The CHAR and
CHAROFF attributes are used when ALIGN=char.
CHAR specifies a single character to be used for
alignment, and defaults to the decimal point in the
current language. CHAROFF specifies the offset, in the
DIR direction, to the first occurrence of the CHAR
character on each line. If a line doesn't include the
CHAR character, it is to end at the CHAROFF position. The
default value for CHAROFF is either 50% or whatever will
cause the CHAR characters in all cells with a declared
CHAR in a column to align. The default units is pixels,
but may be specified by a suffix on the number. The
standard defined units suffixes include: pt=points,
pi=picas, in=inches, cm=centimeters,
mm=millimeters, em=em units, px=screen
pixels. In addition the suffix of a percentsign may be
used to specify the percentage offset within the cell.
The VALIGN attribute defines the vertical alignment of
the cell contents. The ALIGN, CHAR and CHAROFF attribute
values may be inherited from other table elements in the
following order: cells < columns < column groups
< rows < row groups < default. The VALIGN, LANG
and DIR attribute values may be inherited from other
table elements in the following order: cells < rows
< row groups < columns < column groups <
table < default.
<TITLE>characters... </TITLE> <TITLE LANG="..."
DIR=ltr|rtl>characters... </TITLE> <META> <LINK> are
expressly prohibited by RFC 1866 from being nested within
the TITLE element content <HEAD> <TR> <TR LANG="..." DIR=ltr|rtl
ID="..." CLASS="..."
ALIGN=left|right|center|justify|char|decimal
CHAR="..." CHAROFF="..."
VALIGN=top|middle|bottom|baseline DP="...">
<TD> <TH> <TBODY> <TFOOT> <THEAD> The values
justify|char for the ALIGN attribute are new
and are not widely implemented. The table proposal states
that a browser may display ALIGN=justify the
same as the default ALIGN=left if it lacks
support for text justification. The attribute DP is from
an earlier version of the proposal and was used with a
value of decimal on the ALIGN attribute. It
has been replaced with the CHAR and CHAROFF attributes
used when ALIGN=char. CHAR specifies a
single character to be used for alignment, and defaults
to the decimal point in the current language. CHAROFF
specifies the offset, in the DIR direction, to the first
occurrence of the CHAR character on each line. If a line
doesn't include the CHAR character, it is to end at the
CHAROFF position. The default value for CHAROFF is either
50% or whatever will cause the CHAR characters in all
cells with a declared CHAR in a column to align. The
default units is pixels, but may be specified by a suffix
on the number. The standard defined units suffixes
include: pt=points, pi=picas, in=inches,
cm=centimeters, mm=millimeters,
em=em units, px=screen pixels.
In addition the suffix of a percentsign may be used to
specify the percentage offset within the cell. The VALIGN
attribute defines the vertical alignment of the cell
contents. The ALIGN, CHAR and CHAROFF attribute values
may be inherited from other table elements in the
following order: cells < columns < column groups
< rows < row groups < default. The VALIGN, LANG
and DIR attribute values may be inherited from other
table elements in the following order: cells < rows
< row groups < columns < column groups <
table < default.
<TT>characters... </TT> <TT LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</TT> text
font <U>characters... </U> <U LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</U> -In progress, to be determined- -In progress, to be determined- <LI>
elements, and usually marked by a bullet or similar
symbol. <UL></UL> <UL COMPACT LANG="..." DIR=ltr|rtl
ALIGN=center|left|right|justify ID="..."
CLASS="..."
CLEAR=left|right|all|"..." PLAIN
SRC="..." MD="..."
DINGBAT="..." WRAP=vert|horiz
TYPE=disk|circle|square> </UL> <LH> <LI> list ALIGN=center|left|right|justify
Version 3 proposes the CLEAR, PLAIN, SRC, MD, DINGBAT,
and WRAP attributes. The TYPE attribute is a current
Netscape extension. Version 3 proposes to replace it with
the SRC and DINGBAT attributes to point to general server
and browser images respectively. Specifying <UL
PLAIN> to eliminate the bullets is proposed by
Version 3 as a replacement for the MENU element. Specifying <UL
PLAIN WRAP=HORIZ> is proposed by Version 3 as a
replacement for the DIR list
element. The browser may dynamically determine the
appropriate number of columns. All list elements are
Level 0. <VAR>characters... </VAR> <VAR LANG="..." DIR=ltr|rtl
ID="..." CLASS="...">characters...
</VAR> text
phrase <WBR> <WBR> <NOBR>
<XMP>characters... </XMP> <XMP WIDTH="..." LANG="..."
DIR=ltr|rtl>characters... </XMP> block <PRE> element. RFC 1866 states
that the content of the XMP element should be rendered so
that at least 80 characters fit on a line. RFC 1866 has
declared XMP as deprecated and some current browsers no
longer recognize it. The LANG and DIR attributes are
introduced with the internationalization proposal. Michael J. Hannah
Sandia National Laboratories
mjhanna@sandia.gov