Skip to toolbar

Community & Business Groups

Proposed Group: Touch Events Community Group

The Touch Events Community Group has been proposed by Arthur Barstow:

The Touch Events community group was formed by members of the Web Events Working Group (responsible for the Touch Events specification) and the Pointer Events Working Group (responsible for the Pointer Events spec). The group’s focus is to determine differences in touch event behavior between browsers. The group seeks to form consensus on the best approaches for interoperability outside of what’s already standardized.

Among the topics in scope for this group:

* Defining how touch-action should be implemented in browsers that support touch events; see [1].

* Defining the “right” TouchEvent / PointerEvent interaction for both browsers and pointer event polyfills; see [2].

* Trying to form consensus on how exactly browsers should behave in sending touch events when scrolling starts (f.ex. see the following public-webevents thread [3]).

* Identifying other differences that exist between these events.

* Discussing problems web/framework developers have with the design of touch events; see [4].

* Define “mappings” between Touch Events and Pointer Events (f.ex. see [5]).

* Define the relationships between touch-pointer-mouse.

The group also expects to make proposals for potential future standards.






You are invited to support the creation of this group. Once the group has a total of five supporters, it will be launched and people can join to begin work.
Once launched, the group will no longer be listed as “proposed”; it will be in the list of current groups.

In order to support the group, you will need a W3C account.

If you believe that there is an issue with this group that requires the attention of the W3C staff, please send us email on

Thank you,
W3C Community Development Team

Leave a Reply

Your email address will not be published. Required fields are marked *

Before you comment here, note that this forum is moderated and your IP address is sent to Akismet, the plugin we use to mitigate spam comments.