- Notifications
You must be signed in to change notification settings - Fork20
w3c/touch-events
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
This is the document repository for theTouch Events Community Group.
This Community Group is now closed, and the last version of the specification that the group worked on has been mirrored to:Final Community Group Report for Touch Events Level 2.
There is currently no intention to carry on further work on the Touch Events specification. This document has been maintained up to this point to reflect additions and changes made in user agents since the release of the originalTouch Events Level 1 specification. The Community Group considers Touch Events alegacy API – authors are strongly encouraged to adoptPointer Events instead.
This repo has two branches of note:
gh-pages- this branch is active; it contains theTouch Events Level 2 editors draft, which includes all the changes from an oldv1-erratabranch and theTouch Events Extension Working Group Note)v1- this branch is it not active, and only contains the working branch for the v1 specification
Per the group's2015-Jan-27 agreement, the following process was used to review and approve Pull Requests:
- Submit a pull request and post the PR's link to thepublic-touchevents e-mail list asking for feedback.
- As soon as one of the listed spec editors approves the PR it can be merged.
- If there's debate over a PR that has already landed, it may be reverted until consensus is reached.
For normative changes, a correspondingweb-platform-tests PR is highly appreciated. Typically,both PRs will be merged at the same time. Note that a test change that contradicts the spec shouldnot be merged before the corresponding spec change. If testing is not practical, please explain whyand if appropriatefile an issue to followup later. Add thetype:untestable ortype:missing-coverage label as appropriate.
About
Resources
Code of conduct
Uh oh!
There was an error while loading.Please reload this page.