101 | Web Applications Working Group Charter 102 |
103 |104 | The mission of the Web Applications Working Group 106 | (WebApps WG) is to produce specifications that facilitate the 107 | development of client-side web applications. 108 |
109 | 115 |119 | Start date 120 | | 121 |122 | The date when the charter is approved. 123 | | 124 |
---|---|
127 | End date 128 | | 129 |130 | 2 years after the charter approved. 131 | | 132 |
138 | Chairs 139 | | 140 |141 | Léonie Watson (TetraLogical), Marcos Cáceres (Apple Inc., 0.2 142 | FTE) 143 | | 144 |
147 | Team Contacts 148 | | 149 |150 | Xiaoqian Wu (0.1 151 | FTE) 152 | | 153 |
156 | Meeting Schedule 157 | | 158 |
159 | Teleconferences: topic-specific calls will be
160 | held when needed. 161 | Face-to-face: we will meet during the W3C's 162 | annual Technical Plenary week; additional face-to-face meetings 163 | may be scheduled by consent of participants. 164 | |
165 |
170 | Scope 171 |
172 |173 | The scope of the WebApps Working Group is: 174 |
175 |-
176 |
- Haptic input devices and their emitted events and/or data. 177 | 178 |
- Data sharing across remote and local web applications. 179 | 180 |
- Receiving and acting upon data from remote sources. 181 | 182 |
- Accessing the file system and persistent storage. 183 | 184 |
- Interfacing with OS capabilities. 185 | 186 |
- Integrating web applications with the OS. 187 | 188 |
190 | The working group also maintains a specification for mapping HTML 191 | elements and attributes to platform accessibility APIs, and a 192 | separate specification that defines author conformance requirements 193 | for setting ARIA attributes. The Working Group does not expect to add 194 | any other specifications relating to this matter. 195 |
196 |197 | Specifications produced by the WebApps Working Group enable 198 | developers to create web applications that work across a wide range 199 | of platforms and devices, and for a broad diversity of users, by 200 | addressing matters of accessibility, device independence, 201 | internationalization, privacy, and security. 202 |
203 |205 | Success Criteria 206 |
207 |208 | In order to advance to Candidate Recommendation and to add 211 | features after reaching Candidate Recommendation, each feature is 212 | expected to be supported by at least two implementations, which may 213 | be judged by factors including existing implementations, 214 | expressions of interest, and lack of opposition. 215 |
216 |217 | In order to advance to Proposed Recommendation, each 220 | specification must have at 222 | least two independent implementations in wide use. 223 |
224 |225 | Each specification should contain separate sections detailing all 226 | known security and privacy implications for implementers, Web 227 | authors, and end users. 228 |
229 |230 | There should be testing plans for each specification, starting from 231 | the earliest drafts. 232 |
233 |234 | Each specification must have an accompanying test suite, which is 235 | ideally developed in parallel to the specification. The test suite 236 | will be used to produce an implementation report before the 237 | specification transitions to Proposed 239 | Recommendation. 240 |
241 |242 | Where there are implications for user experience, each 243 | specification should contain a section on accessibility that 244 | describes the benefits and impacts, including ways specification 245 | features can be used to address them, and recommendations for 246 | maximising accessibility in implementations. 247 |
248 |252 | Deliverables 253 |
254 |255 | More information about WebApps Working Group specifications can be 256 | found in the GitHub 257 | repository. 258 |
259 |261 | Normative Specifications 262 |
263 |264 | The WebApps Working Group will deliver the following normative 265 | specifications. 266 |
267 |270 | Specification 271 | | 272 |273 | Description 274 | | 275 |
---|---|
278 | File API 279 | | 280 |281 | An API for representing file objects in web applications, as 282 | well as programmatically selecting them and accessing their 283 | data. 284 | | 285 |
288 | Gamepad API 289 | | 290 |
291 | 292 | Level 1 of the API that represents gamepad devices, and 293 | enables web applications to act upon gamepad data. 294 | 295 |296 | Level 2 aims to support the capabilities of next generation 297 | gamepads. 298 | 299 | |
300 |
303 | Image resource 304 | | 305 |306 | This document defines the concept of an "image resource" and a 307 | corresponding WebIDL ImageResource dictionary. Web APIs can use 308 | the ImageResource dictionary to represent an image resource in 309 | contexts where an HTMLImageElement is not suitable or available 310 | (e.g., in a Worker). 311 | | 312 |
315 | Indexed Database API 316 | | 317 |318 | An API for a database of records holding simple values and 319 | hierarchical objects. The third edition adds new 321 | capabilities and improves developer ergonomics by using 322 | promises. 323 | | 324 |
327 | Intersection Observer 328 | | 329 |330 | An API that can be used to understand the visibility and 331 | position of DOM elements ("targets") relative to a containing 332 | element or to the top-level viewport ("root"). 333 | | 334 |
337 | Pointer Lock 338 | | 339 |340 | An API that provides scripted access to raw mouse movement data 341 | while locking the target of mouse events to a single element 342 | and removing the cursor from view. 343 | | 344 |
347 | Push API 348 | | 349 |350 | An API for sending push messages to a web application, via a 351 | push service. 352 | | 353 |
356 | Screen Orientation API 357 | | 358 |359 | An API for reading screen orientation, being informed of screen 360 | orientation changes, and locking screen orientation to a 361 | specific state. 362 | | 363 |
366 | Web App Manifest 367 | | 368 |369 | A JSON-based manifest file that provides developers with a 370 | centralized place to put metadata associated with a web 371 | application. 372 | | 373 |
376 | Web Share API 377 | | 378 |379 | An API for sharing text, links and other content to an 380 | arbitrary destination of the user's choice. 381 | | 382 |
385 | ARIA in HTML 386 | | 387 |388 | Defines the web developer rules (author conformance 389 | requirements) for ARIA attributes on HTML elements. 390 | | 391 |
394 | UI Events 395 | | 396 |397 | UI Events that extend the DOM Event objects defined in the DOM 398 | specification. 399 | | 400 |
403 | UI Events KeyboardEvent code values 404 | | 405 |
406 | The values for the KeyboardEvent.code attribute,
407 | which is defined as part of the UI Events Specification.
408 | |
409 |
412 | UI Events KeyboardEvent key Values 413 | | 414 |
415 | The values for the key attribute defined in the UI
416 | Events specification.
417 | |
418 |
421 | Web Locks API 422 | | 423 |424 | This document defines a web platform API that allows script to 425 | asynchronously acquire a lock over a resource, hold it while 426 | work is performed, then release it. While held, no other script 427 | in the origin can acquire a lock over the same resource. This 428 | allows contexts (windows, workers) within a web application to 429 | coordinate the usage of resources. 430 | | 431 |
434 | Depending on the Consensus of 436 | the Working Group members, the Group may bring the following WHATWG 437 | Review Drafts from W3C Candidate Recommendation to Proposed 438 | Recommendation, in accordance with the WHATWG-W3C 440 | Memorandum of Understanding and 2021 442 | Relationship Update.: 443 |
444 |447 | Specification 448 | | 449 |450 | Description 451 | | 452 |
---|---|
455 | Web IDL 456 | | 457 |458 | This document defines an interface definition language, Web 459 | IDL, that can be used to describe interfaces that are intended 460 | to be implemented in web browsers. Web IDL is an IDL variant 461 | with a number of features that allow the behavior of common 462 | script objects in the web platform to be specified more 463 | readily. How interfaces described with Web IDL correspond to 464 | constructs within ECMAScript execution environments is also 465 | detailed in this document. It is expected that this document 466 | acts as a guide to implementors of already-published 467 | specifications, and that newly published specifications 468 | reference this document to ensure conforming implementations of 469 | interfaces are interoperable. 470 | | 471 |
476 | WICG specifications 477 |
478 |479 | Depending on the WICG progress, including 481 | interest from multiple implementers, the Group may also produce W3C 482 | Recommendations for the following documents: 483 |
484 |487 | Specification 488 | | 489 |490 | Description 491 | | 492 |
---|---|
495 | Cookie Store 496 | | 497 |498 | An asynchronous Javascript cookies API for documents and 499 | workers. 500 | | 501 |
504 | Web Share 505 | Target 506 | | 507 |508 | An API that allows websites to declare themselves as web share 509 | targets, which can receive shared content from either the Web 510 | Share API, or system events (e.g., shares from native apps). 511 | | 512 |
515 | Badging 516 | | 517 |518 | An API allowing web applications to set an application-wide 519 | badge, shown in an operating-system-specific place associated 520 | with the application (such as the shelf or home screen), for 521 | the purpose of notifying the user when the state of the 522 | application has changed (e.g., when new messages have arrived), 523 | without showing a more heavyweight notification. 524 | | 525 |
528 | Contact 529 | Picker API 530 | | 531 |532 | An API to give one-off access to a user’s contact information 533 | with full control over the shared data. It will be a joint 534 | deliverable with the Devices 535 | and Sensors Working Group. 536 | | 537 |
540 | 542 | Haptics 543 | | 544 |545 | An API allowing web applications to interface with haptic 546 | actuators, such as vibration motors found on gamepad 547 | controllers, and potentially other devices that provide haptic 548 | feedback. 549 | | 550 |
553 | User-Agent 554 | Client Hints 555 | | 556 |
557 | This document defines a set of Client Hints that aim to provide
558 | developers with the ability to perform agent-based content
559 | negotiation when necessary, while avoiding the historical
560 | baggage and passive fingerprinting surface exposed by the
561 | venerable User-Agent HTTP header.
562 | |
563 |
568 | Other Deliverables 569 |
570 |571 | Other non-normative documents may be created such as, use case and 572 | requirements documents, implementation reports, and Best Practices 573 | documents, to support web developers when designing applications. 574 |
575 |578 | Timeline 579 |
580 |581 | All specifications produced by the WebApps Working Group are 582 | expected to progress during this charter period. The charter does 583 | not include a detailed timeline for each specification because such 584 | information is speculative and easily becomes inaccurate. However, 585 | a rough estimation of completion is available in the detailed list of Deliverables when 587 | possible. 588 |
589 |590 | The Working Group home 591 | page will link to a more comprehensive page with detailed 592 | status and estimated completion time for each specification. 593 |
594 |595 | Note that the WICG Specifications, if 596 | adopted, have an estimated time of completion of 2 years. 597 |
598 |602 | Coordination 603 |
604 |605 | For all specifications, this Working Group will seek 607 | horizontal review for accessibility, internationalization, 608 | performance, privacy, and security with the relevant Working and 609 | Interest Groups, and with the TAG. Invitation for review 611 | must be issued during each major standards-track document transition, 612 | including FPWD. The Working Group is 614 | encouraged to engage collaboratively with the horizontal review 615 | groups throughout development of each specification. The Working 616 | Group is advised to seek a review at least 3 months before first 617 | entering CR and is encouraged to 619 | proactively notify the horizontal review groups when major changes 620 | occur in a specification following a review. 621 |
622 |623 | For all specifications, technical coordination with the following 624 | Groups will be made, per the W3C Process 626 | Document: 627 |
628 |-
629 |
- 630 | Accessible Platform 631 | Architectures (APA) Working Group 632 | 633 |
- 634 | For accessibility horizontal review, and to collaborate on 635 | accessibility related topics. 636 | 637 |
- 638 | Internationalization 640 | Working Group 641 | 642 |
- 643 | For internationalization horizontal review, and to collaborate on 644 | internationalization related topics. 645 | 646 |
- 647 | Privacy Interest Group 648 | 649 |
- 650 | For privacy horizontal review, and to collaborate on privacy 651 | related topics. 652 | 653 |
- 654 | Technical Architecture Group 655 | (TAG) 656 | 657 |
- 658 | For architectural horizontal review, and to collaborate on 659 | architecture related topics. 660 | 661 |
663 | The WebApps Group will also seek review from the Accessible Rich Internet Applications 665 | (ARIA) Working Group to coordinate on the ARIA attributes on HTML 666 | elements, and their mappings to platform accessibility APIs. 667 |
668 |670 | W3C Groups 671 |
672 |673 | The work of the WebApps Working Group touches on the work of many 674 | other W3C Working and Interest 675 | Groups. Where appropriate, the WebApps Working Group will 676 | coordinate with the relevant Working or Interest Groups, per the 677 | W3C 678 | Process. 679 |
680 |682 | External Organizations 683 |
684 |685 | The WebApps Working Group may also coordinate with the following 686 | organizations: 687 |
688 |-
689 |
- 690 | 692 | ECMA TC39 693 | 694 |
- 695 | For co-ordination on topics relating to JavaScript. 696 | 697 |
- 698 | Internet Engineering Task Force 699 | (IETF) 700 | 701 |
- 702 | For co-ordination on topics relating to internet protocols. 703 | 704 |
- 705 | Web Hypertext Application 706 | Technology Working Group (WHATWG) 707 | 708 |
- 709 | For co-ordination on topics relating to the web platform. 710 | 711 |
717 | Participation 718 |
719 |720 | To be successful, the WebApps Working Group is expected to have 10 or 721 | more active participants for its duration, including representatives 722 | from at least three key implementors. It is also expected to have 723 | active Editors and Test Leads for each specification. 724 |
725 |726 | Chairs, specification Editors, and Test Leads are expected to 727 | contribute half of a working day per week towards the WebApps Working 728 | Group. There is no minimum requirement for other Participants. 729 |
730 |731 | The group encourages questions, comments and issues on its public 732 | mailing lists and document repositories, as described in Communication. 734 |
735 |736 | The group also welcomes technical contributions from non-Members, to 737 | be considered upon their agreement to the terms of the W3C Patent Policy. 739 |
740 |743 | Working mode 744 |
745 |746 | This group primarily conducts its technical work on GitHub. The 747 | public is invited to review, discuss and contribute to this work. 748 |
749 |750 | The Chairs and Editors will assess support from web platform 751 | implementers or web application or framework developers, to assure 752 | that substantial changes are supported by more than a single member 753 | before they are adopted. 754 |
755 |756 | Additionally, support from two or more web platform implementers is 757 | required before a substantive change can be made to a specification. 758 | This is enforced by a pull request template on GitHub, which Editors 759 | must fill out as a public record before a substantive contribution 760 | can be merged. The template will require implementers to give public 761 | support for a change/fix/feature and, where possible, provide a link 762 | to a public bug tracker for an implementation. 763 |
764 |767 | Communication 768 |
769 |770 | Technical discussions for the WebApps Working Group are conducted in 771 | public: 773 | the meeting minutes from teleconference and face-to-face meetings 774 | will be archived for public review, and technical discussions and 775 | issue tracking will be conducted in a manner that can be both read 776 | and contributed to by the general public. Working Drafts and Editor's 777 | Drafts of specifications will be developed on public repositories, 778 | and may permit direct public contribution requests. 779 |
780 |781 | Meetings are not open to public participation, however non-members 782 | may request observer status at meetings by contacting the WebApps 783 | Working Group Chairs. 784 |
785 |786 | Information about the WebApps Working Group (including details about 787 | deliverables, issues, actions, status, participants, and meetings) 788 | will be available from the WebApps Working Group home 790 | page. 791 |
792 |793 | The group may use a Member-confidential mailing list for 794 | administrative purposes and, at the discretion of the Chairs and 795 | members of the group, for member-only discussions in special cases 796 | when a participant requests such a discussion. 797 |
798 |801 | Decision Policy 802 |
803 |804 | This group will seek to make decisions through consensus and due 805 | process, per the W3C Process 807 | Document (section 3.3). Typically, an editor or other participant 808 | makes an initial proposal, which is then refined in discussion with 809 | members of the group and other reviewers, and consensus emerges with 810 | little formal voting being required. 811 |
812 |813 | However, if a decision is necessary for timely progress and consensus 814 | is not achieved after careful consideration of the range of views 815 | presented, the Chairs may call for a group vote and record a decision 816 | along with any objections. 817 |
818 |819 | To afford asynchronous decisions and organizational deliberation, any 820 | resolution (including publication decisions) taken in a face-to-face 821 | meeting or teleconference will be considered provisional. 822 |
823 |824 | A call for consensus (CfC) will be issued for all resolutions (for 825 | example, via email and/or web-based survey), with a response period 826 | from one week to 10 working days, depending on the chair's evaluation 827 | of the group consensus on the issue. 828 |
829 |830 | If no objections are raised on the mailing list by the end of the 831 | response period, the resolution will be considered to have consensus 832 | as a resolution of the WebApps Working Group. 833 |
834 |835 | All decisions made by the group should be considered resolved unless 836 | and until new information becomes available or unless reopened at the 837 | discretion of the Chairs or the Director. 838 |
839 |840 | This charter is written in accordance with the W3C Process 842 | Document (Section 3.4, Votes) and includes no voting procedures 843 | beyond what the Process Document requires. 844 |
845 |848 | Patent Policy 849 |
850 |851 | This Working Group operates under the W3C Patent Policy 853 | (Version of 15 September 2020). To promote the widest adoption of Web 854 | standards, W3C seeks to issue Recommendations that can be 855 | implemented, according to this policy, on a Royalty-Free basis. 856 |
857 |858 | For more information about disclosure obligations for this group, 859 | please see the W3C 860 | Patent Policy Implementation. 861 |
862 |865 | Licensing 866 |
867 |868 | The WebApps Working Group will use the W3C Software 870 | and Document license for all its deliverables. WebIDL will follow 871 | the terms of the WHATWG-W3C 873 | Memorandum of Understanding and 2021 875 | Relationship Update. 876 |
877 |880 | About this Charter 881 |
882 |883 | This charter has been created according to section 5.2 of 885 | the Process 886 | Document. In the event of a conflict between this document or the 887 | provisions of any charter and the W3C Process, the W3C Process shall 888 | take precedence. 889 |
890 |892 | Charter History 893 |
894 |895 | The following table lists details of all changes from the initial 896 | charter, per the W3C Process 898 | Document (section 5.2.3): 899 |
900 |904 | Charter Period 905 | | 906 |907 | Start Date 908 | | 909 |910 | End Date 911 | | 912 |913 | Changes 914 | | 915 |
---|---|---|---|
918 | Initial 920 | Charter 921 | | 922 |923 | 14 May 2019 924 | | 925 |926 | 31 May 2021 927 | | 928 |929 | none 930 | | 931 |
934 | Rechartered 936 | | 937 |938 | 15 December 2020 939 | | 940 |941 | 31 May 2021 942 | | 943 |944 | New Patent Policy 945 | | 946 |
949 | Rechartered 950 | | 951 |952 | 1 June 2021 953 | | 954 |955 | 31 May 2023 956 | | 957 |
958 |
|
969 |
1007 | Note: Starting from 16 July 2020, the team contacts of the WebApps 1008 | Working Group reduced from Yves Lafon (0.3 FTE), Xiaoqian Wu (0.2 1009 | FTE) to Xiaoqian Wu (0.1 FTE). Starting from 5 November 2020, 1010 | Marcos Cáceres re-appointed as co-chair after affiliation change. 1011 | We made non-substantive modifications to this charter to reflect 1012 | these changes. 1013 |
1014 |1017 | History of this WG 1018 |
1019 |1020 | The WebApps Working Group was a predecessor to the Web Platform Working Group 1022 | (which remains active to work on specifications that are pertinent 1023 | to the discussions relating to a collaboration agreement between 1024 | the W3C and the WHATWG). The remaining specifications have been 1025 | transferred from the Web Platform Working Group to the WebApps 1026 | Working Group, so that progress can continue to be made on those 1027 | specifications while the W3C and WHATWG negotiations are ongoing. 1028 |
1029 |1030 | In addition, specifications that have been successfully incubated 1031 | in the Web Platform 1032 | Incubator Community Group (WICG) have been transferred to the 1033 | WebApps Working Group. 1034 |
1035 |1039 | Detailed list of Deliverables 1040 |
1041 |-
1042 |
-
1043 | File
1044 | API
1045 |
-
1046 |
- Latest publication: 2021-06-04 1048 | 1049 |
- Exclusion Draft: https://www.w3.org/TR/2013/WD-FileAPI-20130912/ 1051 | 1052 |
- associated 1054 | Call for Exclusion on 2013-09-13 1055 | 1056 |
- Produced under Working Group Charter: https://www.w3.org/2012/webapps/charter/ 1058 | 1059 |
- Estimated Completion: CR - Q2 2022; REC - Q3 2023 1060 | 1061 |
1063 | -
1064 | Gamepad
1066 |
-
1067 |
- Latest publication: 2021-08-05 1069 | 1070 |
- Exclusion Draft: https://www.w3.org/TR/2012/WD-gamepad-20120529/ 1072 | 1073 |
- associated 1075 | Call for Exclusion on 2012-05-29 1076 | 1077 |
- Produced under Working Group Charter: https://www.w3.org/2012/webapps/charter/ 1079 | 1080 |
- Estimated Completion: CR - Q1 2022; REC - Q2 2023 1081 | 1082 |
1084 | -
1085 | Image Resource
1087 |
-
1088 |
- Latest publication: 2021-06-04 1090 | 1091 |
- Exclusion Draft: https://www.w3.org/TR/2020/WD-image-resource-20200507/ 1093 | 1094 |
- associated 1096 | Call for Exclusion on 2020-05-07 1097 | 1098 |
- Produced under Working Group Charter: https://www.w3.org/2020/12/webapps-wg-charter.html 1100 | 1101 |
- Estimated Completion: CR - Q3 2022; REC - Q3 2023 1102 | 1103 |
1105 | -
1106 | Indexed Database API 3.0
1108 |
-
1109 |
- Latest publication: 2021-06-18 1111 | 1112 |
- Exclusion Draft: https://www.w3.org/TR/2021/WD-IndexedDB-3-20210311/ 1114 | 1115 |
- associated 1117 | Call for Exclusion on 2021-03-11 1118 | 1119 |
- Produced under Working Group Charter: https://www.w3.org/2020/12/webapps-wg-charter.html 1121 | 1122 |
- Estimated Completion: CR - Q3 2022; REC - Q3 2023 1123 | 1124 |
1126 | -
1127 | Intersection Observer
1129 |
-
1130 |
- Latest publication: 1132 | 2021-06-24 1133 | 1134 |
- Exclusion Draft: 1136 | https://www.w3.org/TR/2017/WD-intersection-observer-20170914/ 1137 | 1138 |
- associated 1140 | Call for Exclusion on 2017-09-14 1141 | 1142 |
- Produced under Working Group Charter: https://www.w3.org/2017/08/webplatform-charter.html 1144 | 1145 |
- Estimated Completion: CR - Q1 2022; REC - Q1 2023 1146 | 1147 |
1149 | -
1150 | Pointer Lock 2.0
1152 |
-
1153 |
- Latest publication: 2019-08-28 1155 | 1156 |
- Exclusion Draft: https://www.w3.org/TR/2016/WD-pointerlock-2-20161122/ 1158 | 1159 |
- associated 1161 | Call for Exclusion on 2016-11-22 1162 | 1163 |
- Produced under Working Group Charter: https://www.w3.org/2015/10/webplatform-charter.html 1165 | 1166 |
- Estimated Completion: CR - Q3 2022; REC - Q3 2023 1167 | 1168 |
1170 | -
1171 | Push
1172 | API
1173 |
-
1174 |
- Latest publication: 2021-06-16 1176 | 1177 |
- Exclusion Draft: https://www.w3.org/TR/2012/WD-push-api-20121018/ 1179 | 1180 |
- associated 1182 | Call for Exclusion on 2012-10-18 1183 | 1184 |
- Produced under Working Group Charter: https://www.w3.org/2012/webapps/charter/ 1186 | 1187 |
- Estimated Completion: CR - Q1 2022; REC - Q4 2022 1188 | 1189 |
1191 | -
1192 | The Screen Orientation API
1194 |
-
1195 |
- Latest publication: 2021-06-17 1197 | 1198 |
- Exclusion Draft: https://www.w3.org/TR/2012/WD-screen-orientation-20120522/ 1200 | 1201 |
- associated 1203 | Call for Exclusion on 2012-05-22 1204 | 1205 |
- Produced under Working Group Charter: https://www.w3.org/2012/webapps/charter/ 1207 | 1208 |
- Estimated Completion: CR - Q1 2022; REC - Q4 2022 1209 | 1210 |
1212 | -
1213 | Web
1214 | Application Manifest
1215 |
-
1216 |
- Latest publication: 2021-07-01 1218 | 1219 |
- Exclusion Draft: https://www.w3.org/TR/2013/WD-appmanifest-20131217/ 1221 | 1222 |
- associated 1224 | Call for Exclusion on 2013-12-17 1225 | 1226 |
- Produced under Working Group Charter: https://www.w3.org/2012/webapps/charter/ 1228 | 1229 |
- Estimated Completion: CR - Q1 2022; REC - Q3 2022 1230 | 1231 |
1233 | -
1234 | ARIA in
1235 | HTML
1236 |
-
1237 |
- Latest publication: 2021-08-04 1239 | 1240 |
- Exclusion Draft: https://www.w3.org/TR/2021/CR-html-aria-20210706/ 1242 | 1243 |
- associated 1245 | Call for Exclusion on 2021-07-06 on 2021-09-04 1246 | 1247 |
- Produced under Working Group Charter: https://www.w3.org/2020/12/webapps-wg-charter.html 1249 | 1250 |
- Estimated Completion: REC - Q1 2022 1251 | 1252 |
1254 | -
1255 | UI
1256 | Events
1257 |
-
1258 |
- Latest publication: 2019-05-30 1260 | 1261 |
- Exclusion Draft: https://www.w3.org/TR/2012/WD-DOM-Level-3-Events-20120906/ 1263 | 1264 |
- associated 1266 | Call for Exclusion on 2012-09-06 1267 | 1268 |
- Produced under Working Group Charter: https://www.w3.org/2012/webapps/charter/ 1270 | 1271 |
- Estimated Completion: CR - Q3 2022; REC - Q3 2023 1272 | 1273 |
1275 | -
1276 | UI
1277 | Events KeyboardEvent code Values
1278 |
-
1279 |
- Latest publication: 2017-06-01 1281 | 1282 |
- Exclusion Draft: https://www.w3.org/TR/2017/CR-uievents-code-20170601/ 1284 | 1285 |
- associated 1287 | Call for Exclusion on 2017-06-01 1288 | 1289 |
- Produced under Working Group Charter: http://www.w3.org/2016/11/webplatform-charter.html 1291 | 1292 |
- Estimated Completion: REC - Q3 2022 1293 | 1294 |
1296 | -
1297 | UI
1298 | Events KeyboardEvent key Values
1299 |
-
1300 |
- Latest publication: 2017-06-01 1302 | 1303 |
- Exclusion Draft: https://www.w3.org/TR/2017/CR-uievents-key-20170601/ 1305 | 1306 |
- associated 1308 | Call for Exclusion on 2017-06-01 1309 | 1310 |
- Produced under Working Group Charter: http://www.w3.org/2016/11/webplatform-charter.html 1312 | 1313 |
- Estimated Completion: REC - Q3 2022 1314 | 1315 |
1317 | -
1318 | Web
1319 | Share API
1320 |
-
1321 |
- Latest publication: 2021-08-09 1323 | 1324 |
- Exclusion Draft: https://www.w3.org/TR/2019/WD-web-share-20191217/ 1326 | 1327 |
- associated 1329 | Call for Exclusion on 2019-12-17 1330 | 1331 |
- Produced under Working Group Charter: https://www.w3.org/2019/05/webapps-charter.html 1333 | 1334 |
- Estimated Completion: Q1 2022; REC - Q3 2022 1335 | 1336 |
1338 | -
1339 | Web App Manifest - Application Information
1341 |
-
1342 |
- Latest publication: 2021-03-24 1344 | 1345 |
1347 |