The objective associated with internet Applications performing Group (Web WG) would be to produce requirements that facilitate the growth 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 phone telephone calls would be held whenever required. Face-to-face: we are going to satisfy throughout the W3C’s annual Technical Plenary week; extra meetings that are face-to-face be planned by permission of individuals.|
The range regarding the online performing Group is:
- Haptic input products and their emitted occasions and/or data.
- Textual text and input manipulation.
- Information sharing across remote and web that is local.
- Acting and receiving upon information from remote sources.
- Accessing the file system and storage that is persistent.
- Interfacing with OS abilities.
- Integrating internet applications because of 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 needs for establishing ARIA characteristics. The performing Group will not expect to include every other specs concerning this matter.
Specs made by the net Working Group permit developers to generate internet applications that really work across a broad number of platforms and products, as well as for an easy variety of users, by addressing things of accessibility, device freedom, internationalization, privacy, and protection.
So that you can advance to Proposed Recommendation, each specification should have at the very least two separate implementations in wide usage.
Each specification should have an accompanying test suite, that is preferably developed in parallel into the specification. The test suite will be employed to produce an execution report prior to the specification transitions to Proposed Recommendation.
Where you will find implications for implementors, designers, or users, into the regions of accessibility, internationalization, privacy, and protection, each specification will need to have a part that describes appropriate advantages, restrictions, and most readily useful training solutions for the specific area.
Additional information about internet performing Group requirements are available in the GitHub repository.
The internet performing Group will provide the after normative specs.
|File API||An API for representing objects that are file internet applications, in addition to programmatically choosing them and accessing their information.|
|Indexed Database API||An API for a database of documents keeping easy values and hierarchical items. The third version adds brand new abilities and improves designer ergonomics through the use of promises.|
|Intersection Observer||An API which can be used to know the presence and place of DOM elements („targets”) general to a containing element or to your top-level viewport („root”).|
|Pointer Lock||An API providing you with access that is scripted natural mouse movement information while securing the prospective of mouse events to an individual element and getting rid of the cursor from view.|
|drive API||An API for sending 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 state that is specific.|
|online App Manifest||A JSON-based manifest file that delivers designers having a central location to place metadata related to a internet application.|
|Clipboard API and Events||An API for accessing information regarding the operational system clipboard.|
|Selection API||APIs for selection, which enable users and authors to choose a percentage of a document or specify a true point of great interest for content, paste, as well as other modifying operations.|
|ContentEditable||Allowed values and expected actions for the contenteditable feature.|
|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 developer guidelines (writer conformance demands) for ARIA features on HTML elements.|
|UI Events||UI occasions that extend the DOM Event objects defined into the DOM specification.|
|UI Events KeyboardEvent code values||The values for the KeyboardEvent.code characteristic, that will be understood to be an element of the UI Events Specification.|
|UI Events KeyboardEvent key Values||The values for the attribute that is key into the UI occasions specification.|
With regards to the WICG progress, the Group could also create W3C suggestions for the after documents: