- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Thu, 30 Oct 2014 01:08:43 +0000
- To: public-touchevents@w3.org
In section 7., the note currently reads: "If a Web application can process touch events, it can intercept them, and no corresponding mouse events would need to be dispatched by the user agent. If the Web application is not specifically written for touch input devices, it can react to the subsequent mouse events instead." On first reading, the first sentence is confusing. What is meant here by "it can intercept them"? Does this actually mean "it can cancel the events"? If so, it should say that. Also, "it can" in the last sentence maybe should be "it will" (as to me, "it can" implies some wilful decision on the part of the developer, whereas in most cases it may be a case of "the app wasn't written for touch, but it works anyway"). Just before the note, the spec reads " If the preventDefault method of touchstart or touchmove is called" as preventDefault is not the only way to cancel an event, I wonder if this should be changed to "If the touchstart or touchmove events are cancelled" and perhaps include the definition we have in PE somewhere? "cancelled event An event whose default action was prevented by means of preventDefault(), returning false in an event handler, or other means as defined by [DOM-LEVEL-3-EVENTS] and [HTML5]." Small typo: "If the user agent intreprets a sequence" intreprets > interprets P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Thursday, 30 October 2014 01:09:10 UTC