PointerEvents/
From W3C Wiki
This is the top-level wiki of the W3C's Pointer Events Working Group, chartered to "provide methods to enable simple device independent input from pointing devices such as mouse, pen, and multi-touch screen".
Feedback on the group's work and the chartered deliverables is welcome, via the WG's public-pointer-events mail list.
SeeAlso:
- Charter
- Publication Status - the group's specification list including publication status
- The WG's Code - describes how the group actually operates including links to various resources
- Bugzilla Bug and Issue Tracking - Bugzilla is used for bugs and issues
- Action Tracking - the group uses Tracker for open action management
- Hg/Mercurial Repository - used for all specifications and tests
- public-pointer-events - archive of the group's Public mail list
Contents |
Charter
The Publicly available charter was approved in November 2012 and expires in November 2014.
Meetings
The group has topic-specific distributed teleconferences Meetings and some face-to-face (f2f) meetings. All of the group's meeting Minutes are Publicly available and draft meeting agendas are submitted to the group's public-pointer-events mail list.
Specifications
All of the group's documents are included in the W3C's Hg/Mercurial repository (http://dvcs.w3.org/hg/pointerevents/).
See the group's PubStatus page for the latest publication status regarding all of the group's specifications.
Testing
The group's tests are include in the group's Hg/Mercurial repository. A more browser friendly mirror of the tests is available in the group's Hg Mirror.
The group is expected to follow the general testing process used by the Web Applications group. In particular:
- Test Harness - the group will use
testharness.js. See WebApps' Test Harness wiki for some additional information.
- Test Approval - the group will review and approve submitted tests. Approved tests will be used to determine if a Candidate Recommendation is interoperable. See WebApps' Test Approval wiki for more information.
- Test Repository - the group will use Hg as its test repository. Within this repository, tests will be organized by their Submitter(s) to assure proper attribution. See WebApps' Test Submission wiki for more information.
Tracking Bugs, Issues and Actions
- Bug and Issue tracking - Bugzilla is used to track Bugs and Issues. All Bugzilla activity is automatically sent to the self-subscribe-able
public-pointer-events-bugzillalist (archive). Group members may submit bugs using Bugzilla and non group members may submit bugs to the group'spublic-pointer-eventsmail list (archive.
- Action tracking - Tracker is used for all action tracking (e.g. admin related actions)
Group Membership
A list of W3C Members organizations formally participating in this group is provided in Member List and Participant List identifies the individuals in the group.
Coordination with Other Working Groups
The group's specifications are relevant to some other W3C Working Groups as documented in the charter.
Liaisons With External Groups
Currently, the group has no formal liaisons with organizations or groups outside of the W3C.
