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

I don't think the Polymer polyfill is quite at that point yet - it still
expects you to set the touch-action HTML attribute, but it will set the CSS
property to mirror the attribute, and I landed a fix to make it work
properly when touch-action is supported with touch events (need to test
with Firefox too now though).

My goal once touch-action support in chromium is complete is to shift focus
on the Polymer polyfill.  Eg. I plan to bundle it up as a chrome extension
and test out a bunch of real-world sites designed for IE11 and verify that
they work with pointer events properly (might be good to get a list of
interesting ones from you if possible actually).  We can iterate much
quicker on polymer than we can on Chrome (which still has a 8-10 week
stabilization period).

Rick

On Thu, Jan 16, 2014 at 3:45 PM, Jacob Rossi <Jacob.Rossi@microsoft.com>wrote:

>  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.
>
>
>
> Rick
>
>
>
> [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
>