This repository is for the UI Events specification (formerly known as DOM 3 Events).
The goal of the UI/DOM Events sub-group, part of the Web Applications Working Group, is to complete the UI Events specification according to market needs, to drive its adoption and implementation, to provide a comprehensive test suite (for implementability at least, and hopefully for interoperability, too), and to move it along the Recommendation Track to W3C Recommendation status.
For discussion of matters related to DOM Events, the group uses the [email protected] mailing list (archive).
- Published Documents
- Editor's Drafts
- UI Events Issues Database
- Need for detailed review by implementors
- Need for comprehensive test suite
- key Values Issues
- code Values Issues
This spec was created using bikeshed. If you would like to contribute edits, please make sure that your changes build correctly.
To build this spec:
- Clone this repo into a local directory.
- Install bikeshed
- Run
python build.pyin your local directory.
To make edits to the spec:
- Edit the
index.bsfile or any of thesections\*.txtfiles. - Build (as above). This will create a
sections\*.includefile for each*.txtfile and then create theindex.html.
When submitting pull requests, make sure you don't include any of the
sections\*.include files in your changelist — they've all been added to the
.gitignore file so that you don't include them accidentally. All changes
should be made in the sections\*.txt files and index.bs.
- DomEventViewer for testing UI Events
- Web Platform Tests
- GitHub web-platform-tests/wpt uievents
- Tests are mirrored on wpt.live/uievents/
If you enjoyed this spec, you might be interested in these other specs from the same publisher:
- UI Events KeyboardEvent code Values: GitHub project, Link to spec
- UI Events KeyboardEvent key Values: GitHub project, Link to spec