XMLHttpRequest Level 2. Abstract The XMLHttpRequest specification defines an API that provides scripted client functionality for transferring data between a client and a server. 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 is published as a snapshot of the XMLHttpRequest Living Specification.
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, or please send comments to public-webapps@w3.org (archived) with [XHR] at the start of the subject line. The W3C Web Applications Working Group is the W3C working group responsible for this specification's progress along the W3C Recommendation track. Work on this specification is also done at the WHATWG. The. Selectors API Level 1. Abstract Selectors, which are widely used in CSS, are patterns that match against elements in a tree structure [SELECT][CSS21]. The Selectors API specification defines methods for retrieving Element nodes from the DOM by matching against a group of selectors. It is often desirable to perform DOM operations on a specific set of elements in a document. These methods simplify the process of acquiring specific elements, especially compared with the more verbose techniques defined and used in the past.
Status of this Document This section describes the status of this document at the time of its publication. The Web Applications (WebApps) Working Group has developed a comprehensive Selectors API test suite and has demonstrated interoperability of the features among implementations. Please send comments about this document to public-webapps@w3.org (public archive) with [selectors-api] in the subject. This document was developed by the Web Applications Working Group. Table of Contents 1. 1.1. 2. C WebApps Working Group. Network Communication API. Abstract To enable Web applications to communicate using TCP this specification introduces the TCPSocket interface and a corresponding optional security model. 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 is a first editors' draft specification of the network API from the Web API group, part of the Rich Web Client Activity.
This document is published to solicit comments from interested parties. This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. Publication as a Working Draft does not imply endorsement by the W3C Membership. Table of Contents Introduction This interface does not allow for raw access to the underlying network. Provide an example here The TCPSocket object The peer . Web IDL. This section describes a language, Web IDL, which can be used to define interfaces for APIs in the Web platform. A specification that defines Web APIs can include one or more IDL fragments that describe the interfaces (the state and behavior that objects can exhibit) for the APIs defined by that specification.
An IDL fragment is a sequence of definitions that matches the Definitions grammar symbol. Each definition (matching Definition) can be preceded by a list of extended attributes (matching ExtendedAttributeList), which can control how the definition will be handled in language bindings. 3.1. Every interface, partial interface definition, dictionary, partial dictionary definition, exception, enumeration, callback function and typedef (together called named definitions ) and every constant, attribute, exception field and dictionary member has an identifier , as do some operations. Operation arguments can take a slightly wider set of identifiers. Reserved identifiers 3.2. Interface inherit The. File API. Abstract This specification provides an API for representing file objects in web applications, as well as programmatically selecting them and accessing their data.
This includes: A FileList interface, which represents an array of individually selected files from the underlying system. The user interface for selection can be invoked via <input type="file">, i.e. when the input element is in the File Upload state [HTML] . A Blob interface, which represents immutable raw binary data, and allows access to ranges of bytes within the Blob object as a separate Blob. A File interface, which includes readonly informational attributes about a file such as its name and the date of the last modification (on disk) of the file. Additionally, this specification defines objects to be used within threaded web applications for the synchronous reading of files. The section on Requirements and Use Cases [REQ] covers the motivation behind this specification.
Status of this Document 1. ECMAScript 1.1 Model ΒΆ 2. C Web API Working Group. Element Traversal Specification. Abstract This specification defines the ElementTraversal interface, which allows script navigation of the elements of a DOM tree, excluding all other nodes in the DOM, such as text nodes. It also provides an attribute to expose the number of child elements of an element. It is intended to provide a more convenient alternative to existing DOM navigation interfaces, with a low implementation footprint. 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 is the 22 December 2008 Recommendation of the Element Traversal specification.
This document has been reviewed by W3C Members, by software developers, and by other W3C groups and interested parties, and is endorsed by the Director as a W3C Recommendation. 1. 1.1. 1.2. 2. 3. 3.1. 3.2. Clipboard API and events. Abstract This document describes APIs for clipboard operations such as copy, cut and paste in web applications. 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 Web Applications Working Group as a Working Draft. This document is intended to become a W3C Recommendation. Publication as a Working Draft does not imply endorsement by the W3C Membership.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. Table of Contents 1. As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. 2. This section is non-normative. 3. 3.1 Rich content editing 3.2 Graphics with built-in semantics 4. 5.