- From: Daniel Weck <daniel.weck@gmail.com>
- Date: Fri, 14 Oct 2011 10:11:39 +0100
- To: Janina Sajka <janina@rednote.net>
- Cc: www-style@w3.org, Bert Bos <bert@w3.org>, List WAI Liaison <wai-liaison@w3.org>, List WAI PF <w3c-wai-pf@w3.org>
The text quoted below (from your original email) does not appear to have anything to do with the Last Call Working Draft of the CSS Speech Module Level 3, so I have ignored it. It looks like a copy/paste error, but let me know if I have missed something <smile> Cheers, Daniel On 11 Oct 2011, at 20:25, Janina Sajka wrote: > 1) If a Web application can deal with touch events, it can intercept them, and the idea is that in this case no corresponding mouse events will be dispatched. However, if the Web application is not specifically written for touch input devices, it can react to the subsequent mouse events instead. This can be a powerful paradigm, but it is not fully described in this spec. The relation between touch events and mouse events should be explained in more detail for authors who want to achieve device independence. There is a general need for a "primer" document in the W3C space explaining the various DOM events and how they relate to each other, also providing best practices of device-specific and device-independent authoring. > > 2) Minor editorial issues with the spec: > > - Section 3.1: For each of the attributes, the unit should be mentioned (device pixels, CSS pixels, etc.) > > - Section 7: The "preventDefault" method should be explained or listed in the glossary.
Received on Friday, 14 October 2011 09:12:13 UTC