Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Issue 258459 touch-action CSS property
Starred by 27 users Project Member Reported by rbyers@chromium.org, Jul 9 2013 Back to list
Status: Verified
Owner:
Closed: Mar 2014
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android, Windows, Chrome
Pri: 1
Type: Launch-OWP
Launch-Accessibility: ----
Launch-Legal: ----
Launch-M-Approved: ----
Launch-M-Target: ----
Launch-Privacy: ----
Launch-Security: ----
Launch-Status: ----
Launch-Test: ----
Launch-UI: ----

Blocked on:
issue 241964
issue 329559

Blocking:
issue 196799
issue 352134
issue 404128



Sign in to add a comment
Change description:
New CSS properties (based on pointer events) to enable websites to declaratively state how touches should be handled, without necessarily blocking on the main thread.  Provides performance and functionality benefits to sites using touch events, while also enabling great pointer event polyfills.

Changes to API surface:
- new CSS property: touch-action 
- new CSS property: touch-action-delay (exact name TBD)

Links:
touch-action is part of the pointer events specification (current in CR) here: http://www.w3.org/TR/pointerevents/#the-touch-action-css-property

To make it also apply fully to touch events (in addition to pointer events) without breaking compatibility an additional property is necessary.  Brainstorming has started here: https://docs.google.com/a/chromium.org/document/d/1CV2AXyrdPdGSRypAQcfGrgQVuWYi50EzTmVsMLWgRPM/edit#heading=h.93armas5zeh0.  Once we prove an implementation is feasible in chromium, the WebEvents working group has agreed to work on a specification. 

Support in other browsers:
Internet Explorer:
IE10 implements touch-action with a vendor prefix (http://msdn.microsoft.com/en-us/library/windows/apps/hh767313.aspx), but will have no need for touch-action-delay as IE never delays touch actions and will never support touch events.

Firefox:
Support for pointer events is coming: https://bugzilla.mozilla.org/show_bug.cgi?id=822898.  We've had informal discussions about how touch-action should apply to touch events, and Matt Brubeck has indicated he likes the direction of my proposal (but I don't believe anyone has dug into it deeply).

Safari:
No support planned.

Opera:
Informal support for this approach.
 
Blocking: chromium:196799
Comment 2 by rbyers@chromium.org, Aug 16 2013
Blocking: chromium:168644
Comment 3 by meh@chromium.org, Nov 4 2013
Labels: -M-32 M-X
Moving to M-X as it looks like this will not ship in M-32.
Comment 4 by rbyers@chromium.org, Dec 18 2013
Blockedon: chromium:297781
Comment 5 by rbyers@chromium.org, Dec 18 2013
Blocking: -chromium:168644
Comment 6 by rbyers@chromium.org, Dec 18 2013
Blockedon: -chromium:297781 chromium:329559
Cc: meh@chromium.org
Labels: -M-X M-34
I'd like to plan on shipping the core touch-action support ( issue 297781 ) in M-34 or M-35.  The touch-action-delay stuff ( issue 329559 ) will come later (perhaps I should be filing a 2nd Launch bug for that).
Labels: -M-34 M-35
Labels: -Pri-2 Pri-1
Comment 9 by rbyers@chromium.org, Mar 10 2014
Summary: touch-action CSS property (was: touch-action CSS properties for touch events)
Blocking: chromium:352134
Project Member Comment 12 by bugdroid1@chromium.org, Mar 14 2014
The following revision refers to this bug:
  http://src.chromium.org/viewvc/blink?view=rev&rev=169275

------------------------------------------------------------------
r169275 | rbyers@chromium.org | 2014-03-14T20:49:24.395119Z

Changed paths:
   M http://src.chromium.org/viewvc/blink/trunk/Source/platform/RuntimeEnabledFeatures.in?r1=169275&r2=169274&pathrev=169275
   M http://src.chromium.org/viewvc/blink/trunk/LayoutTests/virtual/stable/webexposed/css-properties-as-js-properties-expected.txt?r1=169275&r2=169274&pathrev=169275

Enable CSS touch-action by default

Blink intent to ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/sc5lHnlcLvM

Removing the unused flag is tracked in  crbug.com/258459 

BUG= 258459 

Review URL: https://codereview.chromium.org/198103007
-----------------------------------------------------------------
Status: Fixed
Correction to the commit message in the above CL: removing the unused flag is tracked by  issue 352134  (not this issue).
Comment 15 by krisr@chromium.org, Mar 25 2014
Labels: Cr-Internals-Input-Touch-Pad
Labels: VerifyIn-35
Comment 17 by krisr@chromium.org, May 14 2014
Labels: -VerifyIn-35
Project Member Comment 18 by bugdroid1@chromium.org, May 15 2014
Labels: merge-merged-1916
The following revision refers to this bug:
  http://src.chromium.org/viewvc/blink?view=rev&rev=174108

------------------------------------------------------------------
r174108 | rbyers@chromium.org | 2014-05-15T22:07:35.133649Z

Changed paths:
   M http://src.chromium.org/viewvc/blink/branches/chromium/1916/Source/platform/RuntimeEnabledFeatures.in?r1=174108&r2=174107&pathrev=174108
   M http://src.chromium.org/viewvc/blink/branches/chromium/1916/LayoutTests/virtual/stable/webexposed/css-properties-as-js-properties-expected.txt?r1=174108&r2=174107&pathrev=174108

Revert 169275 "Enable CSS touch-action by default"

Disabling touch-action for M35 only due to website bugs
Still enabled in M36+

> Enable CSS touch-action by default
> 
> Blink intent to ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/sc5lHnlcLvM
> 
> Removing the unused flag is tracked in  crbug.com/258459 
> 
> BUG= 258459 
> 
> Review URL: https://codereview.chromium.org/198103007

TBR=rbyers@chromium.org
BUG= 372357 

Review URL: https://codereview.chromium.org/284123006
-----------------------------------------------------------------
Note that this was disabled in Chrome 35 for  issue 372357  to buy us some time getting broken websites fixed..  It's still on in Chrome 36+.
Labels: -M-35 M-36
Status: Verified
Blocking: chromium:404128
Sign in to add a comment