The objective for the internet Applications performing Group (Web WG) would be to create 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 telephone phone calls will undoubtedly be held whenever required. Face-to-face: we shall satisfy throughout the W3C’s annual Technical Plenary week; additional meetings that are face-to-face be planned by permission of individuals. |
Range
The range for the Web performing Group is:
- Haptic input products and their emitted occasions and/or information.
- Textual input and text manipulation.
- Information sharing across remote and neighborhood web applications.
- Acting and receiving upon data from remote sources.
- Accessing the file system and storage that is persistent.
- Interfacing with OS abilities.
- Integrating web applications aided by 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 describes writer conformance demands for establishing ARIA characteristics. The performing Group will not be prepared to include every other requirements with this matter.
Requirements created by the Web Working Group help developers to generate internet applications that work across a range that is wide of and products, as well as for a diverse diversity of users, by handling issues of accessibility, unit self-reliance, internationalization, privacy, and protection.
Success Criteria
To be able to advance to Proposed Recommendation, each specification should have at the very least two separate implementations in wide usage.
Each specification will need to have a test that is accompanying, which will be preferably developed in parallel into the specification. The test suite shall 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 aspects of accessibility, internationalization, privacy, and protection, each specification will need to have an area that defines appropriate benefits, limits, and practice solutions that are best for the specific area.
Deliverables
Additional information about internet performing Group requirements are available in the GitHub repository.
Normative Requirements
The net performing Group will provide the after specifications that are normative.
| Specification | definition |
|---|---|
| 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 things. The 3rd version adds brand brand new abilities 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 that provides scripted usage of natural mouse movement information while securing 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, using a push solution. |
| Screen Orientation API | An API for reading display screen orientation, being informed of display orientation modifications, and securing display orientation up to a certain state. |
| internet App Manifest | A JSON-based manifest file that provides developers having a central spot to place metadata connected with a 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 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 anticipated habits for the contenteditable feature. |
| 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 net 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 feature, which will be understood to be an element 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 occasions specification. |
WICG requirements
With respect to the WICG progress, the Group might also create W3C tips for the documents that are following
| Specification | definition |
|---|---|
| Cookie shop | An asynchronous Javascript snacks API for papers and employees. |
| internet Share API | An API for sharing text, links along with other content to a destination that is arbitrary of user’s option. |
| online Share Target | An API which allows internet sites to declare by themselves as internet share goals, that may get provided content from either the Web Share API, or system activities ( e.g., stocks from native ). |
| Badging | An API enabling internet applications to create an application-wide badge, shown in a operating-system-specific place linked to the application (including the rack or house screen), for the true purpose of notifying an individual if the state associated with the application changed ( ag e.g., whenever brand brand new communications have actually appeared), without showing a far more heavyweight notification. |
0 Comments