The objective for the internet Applications performing Group (Web WG) would be to create requirements that facilitate the introduction of client-side internet 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 telephone telephone calls would be held whenever needed. Face-to-face: we shall fulfill throughout the W3C’s yearly Technical Plenary week; extra meetings that are face-to-face be planned by permission of individuals. |
Scope
The range associated with the online performing Group is:
- Haptic input products and their emitted occasions and/or information.
- Textual text and input manipulation.
- Data sharing across remote and web that is local.
- Acting and receiving upon data from remote sources.
- Accessing the file system and persistent storage space.
- Interfacing with OS abilities.
- Integrating internet applications utilizing the OS.
The working group also keeps a specification for mapping HTML elements and attributes to platform accessibility APIs, and a split specification that describes writer conformance needs for setting ARIA characteristics. The performing Group will not expect to include virtually any specs with this matter.
Requirements made by the net Working Group permit 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 freedom, internationalization, privacy, and protection.
Success Criteria
To be able to advance to Proposed Recommendation, each specification will need to have at the very least two separate implementations in wide usage.
Each specification should have a test that is accompanying, that is preferably developed in parallel towards the specification. The test suite will be employed to create an execution report ahead of the specification transitions to Proposed Recommendation.
Where you will find implications for implementors, designers, or users, within the regions of accessibility, internationalization, privacy, and protection, each specification will need to have an area that defines appropriate advantages, limits, and practice solutions that are best for the specific area.
Deliverables
More details about internet performing Group specs are available in the GitHub repository.
Normative Requirements
The Web performing Group will deliver the after normative requirements.
| Specification | explanation |
|---|---|
| File API | An API for representing file things in internet applications, along with programmatically choosing them and accessing their information. |
| Gamepad API | |
| Indexed Database API | An API for a database of documents keeping easy values and hierarchical items. The 3rd version adds brand brand brand new abilities and improves designer ergonomics by utilizing claims. |
| Intersection Observer | An API which you can use to know the exposure 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 access that is scripted natural mouse movement data while securing the prospective of mouse activities to just one element and getting rid of the cursor from view. |
| drive API | An API for giving push communications to an internet application, via a push solution. |
| Screen Orientation API | An API for reading display orientation, being informed of display screen orientation modifications, and securing display orientation up to a particular state. |
| internet App Manifest | A JSON-based manifest file providing you with designers with a central destination to place metadata connected with an internet application. |
| Clipboard API and Events | An API for accessing information in the system clipboard. |
| Input Activities | |
| Selection API | APIs for selection, which enable users and writers to pick a percentage of a document or specify point of great interest for content, paste, along with other editing operations. |
| ContentEditable | Allowed values and anticipated actions for the attribute that is contenteditable. |
| HTML Accessibility API Mappings (AAM) | Defines exactly 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 Activities that increase the DOM Event objects defined within the DOM specification. |
| UI Events KeyboardEvent code values | The values for the KeyboardEvent.code characteristic, which will be thought as area of the UI Events Specification. |
| UI Events KeyboardEvent key Values | The values when it comes to attribute that is key when you look at the UI Activities specification. |
WICG specs
With regards to the WICG progress, the Group might also create W3C tips for the documents that are following
| Specification | definition |
|---|---|
| Cookie Store | An asynchronous Javascript snacks API for papers and employees. |
| online Share API | An API for sharing text, links along with 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 objectives, that may get shared content from either the Web Share API, or system activities ( e.g., stocks from indigenous ). |
| 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 screen), for the true purpose of notifying the consumer once the state regarding the application changed ( e.g., when brand brand new communications have actually appeared), without showing an even more notification that is heavyweight. |