W3C home > Mailing lists > Public > public-pointer-events@w3.org > January to March 2014

RE: touch-action support now in chromium behind flag, targeting ship in Chrome 35

From: Jacob Rossi <Jacob.Rossi@microsoft.com>
Date: Thu, 16 Jan 2014 20:45:55 +0000
To: Rick Byers <rbyers@google.com>, "public-pointer-events@w3.org" <public-pointer-events@w3.org>
Message-ID: <3ac8ffdb8fa14a3986af1699b8067186@BL2PR03MB451.namprd03.prod.outlook.com>
Fantastic! Is it the case that the Polymer PE polyfill will automatically detect support for touch-action and use the native property while still synthesizing the event model?

From: Rick Byers [mailto:rbyers@google.com]
Sent: Tuesday, January 7, 2014 11:55 AM
To: public-pointer-events@w3.org
Subject: touch-action support now in chromium behind flag, targeting ship in Chrome 35

For people not on the WG conference call, I just wanted to repeat that I've turned on support for touch-action in chromium behind the chrome://flags/#enable-experimental-web-platform-features flag.  You can play with it in current Chrome Canary builds on Windows [1], or on Android once Chrome Beta hit's M-34 (or I'm happy to supply custom Android content-shell builds if anyone doesn't want to wait).

There are still some outstanding issues, but it's functionally complete and ready for experimentation.  Eg. the Polymer PointerEvents polyfill will make use of it.  My plan is to tie up all the outstanding issues and get it enabled by default in time for Chrome M-35 (which branches for release at the end of March [2]).  You can follow along in Chromium bug 241964 [3] and the bugs it's blocked on.


[1] https://www.google.ca/intl/en/chrome/browser/canary.html

[2] http://www.chromium.org/developers/calendar

[3] https://code.google.com/p/chromium/issues/detail?id=241964

Received on Thursday, 16 January 2014 20:46:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:48:09 UTC