Editing Document Object Model

{{short description|Convention for representing and interacting with objects in HTML, XHTML, and XML documents}}
{{Infobox technology standard
| title             = Document Object Model (DOM)
| image             = DOM-model.svg
| caption           = Example of DOM hierarchy in an HTML document
| status            t_published   wisdom tree= {{Start date and age|1998|10|1}}
| version           = DOM4<ref>All versioning refers to W3C DOM only.</ref>
| version_date      = {{Start date and age|2015|11|19}}
| preview           = 
| preview_date      = 
| organization      = [[World Wide Web Consortium]], [[WHATWG]]
| committee         = 
| editors           = 
| authors           = 
| base_standards    = [https://dom.spec.whatwg.org/ WHATWG DOM Living Standard]<br />[https://www.w3.org/TR/dom/ W3C DOM4]
| related_standards = 
| abbreviation      = DOM
| domain            = 
| license           = 
}}
{{HTML}} 
The '''Document Object Model''' ('''DOM''') is a [[cross-platform|cros]][[cross-platform|s-platform]]<ref name=":0" /> and [[Language-independent specification|language-independent]] [[API]] that treats an [[HTML]] or [[XML]] document as a [[tree structure]] wherein each [[Node (computer science)|node]] is an [[Object (computer science)|object]] representing a part of the document. The DOM represents a document with a logical tree. Each branch of the tree ends in a node, and each node contains objects. DOM methods allow programmatic access to the tree; with them one can change the structure, style or content of a document.<ref name=":0">{{Cite web |title=Document Object Model (DOM): definition, structure and example |url=https://www.ionos.com/digitalguide/websites/web-development/an-introduction-to-the-document-object-model-dom/ |access-date=2022-04-21 |website=IONOS Digitalguide |language=en}}</ref> Nodes can have [[event handler]]s (also known as event listeners) attached to them. Once an event is triggered, the event handlers get executed.<ref name="Introduction">{{cite web
| access-date = 2012-01-12
| publisher = W3C 
| title = Document Object Model (DOM)
| quote = The Document Object Model is a platform- and language-neutral interface that will allow programs and scripts to dynamically access and update the content, structure and style of documents. 
| url = http://www.w3.org/DOM/#what}}</ref>

The principal standardization of the DOM was handled by the [[World Wide Web Consortium]] (W3C), which last developed a recommendation in 2004. [[WHATWG]] took over the development of the standard, publishing it as a [[living document]]. The W3C now publishes stable snapshots of the WHATWG standard.

In HTML DOM (Document Object Model), every element is a node:<ref>{{cite web | url=https://www.w3schools.com/js/js_htmldom.asp | title=JavaScript HTML DOM }}</ref>

* A document is a document node.
* All HTML elements are element nodes.
* All HTML attributes are attribute nodes.
* Text inserted into HTML elements are text nodes.
* Comments are comment nodes.

==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 language]]s to be widely [[Implementation|implemented]] in the [[JavaScript engine]]s of [[web browser]]s.

JavaScript was released by [[Netscape Communications]] in 1995 within Netscape Navigator 2.0. Netscape's competitor, [[Microsoft]], released [[Internet Explorer 3|Internet Explorer 3.0]] the following year with a reimplementation of JavaScript called JScript. JavaScript and JScript let [[web developer]]s create web pages with [[client-side]] interactivity. The limited facilities for detecting user-generated [[Event (computing)|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 specifications for [[HTML4|HTML 4]].

Legacy DOM was limited in the kinds of [[HTML element|element]]s that could be accessed. [[Form (web)|Form]], [[Hyperlink|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 [[Sequence|sequential index]] of the traversed elements. For example, a [[Text box|form input element]] could be accessed as either <code>document.myForm.myInput</code> or <code>document.forms[0].elements[0]</code>.

The Legacy DOM enabled client-side form validation and simple interface interactivity like creating [[tooltip]]s.

In 1997, Netscape and Microsoft released version 4.0 of Netscape Navigator and Internet Explorer respectively, 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".

After the standardization of [[ECMAScript]], the [[World Wide Web Consortium|W3C]] DOM Working Group began drafting a standard DOM specification. The completed specification, known as "DOM Level 1", became a W3C Recommendation in late 1998. By 2005, large parts of W3C DOM were well-supported by common ECMAScript-enabled browsers, including [[Internet Explorer 6]] (from 2001), [[Opera (web browser)|Opera]], [[Safari (web browser)|Safari]] and [[Gecko (layout engine)|Gecko]]-based browsers (like [[Mozilla Application Suite|Mozilla]], [[Mozilla Firefox|Firefox]], [[SeaMonkey]] and [[Camino (web browser)|Camino]]).

==Standards==
[[File:WHATWG DOM.png|thumb|WHATWG DOM]]
The [[W3C]] DOM Working Group published its final recommendation and subsequently disbanded in 2004. Development efforts migrated to the [[WHATWG]], which continues to maintain a living standard.<ref>{{cite web|url=https://dom.spec.whatwg.org/|title=DOM Standard|access-date=23 September 2016}}</ref> In 2009, the Web Applications group reorganized DOM activities at the W3C.<ref>{{cite web|url=https://www.w3.org/DOM/|title=W3C Document Object Model|access-date=23 September 2016}}</ref> In 2013, due to a lack of progress and the impending release of [[HTML5]], the DOM Level 4 specification was reassigned to the [[HTML Working Group]] to expedite its completion.<ref>{{cite web|url=https://lists.w3.org/Archives/Public/public-html-admin/2013Sep/0129.html|title=New Charter for the HTML Working Group from Philippe Le Hegaret on 2013-09-30 (public-html-admin@w3.org from September 2013)|first=Philippe Le Hegaret|last=(plh@w3.org)|access-date=23 September 2016}}</ref> Meanwhile, in 2015, the Web Applications group was disbanded and DOM stewardship passed to the Web Platform group.<ref>{{cite web|url=https://www.w3.org/2008/webapps/wiki/PubStatus|title=PubStatus - WEBAPPS|access-date=23 September 2016}}</ref> Beginning with the publication of DOM Level 4 in 2015, the W3C creates new recommendations based on snapshots of the WHATWG standard.

* DOM Level 1 provided a complete model for an entire HTML or [[XML]] document, including the means to change any portion of the document.
* DOM Level 2 was published in late 2000. It introduced the <code>getElementById</code> function as well as an [[DOM Events|event model]] and support for [[XML namespace]]s and CSS.
* DOM Level 3, published in April 2004, added support for [[XPath]] and keyboard [[event handling]], as well as an interface for [[serialization|serializing]] documents as XML.
* HTML5 was published in October 2014.  Part of HTML5 had replaced DOM Level 2 HTML module.
* DOM Level 4 was published in 2015 and retired in November 2020.<ref>{{cite web|url=https://www.w3.org/standards/history/dom40/|title=W3C DOM4 publication history|date=3 November 2020 |access-date=10 August 2024}}</ref>
* [https://dom.spec.whatwg.org/review-drafts/2020-06/ DOM 2020-06] was published in September 2021 as a W3C Recommendation.<ref>{{cite web|url=https://www.w3.org/standards/history/dom/|title=DOM publication history|date=28 September 2021 |access-date=10 August 2024}}</ref> It is a snapshot of the WHATWG living standard.

==Applications==
===Web browsers===
To [[Web browser engine|render]] a document such as a HTML page, most web browsers use an internal model similar to the DOM. The nodes of every document are organized in a [[tree structure]], called the ''DOM tree'', with the topmost node named as "Document object". When an HTML page is rendered in browsers, the browser downloads the HTML into local memory and automatically parses it to display the page on screen. However, the DOM does not necessarily need to be represented as a tree,<ref name="Level3-Introduction">{{cite web|url=https://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/introduction.html|title=What is the Document Object Model?|access-date=2021-09-12|publisher=W3C|quote=However, the DOM does not specify that documents must be implemented as a tree or a grove, nor does it specify how the relationships among objects be implemented. The DOM is a logical model that may be implemented in any convenient manner.}}</ref> and some browsers have used other internal models.<ref name="Modernizing-Dom">{{cite web|url=https://blogs.windows.com/msedgedev/2017/04/19/modernizing-dom-tree-microsoft-edge/|title=Modernizing the DOM tree in Microsoft Edge|date=19 April 2017|access-date=2021-09-12|publisher=Microsoft}}</ref>

===JavaScript===
When a web page is loaded, the browser creates a Document Object Model of the page, which is an object oriented representation of an HTML document that acts as an interface between JavaScript and the document itself. This allows the creation of [[dynamic web page]]s,<ref>{{cite web|url=https://www.w3schools.com/js/js_htmldom.asp|title=JavaScript HTML DOM|access-date=23 September 2016}}</ref> because within a page JavaScript can:

* add, change, and remove any of the HTML elements and attributes
* change any of the CSS styles
* react to all the existing events
* create new events

== DOM tree structure ==
A Document Object Model (DOM) tree is a hierarchical representation of an HTML or [[XML]] document. It consists of a root node, which is the document itself, and a series of child nodes that represent the elements, attributes, and text content of the document. Each node in the tree has a parent node, except for the root node, and can have multiple child nodes.

=== Elements as nodes ===
Elements in an HTML or XML document are represented as nodes in the DOM tree. Each element node has a tag name and attributes, and can contain other element nodes or text nodes as children. For example, an HTML document with the following structure:<syntaxhighlight lang="html">
<html>
  <head>
    <title>My Website</title>
  </head>
  <body>
    <h1>Welcome to DOM</h1>
    <p>This is my website.</p>
  </body>
</html>
</syntaxhighlight>will be represented in the DOM tree as:<syntaxhighlight lang="text">
- Document (root)
  - html
    - head
      - title
        - "My Website"
    - body
      - h1
        - "Welcome to DOM"
      - p
        - "This is my website."

</syntaxhighlight>

=== Text nodes ===
Text content within an element is represented as a text node in the DOM tree. Text nodes do not have attributes or child nodes, and are always leaf nodes in the tree. For example, the text content "My Website" in the title element and "Welcome" in the h1 element in the above example are both represented as text nodes.

=== Attributes as properties ===
Attributes of an element are represented as properties of the element node in the DOM tree. For example, an element with the following HTML:<syntaxhighlight lang="html">
<a href="https://example.com">Link</a>
</syntaxhighlight>will be represented in the DOM tree as:<syntaxhighlight lang="text">
- a
  - href: "https://example.com"
  - "Link"

</syntaxhighlight>

== Manipulating the DOM tree ==
The DOM tree can be manipulated using JavaScript or other programming languages. Common tasks include navigating the tree, adding, removing, and modifying nodes, and getting and setting the properties of nodes. The DOM API provides a set of methods and properties to perform these operations, such as <code>getElementById</code>, <code>createElement</code>, <code>appendChild</code>, and <code>innerHTML</code>.<syntaxhighlight lang="javascript">
// Create the root element
var root = document.createElement("root");

// Create a child element
var child = document.createElement("child");

// Add the child element to the root element
root.appendChild(child);

</syntaxhighlight>Another way to create a DOM structure is using the innerHTML property to insert HTML code as a string, creating the elements and children in the process. For example:<syntaxhighlight lang="javascript">
document.getElementById("root").innerHTML = "<child></child>";
</syntaxhighlight>Another method is to use a JavaScript library or framework such as [[jQuery]], [[AngularJS]], [[React (JavaScript library)|React]], [[Vue.js]], etc. These libraries provide a more convenient, eloquent and efficient way to create, manipulate and interact with the DOM.

It is also possible to create a DOM structure from an XML or JSON data, using JavaScript methods to parse the data and create the nodes accordingly.

Creating a DOM structure does not necessarily mean that it will be displayed in the web page, it only exists in memory and should be appended to the document body or a specific container to be rendered.

In summary, creating a DOM structure involves creating individual nodes and organizing them in a hierarchical structure using JavaScript or other programming languages, and it can be done using several methods depending on the use case and the developer's preference.

==Implementations==
Because the DOM supports navigation in any direction (e.g., parent and previous sibling) and allows for arbitrary modifications, implementations typically buffer the document.<ref>{{Cite book|url=https://books.google.com/books?id=HuSQGrRY7F4C|title=Ajax Black Book, New Edition (With Cd)|last=Kogent Solutions Inc.|publisher=Dreamtech Press|year=2008|isbn=978-8177228380|pages=40}}</ref> However, a DOM need not originate in a serialized document at all, but can be created in place with the DOM API. And even before the idea of the DOM originated, there were implementations of equivalent structure with persistent disk representation and rapid access, for example [[DynaText]]'s model disclosed in <ref>{{cite patent| country	= USA| number	= 5557722A| invent1	= Steven DeRose| invent2	= Jeffrey Vogel| status	= Expired| title = Data processing system and method for representing, generating a representation of and random access rendering of electronic documents | pubdate	= 1996-09-17}}</ref> and various database approaches.

===Layout engines===

Web browsers rely on [[web browser engine|layout engine]]s to parse HTML into a DOM. Some layout engines, such as [[Trident (layout engine)|Trident/MSHTML]], are associated primarily or exclusively with a particular browser, such as Internet Explorer. Others, including [[Blink (layout engine)|Blink]], [[WebKit]], and [[Gecko (layout engine)|Gecko]], are shared by a number of browsers, such as [[Google Chrome]], [[Opera (web browser)|Opera]], [[Safari (web browser)|Safari]], and [[Firefox]]. The different layout engines implement the DOM standards to varying degrees of compliance.

===Libraries===
DOM implementations:

* [[libxml2]]
* [[MSXML]]
* [[Apache Xerces|Xerces]] is a collection of DOM implementations written in C++, Java and Perl
* [https://docs.python.org/3/library/xml.dom.html xml.dom] for [[Python (programming language)|Python]] 
* XML for &lt;SCRIPT&gt; is a JavaScript-based DOM implementation<ref>{{cite web|url=http://xmljs.sourceforge.net/|title=XML for <SCRIPT> Cross Platform XML Parser in JavaScript|access-date=23 September 2016}}</ref>
* [https://github.com/PhpGt/Dom PHP.Gt DOM] is a server-side DOM implementation based on [[libxml2]] and brings DOM level 4 compatibility<ref>{{cite web|url=https://php.gt/dom#features-at-a-glance|title=The modern DOM API for PHP 7 projects|date=5 December 2021}}</ref> to the [[PHP]] programming language
* [https://github.com/fgnass/domino/ Domino] is a Server-side (Node.js) DOM implementation based on Mozilla's dom.js. Domino is used in the [[MediaWiki]] stack with Visual Editor.
* [https://github.com/wooly905/SimpleHtmlDom/ SimpleHtmlDom] is a simple HTML document object model in C#, which can generate HTML string programmatically.

APIs that expose DOM implementations:

* [[Java API for XML Processing|JAXP]] (Java API for XML Processing) is an API for accessing DOM providers
* [[Lazarus (IDE)|Lazarus]] ([[Free Pascal]] IDE) contains two variants of the DOM - with UTF-8 and ANSI format

Inspection tools:

* [[DOM Inspector]] is a web developer tool

== See also ==

* [[Shadow DOM]]
* [[Virtual DOM]]

==References==
{{Reflist}}

===General references===
*{{cite book
  | last = Flanagan
  | first = David
  | title = JavaScript: The Definitive Guide
  | url = https://archive.org/details/javascript00libg_297
  | url-access = limited
  | publisher = O'Reilly & Associates
  | year = 2006
  | pages = [https://archive.org/details/javascript00libg_297/page/n310 312]–313
  | isbn = 0-596-10199-6 }}
*{{cite web
  | last = Koch
  | first = Peter-Paul
  | title = The Document Object Model: an Introduction
  | work = Digital Web Magazine
  | date = May 14, 2001
  | url = http://www.digital-web.com/articles/the_document_object_model/
  | archive-url = https://web.archive.org/web/20170427220310/http://www.digital-web.com/articles/the_document_object_model/
  | archive-date = April 27, 2017
  | access-date = January 10, 2009 }}
*{{cite web
  | last = Le Hégaret
  | first = Philippe
  | title = The W3C Document Object Model (DOM)
  | publisher = World Wide Web Consortium
  | year = 2002
  | url = http://www.w3.org/2002/07/26-dom-article.html
  | access-date = January 10, 2009 }}
*{{cite web
  | last = Guisset
  | first = Fabian
  | title = What does each DOM Level bring?
  | publisher = Mozilla Project
  | work = Mozilla Developer Center
  | url = https://developer.mozilla.org/en/docs/DOM_Levels
  | access-date = January 10, 2009
  | archive-date = March 2, 2013
  | archive-url = https://web.archive.org/web/20130302191641/https://developer.mozilla.org/en/docs/DOM_Levels
  | url-status = dead
  }}

==External links==
{{Commons category|Document object models|lcfirst=yes}}

* [https://dom.spec.whatwg.org/ DOM Living Standard] by the WHATWG
* [https://www.w3.org/DOM/ Original W3C DOM hub] by the W3C DOM Working Group (outdated)
* [https://www.w3.org/standards/history/dom Latest snapshots of the WHATWG living standard] published by the W3C HTML Working Group
* [https://www.w3.org/WebPlatform/WG/ Web Platform Working Group] (current steward of W3C DOM)

{{JavaScript}}
{{Web browsers|fsp}}
{{W3C Standards}}
{{Web interfaces}}
{{Authority control}}

{{DEFAULTSORT:Document Object Model}}
[[Category:Application programming interfaces]]
[[Category:HTML]]
[[Category:Object models]]
[[Category:World Wide Web Consortium standards]]
[[Category:XML-based standards]]