- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Fri, 11 Nov 2011 10:25:35 -0500
- To: ext Michael Cooper <cooper@w3.org>
- CC: public-webevents@w3.org, List WAI Liaison <wai-liaison@w3.org>, List WAI PF <w3c-wai-pf@w3.org>, Sangwhan Moon <smoon@opera.com>
Hi Michael - I don't believe you and/or PFWG responded to my email below (sent on October 13 and archived at [1]). Since the comment deadline for LC#2 (published on October 27 [2]) ends on November 17, I would appreciate a response by the 17th. -Thanks, Art Barstow [1] http://lists.w3.org/Archives/Public/public-webevents/2011OctDec/0047.html [2] http://www.w3.org/TR/2011/WD-touch-events-20111027/ On 10/13/11 10:16 AM, ext Arthur Barstow wrote: > Hi Michael, All > > We discussed your comments during WebEvents' 11-Oct-2011 call [1] and > captured your comment #1 as [LC-7] and your comment #2 as [LC-6] in > our LC disposition of comments document. > > * Re LC-6 - we agree additional non-normative tutorial/Primer type > information for the Touch Events spec would be useful. I created > [Action-85] to track this request. If you and/or your colleagues wish > to contribute to such information, please let me know. However, we do > not think completion of this action should block this spec from > progressing on the Recommendation track (and BTW, the next step will > be another LCWD). > > Regarding the interaction between touch events and mouse events, we > agree additional non-normative text would be useful and think the > information already included in section 7 of the spec [2] is > sufficient. If you have additional non-normative text you want to > propose, please send to public-webevents at w3.org so we can review it. > > * Re LC-7 - Sangwhan agreed to address these two editorial comments > (add units to attribute definitions and add a definition of > preventDefault). I noticed he already made two related commits: > > http://dvcs.w3.org/hg/webevents/rev/bee004414dba > http://dvcs.w3.org/hg/webevents/rev/a8b5ef36b865 > > and the result is reflected in the latest Editor's Draft of the spec: > > http://dvcs.w3.org/hg/webevents/raw-file/v1/touchevents.html#attributes > http://dvcs.w3.org/hg/webevents/raw-file/v1/touchevents.html#glossary > > For the purposes of comment tracking, please let us know if our > responses are OK or not. > > -Art Barstow > > [1] http://www.w3.org/2011/10/11-webevents-minutes.html#item04 > [2] http://www.w3.org/TR/2011/WD-touch-events-20110913/#mouse-events > [LC-6] > http://www.w3.org/2010/webevents/wiki/TouchEvents-LCWD-13-Sep-2011#LC-6 > [LC-7] > http://www.w3.org/2010/webevents/wiki/TouchEvents-LCWD-13-Sep-2011#LC-7 > [Action-85] http://www.w3.org/2010/webevents/track/actions/85 > > > On 9/28/11 4:05 PM, ext Michael Cooper wrote: >> The following are comments from the Protocols and Formats Working >> Group on the 13 September 2011 Touch Events version 1 Last Call >> Working Draft http://www.w3.org/TR/2011/WD-touch-events-20110913/. >> Authorization to send these as PFWG comments is archived at >> http://www.w3.org/2011/09/28-pf-minutes#item06. >> >> Note that some PFWG members exempted themselves from our review of >> this specification because of patent concerns at their companies. >> >> 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. >> >> For Protocols and Formats Working Group, >> Michael Cooper, Team Contact >> -- >> >> Michael Cooper >> Web Accessibility Specialist >> World Wide Web Consortium, Web Accessibility Initiative >> E-mail cooper@w3.org <mailto:cooper@w3.org> >> Information Page <http://www.w3.org/People/cooper/> >> >
Received on Friday, 11 November 2011 15:26:42 UTC