The objective of this online Applications performing Group (Web WG) is always to create requirements that facilitate the introduction of client-side web applications.
|Start date||14 May 2019|
|End date||31 May 2021|
|Chairs||LГ©onie Watson (TetraLogical), Marcos CГЎceres (Mozilla)|
|Team Contacts||Xiaoqian Wu (0.1 FTE )|
|Meeting Schedule||Teleconferences: topic-specific phone phone calls are going to be held whenever required. Face-to-face: we are going to satisfy through the W3C’s yearly Technical Plenary week; extra face-to-face conferences may be planned by permission of individuals.|
The range regarding the online performing Group is:
- Haptic input products and their emitted occasions and/or information.
- Textual input and text manipulation.
- Information sharing across remote and regional internet applications.
- Getting and acting upon information from remote sources.
- Accessing the file system and storage that is persistent.
- Interfacing with OS abilities.
- Integrating internet applications using the OS.
The working group additionally keeps a specification for mapping HTML elements and attributes to platform accessibility APIs, and a split specification that describes author conformance demands for establishing ARIA attributes. The Working Group will not expect you’ll include any kind of specs concerning this matter.
Specs made by the net Working Group make it possible for developers to generate internet applications that really work across a range that is wide of and products, as well as a broad variety of users, by handling issues of accessibility, unit independency, internationalization, privacy, and protection.
Each specification must have at least two independent implementations in wide use in order to advance to Proposed Recommendation.
Each specification will need to have a test that is accompanying, that is preferably developed in parallel into the specification. The test suite will be employed to produce an execution report prior to the specification transitions to Proposed Recommendation.
Where you will find implications for implementors, designers, or users, into the aspects of accessibility, internationalization, privacy, and safety, each specification should have an area that defines appropriate benefits, restrictions, and most useful training solutions for that specific area.
More details about internet performing Group requirements are located in the GitHub repository.
The internet Working Group will provide the after normative specs.
|File API||An API for representing file things in internet applications, in addition to programmatically picking them and accessing their data.|
|Indexed Database API||An API for the database of documents keeping easy values and hierarchical things. The 3rd version adds brand brand new abilities and improves designer ergonomics simply by using claims.|
|Intersection Observer||An API which you can use to know the presence and position of DOM elements (“targets”) general to a containing element or into the top-level viewport (“root”).|
|Pointer Lock||An API providing you with access that is scripted natural mouse movement information while securing the mark of mouse activities to just one element and getting rid of the cursor from view.|
|Push API||An API for giving push communications to an internet application, via a push solution.|
|Screen Orientation API||An API for reading display screen orientation, being informed of display screen orientation modifications, and securing display screen orientation up to a certain state.|
|online App Manifest||A JSON-based manifest file providing you with designers with a central spot to put metadata related to a internet application.|
|Clipboard API and Events||An API for accessing data from the system clipboard.|
|Selection API||APIs for selection, which allow users and writers to choose a percentage of a document or specify point of great interest for content, paste, as well as other modifying operations.|
|ContentEditable||granted values and expected behaviors for the attribute that is contenteditable.|
|HTML Accessibility API Mappings (AAM)||Defines exactly exactly how user agents map HTML elements and attributes to platform accessibility APIs.|
|ARIA in HTML||Defines the net designer guidelines (writer conformance needs) for ARIA features on HTML elements.|
|UI Events||UI Activities that increase the DOM Event objects defined when you look at the DOM specification.|
|UI Events KeyboardEvent code values||The values for the KeyboardEvent.code feature, that will be understood to be an element of the UI Events Specification.|
|UI Events KeyboardEvent key Values||The values when it comes to key characteristic defined into the UI occasions specification.|
With respect to the WICG progress, the Group might also create W3C strategies for the after documents:
|online Share API||An API for sharing text, links as well as other content to a destination that is arbitrary of individual’s option.|
|internet Share Target||An API which allows sites to declare on their own as internet share goals, that could get provided content from either the Web Share API, or system activities ( ag e.g., stocks from native ).|
|Badging||An API permitting internet applications to create an application-wide badge, shown in a operating-system-specific destination linked to the application (including the shelf or house display), for the intended purpose of notifying an individual as soon as the state for the application changed ( ag e.g., when brand brand new communications have actually appeared), without showing an even more heavyweight notification.|