The objective associated with internet Applications performing Group (Web WG) would be to create specs that facilitate the development 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 phone phone calls is likely to be held whenever required. Face-to-face: we are going to fulfill throughout the W3C’s yearly Technical Plenary week; extra meetings that are face-to-face be planned by permission of individuals. |
Range
The range associated with internet performing Group is:
- Haptic input products and their emitted activities and/or information.
- Textual text and input manipulation.
- Information sharing across remote and web that is local.
- Getting and acting upon information from remote sources.
- Accessing the file system and persistent storage space.
- Interfacing with OS abilities.
- Integrating internet applications with all 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 setting ARIA characteristics. The performing Group will not expect you’ll include any kind of specs with this matter.
Requirements created by the internet Working Group allow developers to generate web applications that really work across a range that is wide of and devices, as well as an easy variety of users, by handling issues of accessibility, unit liberty, internationalization, privacy, and security.
Success Criteria
So that you can advance to Proposed Recommendation, each specification will need to have at the least two separate implementations in wide usage.
Each specification should have an accompanying test suite, that will be 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 can find implications for implementors, designers, or users, into the aspects of accessibility, internationalization, privacy, and security, each specification will need to have an area that defines appropriate advantages, restrictions, and most readily useful practice solutions for the specific area.
Deliverables
Extra information about online performing Group requirements are available in the GitHub repository.
Normative Specs
The net performing Group will provide the after specifications that are normative.
| Specification | definition |
|---|---|
| File API | An API for representing objects that are file internet applications, along with programmatically choosing them and accessing their information. |
| Gamepad API | |
| Indexed Database API | An API for the database of documents keeping easy values and objects that are hierarchical. The third edition adds brand new abilities and improves designer ergonomics by utilizing claims. |
| Intersection Observer | An API which can be used 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 scripted usage of natural mouse movement information 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 messages to an internet application, using a push solution. |
| Screen Orientation API | An API for reading display orientation, being informed of display orientation modifications, and locking display orientation to a particular state. |
| online App Manifest | A JSON-based manifest file providing you with developers with a central spot to place metadata connected with a internet application. |
| Clipboard API and Events | An API for accessing data in the system clipboard. |
| Input Activities | |
| Selection API | APIs for selection, which enable users and writers to choose a percentage of a document or specify point of great interest for content, paste, along with other modifying operations. |
| ContentEditable | granted values and expected habits for the contenteditable characteristic. |
| 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 internet designer guidelines (writer conformance demands) for ARIA features on HTML elements. |
| UI Events | UI occasions 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 understood to be 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 requirements
With regards to the WICG progress, the Group could also create W3C strategies for the after documents:
| Specification | explanation |
|---|---|
| Cookie shop | An asynchronous Javascript snacks API for papers and employees. |
| internet Share API | An API for sharing text, links as well as other content to a destination that is arbitrary of individual’s option. |
| online Share Target | An API which allows sites to declare on their own as internet share goals, which could get provided content from either the Web Share API, or system activities ( ag e.g., stocks from indigenous ). |
| Badging | An API enabling web applications to create an application-wide badge, shown in a operating-system-specific destination from the application (for instance the rack or house display screen), for the true purpose of notifying the consumer as soon as the state associated with application changed ( ag e.g., whenever brand brand new messages have actually appeared), without showing a far more notification that is heavyweight. |