Intent to Ship: Support touch-action pan-up pan-down pan-left pan-right CSS properties

47 views
Skip to first unread message

Dave Tapuska

unread,
Jul 6, 2016, 4:15:28 PM7/6/16
to blink-dev
dtap...@chromium.org https://w3c.github.io/pointerevents/ The touch-action CSS property determines whether touch input may trigger default behavior supplied by user agent. This includes, but is not limited to, behaviors such as panning or zooming. Additional keywords indicating: pan-up, pan-down, pan-left, pan-right have been added to the specification.
This allows authors to clearly articulate what default behaviors they are allowing on elements. Previously only pan-x and pan-y were supported. The additional values allows authors to build more complex designs.

One example is a carousel can change its property when it is at its extents to have the best user experience. ie; to allow panning in the direction that there is no more carousel content.
Firefox: Public Support Edge: Shipped Safari: No public signals Web developers: No signals
None
None Yes https://crbug.com/626101 https://www.chromestatus.com/features/5712439765106688

Chris Harrelson

unread,
Jul 6, 2016, 5:11:29 PM7/6/16
to Dave Tapuska, blink-dev
LGTM1

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

Dave Tapuska

unread,
Jul 6, 2016, 5:44:20 PM7/6/16
to Chris Harrelson, blink-dev

I need to post a follow-up on this. In terms of Microsoft support it is not supported. I should have done a test which I did not. Rick indicates this will be a topic to discuss with them in a F2F later this month. I will update the chrome status to reflect my error.

So it seems we are going first here.

Dave

Chris Harrelson

unread,
Jul 6, 2016, 5:45:45 PM7/6/16
to Dave Tapuska, blink-dev
On Wed, Jul 6, 2016 at 2:44 PM, Dave Tapuska <dtap...@chromium.org> wrote:

I need to post a follow-up on this. In terms of Microsoft support it is not supported. I should have done a test which I did not. Rick indicates this will be a topic to discuss with them in a F2F later this month.

Ok. Does this mean we might not have enough consensus on details of the spec to ship this feature?

Rick Byers

unread,
Jul 6, 2016, 5:53:04 PM7/6/16
to Chris Harrelson, Dave Tapuska, blink-dev, Ted Dinklocker
There's some spec discussion here.  Personally I'd prefer to wait until we've got a public signal from Microsoft on this before shipping.  As Dave says, Microsoft put it on our agenda to discuss when we're in Redmond in 2 weeks.

Rick

Dave Tapuska

unread,
Jul 6, 2016, 6:07:38 PM7/6/16
to Rick Byers, Ted Dinklocker, Chris Harrelson, blink-dev

Ok. Then I'm fine punting on this until after the F2F. I was just following up some action items I had listed and this was one of them. I guess I should have checked with Rick before pre-emptively sending this. Ignore it for now.

dave

Ted Dinklocker

unread,
Jul 12, 2016, 1:08:10 PM7/12/16
to Dave Tapuska, Rick Byers, Chris Harrelson, blink-dev

All – This is Ted from the Edge Web Platform Team at Microsoft.

 

I just wanted to clarify some timeline information to the broader group as well. We are doing some architectural changes in this area that will likely take at least a year before I would anticipate that we would be able to deliver these new touch-action CSS properties. As noted – I will have the right people available from the Edge side during the face to face to discuss.

 

Ted

Reply all
Reply to author
Forward
0 new messages