This core language is also used in non-browser environments, for example in node.js.
What falls under the ECMAScript scope?
Among other things, ECMAScript defines:
- The language syntax (parsing rules, keywords, control flow, object literal initialization...)
- Error handling mechanisms (throw, try/catch, ability to create user-defined Error types)
- Types (boolean, number, string, function, object...)
- The global object. In a browser environment, this global object is the window object, but ECMAScript only defines the APIs, not specific to browsers, e.g. parseInt, parseFloat, decodeURI, encodeURI...
- A prototype-based inheritance mechanism
- Built-in objects and functions (JSON, Math, Array.prototype methods, Object introspection methods...)
- Strict mode
As of April 2013, the current versions of the main web browsers implement ECMAScript 5.1, but older versions are still in use that implement ECMAScript 3 and only parts of ECMAScript 5. Some resources document ECMAScript 5 browser support.
The proposed fourth edition of ECMA-262 (ECMAScript 4 or ES4) would have been the first major update to ECMAScript since the third edition was published in 1999. As of August 2008, the ECMAScript 4th edition proposal has been scaled back into a project codenamed ECMAScript Harmony, that defines among others, things like Proxies or the
const keyword. Progress can be followed here.
The Web APIs and the DOM
The WebIDL specification provides the glue between the DOM technologies and ECMAScript.
The Core of the DOM
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. Objects in the DOM tree may be addressed and manipulated by using methods on the objects. The Core Document Object Model is standardized by the W3C. It defines language-agnostic interfaces which abstract HTML and XML documents as objects and mechanisms to manipulate this abstraction. Among the things defined by the DOM, we can find:
- The document structure, a tree model, and the DOM Event architecture in DOM core: Node, Element, DocumentFragment, Document, DOMImplementation, Event, EventTarget, …
- A less rigorous definition of the DOM Event Architecture, as well as specific events in DOM events.
- Other things such as DOM Traversal and DOM Range.
From the ECMAScript point of view, objects defined in the DOM specification are called "host objects".
HTML, the Web's markup language, is specified in terms of the DOM. Layered above the abstract concepts defined in DOM Core, HTML also defines the meaning of elements. The HTML DOM includes such things as the
className property on HTML elements, or APIs such as
The HTML specification also defines restrictions on documents; for example, it requires all children of a
ul element, which represents an unordered list, to be
li elements, as those represent list items. In general, it also forbids using elements and attributes that aren't defined in a standard.
Other notable APIs
- The setTimeout and setInterval functions have been first specified on the Window interface in HTML Standard.
- XMLHttpRequest. API allowing to send asynchronous HTTP request.
- CSS Object Model. The CSSOM is used to abstract CSS rules as objects
- WebWorkers. API that allows parallel computation.
- WebSockets. API that allows low-level bidirectional communication.
- Canvas 2D Context. Drawing API for the canvas element.
Every web developer has experienced that the DOM is a mess. Browser support uniformity varies a lot from feature to feature. The main reason for this situation is the fact that many important DOM features have had very unclear, if any, specifications. Also, different web browsers have added incompatible features for overlapping use cases (like the Internet Explorer event model). The current (as of June 2011) trend is that the W3C and particularly the WHATWG are defining older features in detail, in order to improve interoperability. Following this trend, browsers are improving their implementations based on these specifications.