Thanks for your input guys - I know this is a tough topic, and working well with all the major vendors as best we can is super important to us. I don't think we're going to get resolution on this issue here, but I also think we can table it for a bit. I think all our pressing issues fall within the scope we discussed for "errata" (radius/angle was a minor extra thing - not important in itself). When (and I'm pretty sure it'll be "when", not "if") we have something important we want to add/change to TouchEvents that falls outside that scope I'll continue the discussion in a broader context. Rick On Wed, Jun 11, 2014 at 10:47 AM, Anne van Kesteren <annevk@annevk.nl> wrote: > On Wed, Jun 11, 2014 at 2:03 AM, Jacob Rossi <Jacob.Rossi@microsoft.com> > wrote: > > If you ask web developers what the biggest problem is for touch, they’ll > > tell you interoperable APIs. > > Given that Chrome and Safari do touch events, it seems that unless > that changes the platform is doomed with respect to replacing them. It > might be good to discuss this on a somewhat broader forum though, such > as public-webapps@w3.org. There's almost no exposure here. > > > -- > http://annevankesteren.nl/ >
Received on Thursday, 12 June 2014 20:33:50 UTC