Document Object Model

Not to be confused with Domain Object Model. This article includes a list of references, related reading or external links, but its sources remain unclear because it lacks inline citations. Please improve this article by introducing more precise citations where appropriate. (August 2010) HTML HTML and HTML5 Dynamic HTML XHTML XHTML Mobile Profile and C-HTML Canvas element Character encodings Document Object Model Font family HTML editor HTML element HTML Frames HTML5 video HTML scripting Web browser engine Quirks mode Style sheets Unicode and HTML W3C and WHATWG Web colors WebGL Web Storage Comparison of document markup languages web browsers layout engines for HTML HTML5 HTML5 Canvas HTML5 Media Non-standard HTML XHTML This box: view · talk · Hierarchy of objects in an example HTML DOM - Document Object Model The Document Object Model (DOM) is a cross-platform and language-independent convention for representing and interacting with objects in HTML, XHTML and XML documents. Aspects of the DOM (such as its "Elements") may be addressed and manipulated within the syntax of the programming language in use. The public interface of a DOM is specified in its application programming interface (API). Contents 1 History 1.1 Legacy DOM 1.2 Intermediate DOM 1.3 Standardization 2 Applications 2.1 Web browsers 3 Implementations 3.1 Layout engines 3.2 Libraries 4 See also 5 References 6 External links // History The history of the Document Object Model is intertwined with the history of the "browser wars" of the late 1990s between Netscape Navigator and Microsoft Internet Explorer, as well as with that of JavaScript and JScript, the first scripting languages to be widely implemented in the layout engines of web browsers. Legacy DOM JavaScript was released by Netscape Communications in 1996 within Netscape Navigator 2.0. Netscape's competitor, Microsoft, released Internet Explorer 3.0 later the same year with a port of JavaScript called JScript. JavaScript and JScript let web developers create web pages with client-side interactivity. The limited facilities for detecting user-generated events and modifying the HTML document in the first generation of these languages eventually became known as "DOM Level 0" or "Legacy DOM". No independent standard was developed for DOM Level 0, but it was partly described in the specification of HTML4. Legacy DOM was limited in the kinds of elements that could be accessed. Form, link and image elements could be referenced with a hierarchical name that began with the root document object. A hierarchical name could make use of either the names or the sequential index of the traversed elements. For example, a form input element could be accessed as either "document.formName.inputName" or "document.forms[0].elements[0]". The Legacy DOM enabled client-side form validation and the popular "rollover" effect. Intermediate DOM In 1997, Netscape and Microsoft released version 4.0 of Netscape Navigator and Internet Explorer, adding support for Dynamic HTML (DHTML), functionality enabling changes to a loaded HTML document. DHTML required extensions to the rudimentary document object that was available in the Legacy DOM implementations. Although the Legacy DOM implementations were largely compatible since JScript was based on JavaScript, the DHTML DOM extensions were developed in parallel by each browser maker and remained incompatible. These versions of the DOM became known as the "Intermediate DOM." The Intermediate DOMs enabled the manipulation of Cascading Style Sheet (CSS) properties which influence the display of a document. They also provided access to a new feature called "layers" via the "document.layers" property (Netscape Navigator) and the "document.all" property (Internet Explorer). Because of the fundamental incompatibilities in the Intermediate DOMs, cross-browser development required special handling for each supported browser. Subsequent versions of Netscape Navigator abandoned support for its Intermediate DOM. Internet Explorer continues to support its Intermediate DOM for backwards compatibility. Standardization The World Wide Web Consortium (W3C), founded in 1994 to promote open standards for the World Wide Web, brought Netscape Communications and Microsoft together with other companies to develop a standard for browser scripting languages, called "ECMAScript". The first version of the standard was published in 1997. Subsequent releases of JavaScript and JScript would implement the ECMAScript standard for greater cross-browser compatibility. After the release of ECMAScript, W3C began work on a standardized DOM. The initial DOM standard, known as "DOM Level 1," was recommended by W3C in late 1998. About the same time, Internet Explorer 5.0 shipped with limited support for DOM Level 1. DOM Level 1 provided a complete model for an entire HTML or XML document, including means to change any portion of the document. Non-conformant browsers such as Internet Explorer 4.x and Netscape 4.x were still widely used as late as 2000. DOM Level 2 was published in late 2000. It introduced the "getElementById" function as well as an event model and support for XML namespaces and CSS. DOM Level 3, the current release of the DOM specification, published in April 2004, added support for XPath and keyboard event handling, as well as an interface for serializing documents as XML. By 2005, large parts of W3C DOM were well-supported by common ECMAScript-enabled browsers, including Microsoft Internet Explorer version 6 (2001), Opera, Safari and Gecko-based browsers (like Mozilla, Firefox, SeaMonkey and Camino). Applications DOM is likely to be best suited for applications where the document must be accessed repeatedly or out of sequence order. If the application is strictly sequential and one-pass, the SAX model is likely to be faster and use less memory. Web browsers A web browser is not obliged to use DOM in order to render an HTML document. However, the DOM is required by JavaScript scripts that wish to inspect or modify a web page dynamically. In other words, the Document Object Model is the way JavaScript sees its containing HTML page and browser state. Implementations Because DOM supports navigation in any direction (e.g., parent and previous sibling) and allows for arbitrary modifications, an implementation must at least buffer the document that has been read so far (or some parsed form of it). Layout engines Web browsers rely on layout engines to parse HTML into a DOM. Some layout engines such as Trident/MSHTML and Presto are associated primarily or exclusively with a particular browser such as Internet Explorer and Opera respectively. Others, such as WebKit and Gecko, are shared by a number of browsers, such as Safari, Google Chrome, RockMelt, Firefox or Flock. The different layout engines implement the DOM standards to varying degrees of compliance. See also: Comparison of layout engines (Document Object Model) Libraries DOM implementations: libxml2 MSXML Xerces is a C++ DOM implementation with Java and Perl bindings APIs that expose DOM implementations: JAXP (Java API for XML Processing) is an API for accessing DOM providers See also DOM scripting JSON Prototype.js JQuery SAX - serial access parser API for XML, an alternative to DOM. JDOM - a Java-based document object model for XML that integrates with DOM and SAX and uses parsers to build the document. SXML - a model for representing XML and HTML in the form of S-expressions. Ajax - a methodology employing DOM in combination with techniques for retrieving data without reloading a page. TinyXml - efficient platform-independent XML library for C++. RapidXml - is an attempt to create the fastest XML parser possible using modern C++. Application Object Model References Flanagan, David (2006). JavaScript: The Definitive Guide. O'Reilly & Associates. pp. 312–313. ISBN 0596101996.  Koch, Peter-Paul (May 14, 2001). "The Document Object Model: an Introduction". Digital Web Magazine. http://www.digital-web.com/articles/the_document_object_model/. Retrieved January 10, 2009.  Le Hégaret, Philippe (2002). "The W3C Document Object Model (DOM)". World Wide Web Consortium. http://www.w3.org/2002/07/26-dom-article.html. Retrieved January 10, 2009.  Guisset, Fabian. "What does each DOM Level bring?". Mozilla Developer Center. Mozilla Project. https://developer.mozilla.org/en/docs/DOM_Levels. Retrieved January 10, 2009.  External links Wikimedia Commons has media related to: Document object models W3.org on DOM Technology Reports What does your user agent claim to support? W3C DOM scripts and compatibility tables (Quirksmode) Gecko DOM Reference (Mozilla Developer Center) DOM Reference (Tellme) IB DOM Utilities: Mapping JavaScript Objects to DOM Elements XJR with DOM, SAX2, and XPath interfaces Great DOM and JavaScript video lecture by Douglas Crockford v · d · eWorld Wide Web Consortium Products and standards Recommendations Canonical XML · CDF · CSS · DOM · Geolocation API · HTML · MathML · OWL · P3P · PLS · RDF · RDF Schema · SISR · SKOS · SMIL · SOAP · SRGS · SSML · SVG · SPARQL · Timed Text · VoiceXML · WSDL · XForms · XHTML · XHTML+RDFa · XInclude · XLink · XML · XML Base · XML Encryption · XML Events · XML Information Set · XML namespace · XML Schema · XML Signature · XPath 1.0, 2.0 · XPointer · XProc · XQuery · XSL · XSL-FO · XSLT (elements)  · XUP Notes XAdES · XHTML+SMIL Working Drafts CCXML · CURIE · HTML5 · InkML · RIF · SCXML · SMIL Timesheets · sXBL · WICD · XFDL · XFrames · XBL · XHTML+MathML+SVG · XMLHttpRequest Guidelines Web Content Accessibility Guidelines Initiative Multimodal Interaction Activity · Markup Validation Service · Web Accessibility Initiative Deprecated C-HTML · HDML · JSSS · PGML · VML Organizations World Wide Web Foundation · SVG Working Group · WebOnt · W3C Device Description Working Group · WHATWG Software Agora · Argo · Arena · Amaya · CERN httpd · Libwww · Line Mode Browser Conference-related IW3C2 · World Wide Web Conference · WWW1