Please refer to the errata for this document, which may include some normative corrections.
This document is also available in these non-normative formats: XML file, plain text, PostScript file, PDF file, single HTML file, and ZIP file.
See also translations of this document.
Copyright ©2003 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.
This specification defines the Document Object Model Level 2 HTML, a platform- and language-neutral interface that allows programs and scripts to dynamically access and update the content and structure of [HTML 4.01] and [XHTML 1.0] documents. The Document Object Model Level 2 HTML builds on the Document Object Model Level 2 Core [DOM Level 2 Core] and is not backward compatible with DOM Level 1 HTML [DOM Level 1].
This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.
This is the 09 January 2003 of "DOM Level 2 HTML". This document has been reviewed by W3C Members, software developers, and other W3C groups and interested parties, and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This document enhances the interoperability of the Web.
Patent disclosures relevant to this specification may be found on the Working Group's public patent disclosure page.
This document has been produced as part of the W3C DOM Activity. The authors of this document are the DOM Working Group participants.
The English version of this specification is the only normative version. Information about translations of this document is available at http://www.w3.org/2000/11/DOM-Level-2-translations.
The list of known errors in this document is available at http://www.w3.org/2000/11/DOM-Level-2-errata
Comments on this document are invited and are to be sent to the public mailing list www-dom@w3.org. An archive is available at http://lists.w3.org/Archives/Public/www-dom/.
An implementation report, based on the DOM Test Suite work, is available at http://www.w3.org/2002/11/DOM-Level-2-HTML-Results.
A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR.
Note:This specification renders the DOM Level 1 HTML Recommendation obsolete given that some changes from DOM Level 1 HTML are incompatible with that specification but represent more accurately the state of deployed software. W3C strongly suggests that developers and authors conform to DOM Level 2 HTML instead.
Copyright © 2003 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved.
This document is published under the W3C Document Copyright Notice and License. The bindings within this document are published under the W3C Software Copyright Notice and License. The software license requires "Notice of any changes or modifications to the W3C files, including the date changes were made." Consequently, modified versions of the DOM bindings must document that they do not conform to the W3C standard; in the case of the IDL definitions, the pragma prefix can no longer be 'w3c.org'; in the case of the Java Language binding, the package names can no longer be in the 'org.w3c' package.
Note: This section is a copy of the W3C Document Notice and License and could be found at http://www.w3.org/Consortium/Legal/copyright-documents-19990405.
Copyright © 1994-2003 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved.
http://www.w3.org/Consortium/Legal/
Public documents on the W3C site are provided by the copyright holders under the following license. The software or Document Type Definitions (DTDs) associated with W3C specifications are governed by the Software Notice. By using and/or copying this document, or the W3C document from which this statement is linked, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:
Permission to use, copy, and distribute the contents of this document, or the W3C document from which this statement is linked, in any medium for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the document, or portions thereof, that you use:
When space permits, inclusion of the full text of this NOTICE should be provided. We request that authorship attribution be provided in any software, documents, or other items or products that you create pursuant to the implementation of the contents of this document, or any portion thereof.
No right to create modifications or derivatives of W3C documents is granted pursuant to this license. However, if additional requirements (documented in the Copyright FAQ) are satisfied, the right to create modifications or derivatives is sometimes granted by the W3C to individuals complying with those requirements.
THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to this document or its contents without specific, written prior permission. Title to copyright in this document will at all times remain with copyright holders.
Note: This section is a copy of the W3C Software Copyright Notice and License and could be found at http://www.w3.org/Consortium/Legal/copyright-software-19980720
Copyright © 1994-2003 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved.
http://www.w3.org/Consortium/Legal/
This W3C work (including software, documents, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:
Permission to use, copy, and modify this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications, that you make:
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.
This section extends the DOM Level 2 Core API [DOM Level 2 Core] to describe objects and methods specific to HTML documents [HTML 4.01], and XHTML documents [XHTML 1.0]. In general, the functionality needed to manipulate hierarchical document structures, elements, and attributes will be found in the core section; functionality that depends on the specific elements defined in HTML will be found in this section.
The goals of the HTML-specific DOM API are:
The key differences between the core DOM and the HTML application of DOM is that the HTML Document Object Model exposes a number of convenience methods and properties that are consistent with the existing models and are more appropriate to script writers. In many cases, these enhancements are not applicable to a general DOM because they rely on the presence of a predefined DTD. The transitional or frameset DTD for HTML 4.01, or the XHTML 1.0 DTDs are assumed. Interoperability between implementations is only guaranteed for elements and attributes that are specified in the HTML 4.01 and XHTML 1.0 DTDs.
More specifically, this document includes the following specializations for HTML:
HTMLDocument
interface, derived from the core Document interface.
HTMLDocument
specifies the operations and queries that can be made on a HTML
document.HTMLElement
interface, derived from the core Element interface. HTMLElement specifies
the operations and queries that can be made on any HTML element.
Methods on HTMLElement include
those that allow for the retrieval and modification of attributes
that apply to all HTML elements.HTMLElement
interface. For all such attributes, the derived interface for the
element contains explicit methods for setting and getting the
values.The DOM Level 2 includes mechanisms to access and modify style specified through CSS and defines an event model that can be used with HTML documents.
The interfaces found within this section are not mandatory. A
DOM application may use the hasFeature(feature,
version) method of the DOMImplementation
interface with parameter values "HTML" and "2.0" (respectively) to
determine whether or not this module is supported by the
implementation. In addition to the feature string "HTML", the
feature string "XHTML" (version string "2.0") can be used to check
if the implementation supports XHTML (this is equivalent to
checking the features "XML" and "HTML"). In order to fully support
this module, an implementation must also support the "Core" feature
defined [DOM Level 2 Core]. Please refer
to additional information about
conformance in the DOM Level 2 Core specification [DOM Level 2
Core].
A DOM application can use the hasFeature method of
the DOMImplementation interface to determine whether
they are supported or not. The feature string for all the
interfaces listed in this section is "HTML" and the version is
"2.0". In order to fully support this feature, an implementation
needs also to support the "Core" feature defined in the Document
Object Model Level 2 Core [DOM Level 2 Core] (see also
Conformance).
The interfaces in this specification are designed for [HTML 4.01] documents, as well as for [XHTML 1.0] documents.
Note: This specification does not intend to define
exactly how a user agent will respond to a change to any attribute
on an element that directly or indirectly references external data,
such elements are HTMLAppletElement, HTMLFrameElement, HTMLFrameSetElement,
HTMLIFrameElement,
HTMLImageElement,
HTMLLinkElement,
HTMLObjectElement,
HTMLParamElement,
and HTMLScriptElement.
The HTML DOM follows a naming convention for properties, methods, events, collections, and data types. All names are defined as one or more English words concatenated together to form a single string.
The property or method name starts with the initial keyword in lowercase, and each subsequent word starts with a capital letter. For example, a property that returns document meta information such as the date the file was created might be named "fileDateCreated". In the ECMAScript binding, properties are exposed as properties of a given object. In Java, properties are exposed with get and set methods.
While most of the interfaces defined below can be mapped directly to elements defined in the HTML 4.01 Recommendation, some of them cannot. Similarly, not all attributes listed below have counterparts in the HTML 4.01 specification (and some do, but have been renamed to avoid conflicts with scripting languages). Interfaces and attribute definitions that have links to the HTML 4.0 specification have corresponding element and attribute definitions there; all others are added by this specification, either for convenience or backwards compatibility with DOM Level 0 implementations.
The DOM HTML Level 1 API [DOM Level 1] were originally intended to be used only for HTML 4.01 documents [HTML 4.01]. The APIs were defined well before XHTML 1.0 [XHTML 1.0] became a specification, or before it was worked on by the HTML Working Group.
From the DOM point of view, The biggest difference between HTML 4.01 (and earlier) and XHTML 1.0 is that XHTML is case sensitive, whereas HTML 4.01 is case insensitive. The HTML case insensitivity is also reflected in the DOM HTML API. For instance, element and attribute names are exposed as all uppercase (for consistency) when used on an HTML document, regardless of the character case used in the markup. Since XHTML is based on XML, in XHTML everything is case sensitive, and element and attribute names must be lowercase in the markup.
Developers need to take two things into account when writing
code that works on both HTML and XHTML documents. When comparing
element or attribute names to strings, the string compare needs to
be case insensitive, or the element or attribute name needs to be
converted into lowercase before comparing against a lowercase
string. Second, when calling methods that are case insensitive when
used on a HTML document (such as
getElementsByTagName() and namedItem()),
the string that is passed in should be lowercase.
Note: The interfaces provided in this document are only for [HTML 4.01] and [XHTML 1.0] documents and are not guaranteed to work with any future version of XHTML.
An HTMLCollection is a list of nodes. An individual
node may be accessed by either ordinal index or the node's
name or id attributes.
Note: Collections in the HTML DOM are assumed to be live meaning that they are automatically updated when the underlying document is changed.
interface HTMLCollection { readonly attribute unsigned long length; Node item(in unsigned long index); Node namedItem(in DOMString name); };
length of type unsigned
long, readonlyitemindex of type
unsigned long0.|
|
The |
namedItemNode using
a name. With [HTML 4.01] documents, it first
searches for a Node with a matching id
attribute. If it doesn't find one, it then searches for a
Node with a matching name attribute, but
only on those elements that are allowed a name attribute. With [XHTML
1.0] documents, this method only searches for
Nodes with a matching id attribute. This
method is case insensitive in HTML documents and case sensitive in
XHTML documents.
name of type
DOMStringNode to be fetched.|
|
The |
An HTMLOptionsCollection is a list of nodes
representing HTML option element. An individual node may be
accessed by either ordinal index or the node's name or
id attributes.
Note: Collections in the HTML DOM are assumed to be live meaning that they are automatically updated when the underlying document is changed.
// Introduced in DOM Level 2: interface HTMLOptionsCollection { attribute unsigned long length; // raises(DOMException) on setting Node item(in unsigned long index); Node namedItem(in DOMString name); };
length of type
unsigned long|
|
NOT_SUPPORTED_ERR: if setting the length is not allowed by the implementation. |
itemindex of type
unsigned long|
|
The |
namedItemNode using
a name. It first searches for a Node with a matching
id attribute. If it doesn't find one, it then searches
for a Node with a matching name
attribute, but only on those elements that are allowed a name
attribute. This method is case insensitive in HTML documents and
case sensitive in XHTML documents.
name of type
DOMStringNode to be fetched.|
|
The |
An HTMLDocument is the root of the HTML hierarchy
and holds the entire content. Besides providing access to the
hierarchy, it also provides some convenience
methods for accessing certain sets of information from the
document.
The following properties have been deprecated in favor of the
corresponding ones for the BODY element:
Note: In DOM Level 2, the method
getElementById is inherited from the
Document interface where it was moved to.
interface HTMLDocument : Document { attribute DOMString title; readonly attribute DOMString referrer; readonly attribute DOMString domain; readonly attribute DOMString URL; attribute HTMLElement body; readonly attribute HTMLCollection images; readonly attribute HTMLCollection applets; readonly attribute HTMLCollection links; readonly attribute HTMLCollection forms; readonly attribute HTMLCollection anchors; attribute DOMString cookie; // raises(DOMException) on setting void open(); void close(); void write(in DOMString text); void writeln(in DOMString text); NodeList getElementsByName(in DOMString elementName); };
URL of type DOMString,
readonlyanchors of type HTMLCollection,
readonlyA) elements in a
document with a value for the name attribute.
Note: For reasons of backward compatibility, the returned
set of anchors only contains those anchors created with the
name attribute, not those created with the
id attribute. Note that in [XHTML
1.0], the name attribute (see section
4.10) has no semantics and is only present for legacy user
agents: the id attribute is used instead. Users should
prefer the iterator mechanisms provided by [DOM Level 2 Traversal]
instead.
applets of type HTMLCollection,
readonlyOBJECT elements that
include applets and APPLET (deprecated)
elements in a document.body of type HTMLElementBODY contents, returns the
BODY element. In frameset documents, this returns the
outermost FRAMESET element.cookie of type
DOMStringcookies non-terminal of [IETF RFC 2965], Section
4.2.2.cookie non-terminal of [IETF RFC
2965]; that is, it should be a single name-value pair followed
by zero or more cookie attribute values. If no domain attribute is
specified, then the domain attribute for the new value defaults to
the host portion of an absolute URI [IETF RFC 2396] of the current
frame or document. If no path attribute is specified, then the path
attribute for the new value defaults to the absolute path portion
of the URI [IETF RFC 2396] of the current
frame or document. If no max-age attribute is specified, then the
max-age attribute for the new value defaults to a user agent
defined value. If a cookie with the specified name is already
associated with the current frame or document, then the new value
as well as the new attributes replace the old value and attributes.
If a max-age attribute of 0 is specified for the new value, then
any existing cookies of the specified name are removed from the
cookie storage.
Note: See [IETF RFC 2965] for the semantics of persistent state item attribute value pairs.
Note: The precise nature of a user agent session is not defined by this specification.
|
|
SYNTAX_ERR: If the new value does not adhere to the cookie syntax specified by [IETF RFC 2965]. |
domain of type DOMString,
readonlynull if the server cannot be identified by a domain
name.forms of type HTMLCollection,
readonlyimages of type HTMLCollection,
readonlyIMG elements in a
document. The behavior is limited to IMG elements for
backwards compatibility.
Note: As suggested by [HTML 4.01], to include images,
authors may use the OBJECT element or the
IMG element. Therefore, it is recommended not to use
this attribute to find the images in the document but
getElementsByTagName with HTML 4.01 or
getElementsByTagNameNS with XHTML 1.0.
links of type HTMLCollection,
readonlyAREA elements and anchor
(A) elements in a document with a value for the
href attribute.referrer of type
DOMString, readonlytitle of type
DOMStringTITLE
element in the head of the document.closeopen() and forces rendering.
getElementsByNamename value is given by elementName. In
[XHTML
1.0] documents, this methods only return the (possibly empty)
collection of form controls with matching name. This method is case
sensitive.
elementName of type
DOMStringname attribute value for an element.|
|
The matching elements. |
openNote: This method and the ones following allow a user to add to or replace the structure model of a document using strings of unparsed HTML. At the time of writing alternate methods for providing similar functionality for both HTML and XML documents were being considered (see [DOM Level 3 Load and Save]).
writeopen(). Note that the function will produce
a document which is not necessarily driven by a DTD and therefore
might be produce an invalid result in the context of the document.
text of type
DOMStringwritelnopen(). Note
that the function will produce a document which is not necessarily
driven by a DTD and therefore might be produce an invalid result in
the context of the document
text of type
DOMStringHTML attributes are exposed as properties on the element object. The DOM naming conventions always determine the name of the exposed property, and are independent of the case of the attribute in the source document. The data type of the property is in general determined by the type of the attribute as determined by the HTML 4.01 (transitional and frameset) and XHTML 1.0 DTDs. The attributes have the semantics (including case-sensitivity) given in the [HTML 4.01] and [XHTML 1.0] specifications.
The attributes are exposed as properties for compatibility with
DOM Level 0.
This usage is deprecated because it can not be generalized to all
possible attribute names for XML. We recommend the use of generic
methods on the core Element interface for setting,
getting and removing attributes.
| DTD Data Type | Object Model Data Type |
|---|---|
| CDATA | DOMString |
| Value list (e.g., (left | right | center)) | DOMString |
| one-value Value list (e.g., (disabled)) | boolean |
| Number | long int |
In an HTML document the return value of an attribute that has a data type that is a value list is normalized to lowercase (independent of the case of the value in the source document).
For example, if the value of the align attribute on a P element
is "Left" (which is not a valid value in XHTML due to the case
sensitivity of XHTML) then the value is returned as "left". For
attributes with the CDATA data type, the case of the
return value is that given in the source document.
The return value of an attribute that is unspecified and does not have a default value is the empty string if the return type is a DOMString, false if the return type is a boolean and 0 if the return type is a number.
To avoid namespace conflicts, two attributes with the same name
as a keyword in one of our chosen binding languages
were prefixed. The for attribute of the
LABEL and SCRIPT elements collides with
loop construct naming conventions and is renamed
htmlFor. The class attribute of the HTML
elements collides with class definitions naming conventions and is
renamed className.
tagName, (nodeName))If the document is an HTML 4.01 document the element type names
exposed through a property are in uppercase. For example, the body
element type name is exposed through the tagName
property as BODY. If the document is an XHTML 1.0
document the element name is exposed as it is written in the XHTML
file. This means that the element type names are exposed in
lowercase for XHTML documents since the XHTML 1.0 DTDs defines
element type names as lowercase, and XHTML, being derived from XML,
is case sensitive.
All HTML element interfaces derive from this class. Elements
that only expose the HTML core attributes are represented by the
base HTMLElement interface. These elements are as
follows:
Note: The style attribute of an HTML element
is accessible through the ElementCSSInlineStyle
interface which is defined in the CSS module [DOM
Level 2 Style Sheets and CSS].
interface HTMLElement : Element { attribute DOMString id; attribute DOMString title; attribute DOMString lang; attribute DOMString dir; attribute DOMString className; };
className of type
DOMStringdir of type
DOMStringid of type
DOMStringlang of type
DOMStringtitle of type
DOMStringRoot of an HTML document. See the HTML element definition in HTML 4.01.
interface HTMLHtmlElement : HTMLElement { attribute DOMString version; };
version of type
DOMStringDocument head information. See the HEAD element definition in HTML 4.01.
interface HTMLHeadElement : HTMLElement { attribute DOMString profile; };
profile of type
DOMStringThe LINK element specifies a link to an external
resource, and defines this document's relationship to that resource
(or vice versa). See the
LINK element definition in HTML 4.01 (see also the
LinkStyle interface in the StyleSheet module [DOM
Level 2 Style Sheets and CSS]).
interface HTMLLinkElement : HTMLElement { attribute boolean disabled; attribute DOMString charset; attribute DOMString href; attribute DOMString hreflang; attribute DOMString media; attribute DOMString rel; attribute DOMString rev; attribute DOMString target; attribute DOMString type; };
charset of type
DOMStringdisabled of type
booleanhref of type
DOMStringhreflang of type
DOMStringmedia of type
DOMStringrel of type
DOMStringrev of type
DOMStringtarget of type
DOMStringtype of type
DOMStringThe document title. See the TITLE element definition in HTML 4.01.
interface HTMLTitleElement : HTMLElement { attribute DOMString text; };
text of type
DOMStringThis contains generic meta-information about the document. See the META element definition in HTML 4.01.
interface HTMLMetaElement : HTMLElement { attribute DOMString content; attribute DOMString httpEquiv; attribute DOMString name; attribute DOMString scheme; };
content of type
DOMStringhttpEquiv of type
DOMStringname of type
DOMStringscheme of type
DOMStringDocument base URI [IETF RFC 2396]. See the BASE element definition in HTML 4.01.
interface HTMLBaseElement : HTMLElement { attribute DOMString href; attribute DOMString target; };
href of type
DOMStringtarget of type
DOMStringThis element is used for single-line text input. See the ISINDEX element definition in HTML 4.01. This element is deprecated in HTML 4.01.
interface HTMLIsIndexElement : HTMLElement { readonly attribute HTMLFormElement form; attribute DOMString prompt; };
form of type HTMLFormElement,
readonlyFORM element containing this control.
Returns null if this control is not within the context
of a form.prompt of type
DOMStringStyle information. See the
STYLE element definition in HTML 4.01, the CSS module [DOM Level
2 Style Sheets and CSS] and the LinkStyle
interface in the StyleSheets module [DOM Level 2 Style Sheets and
CSS].
interface HTMLStyleElement : HTMLElement { attribute boolean disabled; attribute DOMString media; attribute DOMString type; };
disabled of type
booleanmedia of type
DOMStringtype of type
DOMStringThe HTML document body. This element is always present in the DOM API, even if the tags are not present in the source document. See the BODY element definition in HTML 4.01.
interface HTMLBodyElement : HTMLElement { attribute DOMString aLink; attribute DOMString background; attribute DOMString bgColor; attribute DOMString link; attribute DOMString text; attribute DOMString vLink; };
aLink of type
DOMStringbackground of type
DOMStringbgColor of type
DOMStringlink of type
DOMStringtext of type
DOMStringvLink of type
DOMStringThe FORM element encompasses behavior similar to a
collection and an element. It provides direct access to the
contained form controls as well as the attributes of the form
element. See the
FORM element definition in HTML 4.01.
interface HTMLFormElement : HTMLElement { readonly attribute HTMLCollection elements; readonly attribute long length; attribute DOMString name; attribute DOMString acceptCharset; attribute DOMString action; attribute DOMString enctype; attribute DOMString method; attribute DOMString target; void submit(); void reset(); };
acceptCharset of type
DOMStringaction of type
DOMStringelements of type HTMLCollection,
readonlyenctype of type
DOMStringNote: The onsubmit even handler is not guaranteed to be triggered when invoking this method. The behavior is inconsistent for historical reasons and authors should not rely on a particular one.
length of type
long, readonlymethod of type
DOMStringname of type
DOMStringtarget of type
DOMStringThe select element allows the selection of an option. The contained options can be directly accessed through the select element as a collection. See the SELECT element definition in HTML 4.01.
interface HTMLSelectElement : HTMLElement { readonly attribute DOMString type; attribute long selectedIndex; attribute DOMString value; // Modified in DOM Level 2: attribute unsigned long length; // raises(DOMException) on setting readonly attribute HTMLFormElement form; // Modified in DOM Level 2: readonly attribute HTMLOptionsCollection options; attribute boolean disabled; attribute boolean multiple; attribute DOMString name; attribute long size; attribute long tabIndex; void add(in HTMLElement element, in HTMLElement before) raises(DOMException); void remove(in long index); void blur(); void focus(); };
disabled of type
booleanform of type HTMLFormElement,
readonlyFORM element containing this control.
Returns null if this control is not within the context
of a form.length of type unsigned
long, modified in DOM Level 2SELECT.|
|
NOT_SUPPORTED_ERR: if setting the length is not allowed by the implementation. |
multiple of type
booleanOPTION elements may be selected
in this SELECT. See the
multiple attribute definition in HTML 4.01.name of type
DOMStringoptions of type HTMLOptionsCollection,
readonly, modified in DOM Level 2OPTION elements contained by
this element.selectedIndex of type
longsize of type longtabIndex of type
longtype of type DOMString,
readonlytrue
and the string "select-one" when false.value of type
DOMStringaddOPTION elements for this SELECT. This
method is the equivalent of the appendChild method of
the Node interface if the before
parameter is null. It is equivalent to the
insertBefore method on the parent of
before in all other cases. This method may have no
effect if the new element is not an OPTION or an
OPTGROUP.
element of type HTMLElementbefore of type HTMLElementnull for the tail
of the list.|
|
NOT_FOUND_ERR: Raised if |
blurfocusremoveOPTION elements for this SELECT. Does
nothing if no element has the given index.
index of type
longGroup options together in logical subdivisions. See the OPTGROUP element definition in HTML 4.01.
interface HTMLOptGroupElement : HTMLElement { attribute boolean disabled; attribute DOMString label; };
disabled of type
booleanlabel of type
DOMStringA selectable choice. See the OPTION element definition in HTML 4.01.
interface HTMLOptionElement : HTMLElement { readonly attribute HTMLFormElement form; // Modified in DOM Level 2: attribute boolean defaultSelected; readonly attribute DOMString text; // Modified in DOM Level 2: readonly attribute long index; attribute boolean disabled; attribute DOMString label; attribute boolean selected; attribute DOMString value; };
defaultSelected of type
boolean, modified in DOM Level
2disabled of type
booleanform of type HTMLFormElement,
readonlyFORM element containing this control.
Returns null if this control is not within the context
of a form.index of type long,
readonly, modified in DOM Level 2OPTION in its parent
SELECT, starting from 0.label of type
DOMStringselected of type
booleantext of type DOMString,
readonlyvalue of type
DOMStringForm control.
Note: Depending upon the environment in which the page is being viewed, the value property may be read-only for the file upload input type. For the "password" input type, the actual value returned may be masked to prevent unauthorized use. See the INPUT element definition in [HTML 4.01].
interface HTMLInputElement : HTMLElement { attribute DOMString defaultValue; attribute boolean defaultChecked; readonly attribute HTMLFormElement form; attribute DOMString accept; attribute DOMString accessKey; attribute DOMString align; attribute DOMString alt; attribute boolean checked; attribute boolean disabled; attribute long maxLength; attribute DOMString name; attribute boolean readOnly; // Modified in DOM Level 2: attribute unsigned long size; attribute DOMString src; attribute long tabIndex; // Modified in DOM Level 2: attribute DOMString type; attribute DOMString useMap; attribute DOMString value; void blur(); void focus(); void select(); void click(); };
accept of type
DOMStringaccessKey of type
DOMStringalign of type
DOMStringalt of type
DOMStringchecked of type
booleantype attribute of the element has the
value "radio" or "checkbox", this represents the current state of
the form control, in an interactive user agent. Changes to this
attribute change the state of the form control, but do not change
the value of the HTML checked attribute of the INPUT element.
Note: During the handling of a click event on an input element with a type attribute that has the value "radio" or "checkbox", some implementations may change the value of this property before the event is being dispatched in the document. If the default action of the event is canceled, the value of the property may be changed back to its original value. This means that the value of this property during the handling of click events is implementation dependent.
defaultChecked of type
booleantype has the value "radio" or "checkbox",
this represents the HTML checked attribute of the element. The
value of this attribute does not change if the state of the
corresponding form control, in an interactive user agent, changes.
See the
checked attribute definition in HTML 4.01.defaultValue of type
DOMStringtype attribute of the element has the
value "text", "file" or "password", this represents the HTML value
attribute of the element. The value of this attribute does not
change if the contents of the corresponding form control, in an
interactive user agent, changes. See the
value attribute definition in HTML 4.01.disabled of type
booleanform of type HTMLFormElement,
readonlyFORM element containing this control.
Returns null if this control is not within the context
of a form.maxLength of type
longtype has the value "text" or "password". See the
maxlength attribute definition in HTML 4.01.name of type
DOMStringreadOnly of type
booleantype
has the value "text" or "password". See the
readonly attribute definition in HTML 4.01.size of type unsigned
long, modified in DOM Level 2src of type
DOMStringtype attribute has the value "image",
this attribute specifies the location of the image to be used to
decorate the graphical submit button. See the
src attribute definition in HTML 4.01.tabIndex of type
longtype of type DOMString,
modified in DOM Level 2useMap of type
DOMStringvalue of type
DOMStringtype attribute of the element has the
value "text", "file" or "password", this represents the current
contents of the corresponding form control, in an interactive user
agent. Changing this attribute changes the contents of the form
control, but does not change the value of the HTML value attribute
of the element. When the type attribute of the element
has the value "button", "hidden", "submit", "reset", "image",
"checkbox" or "radio", this represents the HTML value attribute of
the element. See the
value attribute definition in HTML 4.01.blurclickINPUT
elements whose type attribute has one of the following
values: "button", "checkbox", "radio", "reset", or "submit".
focusselectINPUT elements whose type attribute has
one of the following values: "text", "file", or "password".
Multi-line text field. See the TEXTAREA element definition in HTML 4.01.
interface HTMLTextAreaElement : HTMLElement { // Modified in DOM Level 2: attribute DOMString defaultValue; readonly attribute HTMLFormElement form; attribute DOMString accessKey; attribute long cols; attribute boolean disabled; attribute DOMString name; attribute boolean readOnly; attribute long rows; attribute long tabIndex; readonly attribute DOMString type; attribute DOMString value; void blur(); void focus(); void select(); };
accessKey of type
DOMStringcols of type longdefaultValue of type
DOMString, modified in DOM Level
2disabled of type
booleanform of type HTMLFormElement,
readonlyFORM element containing this control.
Returns null if this control is not within the context
of a form.name of type
DOMStringreadOnly of type
booleanrows of type longtabIndex of type
longtype of type
DOMString, readonlyvalue of type
DOMStringDOMString, the implementation may
truncate the data.Push button. See the BUTTON element definition in HTML 4.01.
interface HTMLButtonElement : HTMLElement { readonly attribute HTMLFormElement form; attribute DOMString accessKey; attribute boolean disabled; attribute DOMString name; attribute long tabIndex; readonly attribute DOMString type; attribute DOMString value; };
accessKey of type
DOMStringdisabled of type
booleanform of type HTMLFormElement,
readonlyFORM element containing this control.
Returns null if this control is not within the context
of a form.name of type
DOMString