The objective regarding the internet Applications Working Group (Web WG) is always to produce specs 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 phone calls may be held when required. Face-to-face: we’re going to fulfill through the W3C’s yearly Technical Plenary week; extra face-to-face conferences may be planned by permission of participants. |
Range
The range associated with internet Working Group is:
- Haptic input products and their emitted occasions and/or information.
- Textual input and text manipulation.
- Information 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 using the OS.
The group that is working keeps a specification for mapping HTML elements and attributes to platform accessibility APIs, and a split specification that defines author conformance demands for setting ARIA attributes. The Working Group doesn’t be prepared to include any kind of requirements concerning this matter.
Requirements created by the internet Working Group help developers to generate web applications that really work across an extensive number of platforms and devices, as well as for a diverse variety of users, by handling issues of accessibility, unit independency, internationalization, privacy, and safety.
Success Criteria
To be able to advance to Proposed Recommendation, each specification should have at the very least two independent implementations in wide usage.
Each specification will need to have an accompanying test suite, which can be preferably developed in parallel into 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, into the aspects of accessibility, internationalization, privacy, and protection, each specification will need to have a part that defines appropriate advantages, limits, and most readily useful practice solutions for the specific area.
Deliverables
More details about internet performing Group specs are located in the GitHub repository.
Normative Specifications
The online performing Group will provide the after normative requirements.
| Specification | definition |
|---|---|
| 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 a database of documents keeping easy values and objects that are hierarchical. The 3rd version adds brand 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 towards the top-level viewport (“root”). |
| Pointer Lock | An API providing you with access that is scripted 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 a internet application, using a push solution. |
| Screen Orientation API | An API for reading display orientation, being informed of display orientation modifications, and securing display screen orientation to a state that is specific. |
| online App Manifest | A JSON-based manifest file that delivers designers with a central spot to place metadata related to 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 a true point of great interest for content, paste, as well as other modifying operations. |
| ContentEditable | granted values and anticipated actions for the attribute that is contenteditable. |
| HTML Accessibility API Mappings (AAM) | Defines how user agents map HTML elements and attributes to platform accessibility APIs. |
| ARIA in HTML | Defines the net designer rules (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 feature, that is thought as an element of the UI Events Specification. |
| UI Events KeyboardEvent key Values | The values when it comes to key characteristic defined when you look at the UI occasions specification. |
WICG specs
With regards to the WICG progress, the Group could also create W3C tips for the documents that are following
| Specification | explanation |
|---|---|
| Cookie shop | An asynchronous Javascript snacks API for documents and employees. |
| Web Share API | An API for sharing text, links along with other content to an arbitrary location regarding the individual’s option. |
| Web Share Target | An API which allows web sites to declare on their own as internet share goals, 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 from the application (including the rack or home display screen), for the intended purpose of notifying the consumer if the state regarding the application changed ( ag e.g., when brand brand new communications have actually appeared), without showing a far more notification that is heavyweight. |