Web Workers. Abstract This specification defines an API that allows Web application authors to spawn background workers running scripts in parallel to their main page.
This allows for thread-like operation with message-passing as the coordination mechanism. Multimedia. Semantics. 4 The elements of HTML — HTML5. 4 The elements of HTML. 4.3 Sections 4.3.1 The body element Categories: Sectioning root.
Contexts in which this element can be used: As the second element in an html element. Content model: Flow content. Tag omission in text/html: A body element's start tag can be omitted if the element is empty, or if the first thing inside the body element is not a space character or a comment, except if the first thing inside the body element is a meta, link, script, style, or template element. A body element's end tag can be omitted if the body element is not immediately followed by a comment.
Content attributes: Global attributes onafterprint onbeforeprint onbeforeunload onhashchange onlanguagechange onmessage onoffline ononline onpagehide onpageshow onpopstate onstorage onunload DOM interface: interface HTMLBodyElement : HTMLElement { // also has obsolete members }; HTMLBodyElement implements WindowEventHandlers; The body element represents the main content of the document. In conforming documents, there is only one body element. 4.3.2 The article.
Connectivity. The WebSocket API. Abstract This specification defines an API that enables Web pages to use the WebSocket protocol (defined by the IETF) for two-way communication with a remote host.
Status of This document This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at If you wish to make comments regarding this document in a manner that is tracked by the W3C, please submit them via using our public bug database. You can also e-mail feedback to public-webapps@w3.org (subscribe, archives), or whatwg@whatwg.org (subscribe, archives).
Notifications of changes to this specification are sent along with notifications of changes to related specifications using the following mechanisms: E-mail notifications of changes Commit-Watchers mailing list (complete source diffs): Browsable version-control record of all changes: Server-Sent Events. Abstract This specification defines an API for opening an HTTP connection for receiving push notifications from a server in the form of DOM events.
The API is designed such that it can be extended to work with other push notification schemes such as Push SMS. Status of This document This section describes the status of this document at the time of its publication. Other documents may supersede this document. If you wish to make comments regarding this document in a manner that is tracked by the W3C, please submit them via using our public bug database. You can also e-mail feedback to public-webapps@w3.org (subscribe, archives), or whatwg@whatwg.org (subscribe, archives). Notifications of changes to this specification are sent along with notifications of changes to related specifications using the following mechanisms: E-mail notifications of changes Commit-Watchers mailing list (complete source diffs): Browsable version-control record of all changes: CVSWeb interface with side-by-side diffs:
File API. Geolocation API Specification Level 2. Abstract This specification defines an API that provides scripted access to geographical location information associated with the hosting device.
Status of This Document This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at This document was published by the Geolocation Working Group as both a First Public Working Draft and Last Call Working Draft. When providing feedback, please first refer to the Editor's Draft and confirm that the issue has not been addressed already. All feedback is welcome.
Presentation.