W3C home > Mailing lists > Public > public-touchevents@w3.org > January 2015

Draft agenda for TECG call: Jan 6

From: Rick Byers <rbyers@chromium.org>
Date: Mon, 5 Jan 2015 13:03:54 -0500
Message-ID: <CAFUtAY9w+LSkYemipdYT3+isJBaDwtE7adU0MbfGyHNj_RTiCg@mail.gmail.com>
To: "public-touchevents@w3.org" <public-touchevents@w3.org>
Here's a proposed agenda for our call tomorrow (Tuesday Jan 6th).

1. Identifying mouse events derived from touch
<http://lists.w3.org/Archives/Public/public-touchevents/2014Sep/0000.html>
I believe solving this is essential to reaching the "touch events enabled
everywhere" goal (IE
<http://blogs.msdn.com/b/ie/archive/2014/09/05/making-the-web-just-work-with-any-input.aspx>
, Chrome <https://code.google.com/p/chromium/issues/detail?id=392584>).  Do
others agree, or is it maybe less important than I think it is?
If it's important, let's brainstorm some options for moving it forward.

2. Identifying touch events that will trigger a tap / click
<http://lists.w3.org/Archives/Public/public-touchevents/2015Jan/0002.html>
This is related to the above, so I think worth discussing at the same time.

Anything else?
   Rick

Logistics:
* Time: UTC: 16:00; Paris: 17:00; Helsinki: 18:00; Boston: 11:00; San
Francisco: 08:00; Tokyo: 01:00 (Wednesday); Duration = 90 minutes maximum
* Phone Numbers: W3C's Zakim Bridge +1.617.761.6200; PIN = 7394# (PEWG#);
SIP information <http://www.w3.org/2006/tools/wiki/Zakim-SIP>
* IRC: irc://irc.w3.org/ ; channel #touchevents

Resources:
List Archive: http://lists.w3.org/Archives/Public/public-touchevents/
ED v1 eratta:
https://dvcs.w3.org/hg/webevents/raw-file/v1-errata/touchevents.html
Extensions note:
https://dvcs.w3.org/hg/webevents/raw-file/default/touchevents.html
Group page: http://www.w3.org/community/touchevents/
Received on Monday, 5 January 2015 18:04:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:35:14 UTC