The objective regarding the internet Applications performing Group (Web WG) would be to produce specs 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 will undoubtedly be held whenever required. Face-to-face: we’re going to satisfy throughout the W3C’s yearly Technical Plenary week; extra meetings that are face-to-face be planned by permission of participants. |
Range
The range associated with the Web performing Group is:
- Haptic input products and their emitted occasions and/or information.
- Textual text and input manipulation.
- Information sharing across remote and web that is local.
- Acting and receiving upon data 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 writer conformance demands for establishing ARIA characteristics. The performing Group will not expect you’ll include just about any specs concerning this matter.
Specs made by the internet Working Group help developers to produce internet applications that really work across a range that is wide of and products, as well as for a broad variety of users, by handling things of accessibility, unit freedom, internationalization, privacy, and safety.
Success Criteria
Each specification must have at least two independent implementations in wide use in order to advance to Proposed Recommendation.
Each specification should have an accompanying test suite, that is preferably developed in parallel to your specification. The test suite will be employed to produce an implementation report ahead of the specification transitions to Proposed Recommendation.
Where you can find implications for implementors, developers, or users, when you look at the regions of accessibility, internationalization, privacy, and protection, each specification will need to have a area that defines appropriate advantages, limits, and most useful training solutions for that specific area.
Deliverables
Additional information about Web performing Group requirements are available in the GitHub repository.
Normative Requirements
The internet performing Group will deliver the after specifications that are normative.
| Specification | explanation |
|---|---|
| File API | An API for representing objects that are file web applications, in addition to programmatically picking them and accessing their information. |
| Gamepad API | |
| Indexed Database API | An API for the database of records keeping easy values and objects that are hierarchical. The edition that is third brand brand new capabilities and improves designer ergonomics simply by using claims. |
| Intersection Observer | An API which you can use to know the presence and place of DOM elements (“targets”) general to a containing element or into the top-level viewport (“root”). |
| Pointer Lock | An API providing you with scripted usage of natural mouse movement information while securing the prospective of mouse events to just one element and getting rid of the cursor from view. |
| drive API | An API for sending push messages 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 to a state that is specific. |
| internet App Manifest | A JSON-based manifest file that delivers designers with a central spot to put metadata related to an internet application. |
| Clipboard API and Events | An API for accessing information from the system clipboard. |
| Input Occasions | |
| Selection API | APIs for selection, which enable users and writers to pick a percentage of the document or specify point of great interest for copy, paste, along with other modifying operations. |
| ContentEditable | granted values and anticipated habits for the contenteditable feature. |
| HTML Accessibility API Mappings (AAM) | Defines how user agents map HTML elements and attributes to platform accessibility APIs. |
| ARIA in HTML | Defines the internet designer guidelines (writer conformance demands) for ARIA features on HTML elements. |
| UI Events | UI occasions 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, which will be thought as an element of the UI Events Specification. |
| UI Events KeyboardEvent key Values | The values when it comes to attribute that is key into the UI Activities specification. |
WICG specs
According to the WICG progress, the Group could also create W3C tips for the following documents:
| Specification | explanation |
|---|---|
| Cookie shop | An asynchronous Javascript snacks API for papers and workers. |
| Web Share API | An API for sharing text, links along with other content to an arbitrary location associated with the individual’s option. |
| online Share Target | An API which allows internet sites to declare on their own as internet share targets, that may get provided content from either the Web Share API, or system activities ( ag e.g., stocks from indigenous ). |
| Badging | An API enabling internet applications to create an application-wide badge, shown in a operating-system-specific destination linked to the application (including the rack or home display screen), for the intended purpose of notifying the consumer once the state for the application changed ( e.g., when brand brand new communications have actually appeared), without showing a far more notification that is heavyweight. |