The objective associated with 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 phone telephone calls will likely to be held whenever required. Face-to-face: we’re going to satisfy throughout the W3C’s annual Technical Plenary week; extra meetings that are face-to-face be scheduled by permission of individuals. |
Range
The range of this internet performing Group is:
- Haptic input products and their emitted activities and/or information.
- Textual text and input manipulation.
- Information sharing across remote and regional internet applications.
- Getting and acting upon information from remote sources.
- Accessing the file system and persistent storage.
- Interfacing with OS abilities.
- Integrating web applications aided by the OS.
The working group additionally maintains a specification for mapping HTML elements and attributes to platform accessibility APIs, and a split specification that defines writer conformance needs for establishing ARIA characteristics. The performing Group will not expect you’ll include some other specs with this matter.
Specs made by the internet Working Group allow developers to produce internet applications that work across an extensive variety of platforms and products, as well as for an easy variety of users, by handling things of accessibility, unit self-reliance, 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 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 prior to the specification transitions to Proposed Recommendation.
Where you can find implications for implementors, designers, or users, within the aspects of accessibility, internationalization, mennation giriЕџ privacy, and safety, each specification will need to have a part that defines relevant advantages, restrictions, and most readily useful training solutions for the specific area.
Deliverables
Extra information about internet Working Group requirements are available in the GitHub repository.
Normative Requirements
The internet performing Group will provide the after specifications that are normative.
| Specification | explanation |
|---|---|
| File API | An API for representing file things in web applications, along with programmatically picking them and accessing their information. |
| Gamepad API | |
| Indexed Database API | An API for a database of documents holding easy values and hierarchical things. The edition that is third brand brand new abilities and improves designer ergonomics making use of promises. |
| Intersection Observer | An API which you can use to know the exposure and place of DOM elements («targets») relative to an element that is containing to your top-level viewport («root»). |
| Pointer Lock | An API providing you with scripted usage of natural mouse movement information while locking the goal of mouse activities to an individual 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 screen orientation, being informed of display screen orientation changes, and securing display orientation up to a certain state. |
| internet App Manifest | A JSON-based manifest file that delivers designers by having a central location to put metadata connected with a internet application. |
| Clipboard API and Events | An API for accessing information regarding the operational system clipboard. |
| Input Activities | |
| Selection API | APIs for selection, which enable users and writers to choose a percentage of the document or specify a true point of great interest for content, paste, along with other modifying operations. |
| ContentEditable | granted values and expected actions 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 needs) for ARIA features on HTML elements. |
| UI Events | UI occasions that increase the DOM Event objects defined into the DOM specification. |
| UI Events KeyboardEvent code values | The values for the KeyboardEvent.code characteristic, that is 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 occasions specification. |
WICG requirements
With respect to the WICG progress, the Group could also create W3C tips for the after documents:
| Specification | explanation |
|---|---|
| Cookie shop | An asynchronous Javascript cookies API for papers and employees. |
| online Share API | An API for sharing text, links as well as other content to an arbitrary location regarding the user’s option. |
| internet Share Target | An API which allows web sites to declare on their own as internet share objectives, that could get provided content from either the Web Share API, or system activities ( e.g., stocks from indigenous ). |
| Badging | An API enabling internet applications to create an application-wide badge, shown in a operating-system-specific spot from the application (like the rack or house display screen), for the intended purpose of notifying the consumer once the state associated with application changed ( ag e.g., when new communications have actually appeared), without showing a far more notification that is heavyweight. |
