- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Tue, 10 May 2022 14:32:35 +0100
- To: public-touchevents@w3.org
Hi all, as mentioned a few weeks ago, I'm keen to "tidy up" the community group pages and to clear the deck on any outstanding issues/PRs we have. As part of this, I'd like to update the summary/description/aims of the group, to better reflect what this group actually did/does. Current text (on https://www.w3.org/groups/cg/touchevents and https://www.w3.org/community/touchevents/): 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: https://docs.google.com/document/d/1CV2AXyrdPdGSRypAQcfGrgQVuWYi50EzTmVsMLWgRPM/ * Defining the "right" TouchEvent / PointerEvent interaction for both browsers and pointer event polyfills; see: https://docs.google.com/document/d/1Sasl1qYJV6agrDvGplEYlZznzc38U-TFN_3a67-nlSc/ * 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: http://lists.w3.org/Archives/Public/public-webevents/2013AprJun/0040.html * Identifying other differences that exist between these events. * Discussing problems web/framework developers have with the design of touch events; see: https://docs.google.com/document/d/12-HPlSIF7-ISY8TQHtuQ3IqDi-isZVI0Yzv5zwl90VU/ * Define "mappings" between Touch Events and Pointer Events; for example, see: https://docs.google.com/spreadsheet/ccc?key=0AvdBn9Kvx22qdGRnRXNPb0ZBTUl3SEkwdUdtaW9pWWc&usp=sharing * Define the relationships between touch-pointer-mouse. The group also expects to make proposals for potential future standards. Proposed streamlined text (more in line with the work that has been going on since, and future plans): 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. As focus has now shifted towards taking forward the Pointer Events specification https://w3c.github.io/pointerevents/, this community group is primarily acting as caretakers to maintain and, where necessary, update the Touch Events specification to reflect browser implementation reality. There are currently no plans for any new feature development as part of this specification. It would be great if you could respond to this by 17 March 2022 (in a week's time) if you have any concerns, or would like this to be phrased differently, etc. A lack of response will be taken as approval. Explicit "+1" messages are not necessary, but welcome. Many thanks, Patrick -- Patrick H. Lauke https://www.splintered.co.uk/ | https://github.com/patrickhlauke https://flickr.com/photos/redux/ | https://www.deviantart.com/redux twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Tuesday, 10 May 2022 13:32:49 UTC