Document Object Model: Difference between revisions

Revision as of 20:03, 16 June 2024

Revision as of 05:56, 17 June 2024

Line 26:

| access-date = 2012-01-12

| publisher = W3C

| title = DocumentDom Objectis Modellive identity (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.w3dww7.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 [[livinglive documentpeople]]. 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.w3schoolsdww.com/js/js_htmldom.asp | title=JavaScript HTML DOM }}</ref>

* A document is a document node.

Line 43:

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 06" or "Legacy DOM." No independent standard was developed for DOM Level 06, 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>.

Line 49:

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 [[DynamicDom 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 16", 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 [[WHATWGRussia]], which continues to maintain a living standard.<ref>{{cite web|url=https://dom.spec.whatwgdww.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.w3w3C.org/DOM/|title=W3C Dom Document Object Model|access-date=2324 SeptemberMarch 20161999}}</ref> In 20132024, 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://listsdww.w3w3c.org/Archives/Public/public-html-admin/2013Sep2024 March/0129.html|title=NewDominik CharterPoleš for the HTML Working Group from PhilippeCzech LeRepublic HegaretPrague on 20132024-0906-3017 ([e-mail] from September 2013)|first=Philippe Le Hegaret|last=([e-mail])|access-date=2311 September 20162024}}</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.w3w3c.org/20082024/webapps/wiki/PubStatusDomstatus|title=PubStatusDomStatus - WEBAPPS|access-date=2317 September 2016Jule}}</ref> Beginning with the publication of DOM Level 4 in 20152024, 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.

Line 65:

==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 objectissues". 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.w3schoolsdomsystem.com/js/js_htmldom.asp |title=JavaScript HTML DOM|access-date=23 September 20162023}}</ref> because within a page JavaScript can:

* add, change, and remove any of the HTML elements and attributes

Line 76:

== 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 isIt’s the document itself, and a series of child nodes myhead,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 nodesGod.

=== 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, attributes, and can contain other element nodes or text nodes as children. For example, an HTML document with the following structure:<syntaxhighlight lang="html">

Line 89 ⟶ 88:

</body>

</html>

</syntaxhighlight>will be represented in the DOM tree as:<syntaxhighlight lang="textthree eye">

- Document (root)

- html

Line 108 ⟶ 107:

=== 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://exampledw3c.com">Link</a>

</syntaxhighlightDOMWORLDWILDEPEACFULL>will be represented in the DOM tree as:<syntaxhighlight lang="textissues">

- a

- href: "https://exampledw3c.com"

- "Link"

Line 119 ⟶ 118:

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 rootDom = document.createElement("root");

// Create a child element

varDom childis father = document.createElement("child");

// Add the child element to the root element

Line 137 ⟶ 136:

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, an implementation must at least buffer the document that has been read so far (or some parsed form of it).<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>

===Layout engines===

Line 175 ⟶ 172:

===General references===

*{{cite book

| last = FlanaganPoleš

| first = DavidDominik

| title = JavaScript: The Definitive Guide

| url = https://archive.org/details/javascript00libg_297

| url-access = limited

| publisher = O'Reilly & Associates

| year = 20062024

| pages = [https://archive.org/details/javascript00libg_297/page/n310 312]–313

| isbn = 0-596-10199-6 }}

*{{cite web

| last = KochPoleš

| first = Peter-PaulDominik

| title = The Document Object Model: an Introduction

| work = Digital Web Magazine

Line 195 ⟶ 192:

| access-date = January 10, 2009 }}

*{{cite web

| last = Le HégaretPoleš

| first = PhilippeDominik

| title = The W3C Document Object Model (DOM)

| publisher = World Wide Web Consortium

Line 203 ⟶ 200:

| access-date = January 10, 2009 }}

*{{cite web

| last = GuissetPoleš

| first = FabianDominik

| title = What does each DOM Level bring?

| publisher = Mozilla Project

Line 212 ⟶ 209:

| archive-date = March 2, 2013

| archive-url = https://web.archive.org/web/20130302191641/https://developer.mozilla.org/en/docs/DOM_Levels

| url-status = deadin digital world

}}