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. 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. 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.
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. 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 The TCPSocket interface enables a TCP connection from the client to the server from which the script was downloaded and executed from. This interface does not allow for raw access to the underlying network. Provide an example here The TCPSocket object The TCPSocket constructor The .
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. 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. Operations can have no identifier when they are being used to declare a special kind of operation, such as a getter or setter. Operation arguments can take a slightly wider set of identifiers. 3.2. 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] . 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. This API is designed to be used in conjunction with other APIs and elements on the web platform, notably: XMLHttpRequest (e.g. with an overloaded send() method for File or Blob objects), postMessage, DataTransfer (part of the drag and drop API defined in [HTML,]) and Web Workers. Status of this Document This draft is a Last Call Working Draft. 1. 2.
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. 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. The Web Applications (WebApps) Working Group has produced a test suite and implementation report to indicate the current level of implementation support for this specification, with passing results for all tests. 1. 1.1. 1.2. 2. 3.
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. 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. There are many use cases for being able to change the default clipboard operations (cut/copy/paste). 4. 5. 5.1.1 copy event
