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

Re: Touch-action to SVG elements

From: Rick Byers <rbyers@google.com>
Date: Wed, 26 Mar 2014 18:34:26 -0400
Message-ID: <CAFUtAY-cA_EVsN3WP8ootnEEBD86RXhV1KNWbdGMuR1yEfDmzA@mail.gmail.com>
To: Jacob Rossi <Jacob.Rossi@microsoft.com>
Cc: Arthur Barstow <art.barstow@nokia.com>, "Cathy.Chan@nokia.com" <Cathy.Chan@nokia.com>, "public-pointer-events@w3.org" <public-pointer-events@w3.org>, "gnanasekar.s@samsung.com" <gnanasekar.s@samsung.com>
On Wed, Mar 26, 2014 at 4:15 PM, Jacob Rossi <Jacob.Rossi@microsoft.com>wrote:

> I agree "except" is clearer.  I pushed an update to fix this and the out
> of date note that Rick pointed out:
>
>
> https://dvcs.w3.org/hg/pointerevents/raw-file/tip/pointerEvents.html#the-touch-action-css-property
>
> "Applies to: all elements except: non-replaced inline elements, table
> rows, row groups, table columns, and column groups"
>
> "Note: The touch-action property applies only to elements that support
> both the CSS width and height properties (see [CSS21] ). This restriction
> is designed to facilitate user agent optimizations for low-latency touch
> actions. For elements not supported by default, such as <span> which is a
> non-replaced inline element (see [HTML5]), authors can set the display CSS
> property to a value, such as block, that supports width and height. Future
> specifications could extend this API to all elements.."
>

Love it!  One pre-existing issue: I've always been uneasy about the 'future
specifications' part - that would be a breaking change with potential web
compat impact (eg. preventing scrolling in scenarios that scrolling is
possible today).  I'd prefer we just remove any speculation here (whether
or not we could make such a change won't be impacted by what we write
here).  I.e. just axe the last sentence.  WDYT?


>
> -Jacob
>
>
> -----Original Message-----
> From: Arthur Barstow [mailto:art.barstow@nokia.com]
> Sent: Wednesday, March 26, 2014 11:19 AM
> To: Cathy.Chan@nokia.com; Jacob Rossi; rbyers@google.com
> Cc: public-pointer-events@w3.org; gnanasekar.s@samsung.com
> Subject: Re: Touch-action to SVG elements
>
> On 3/26/14 1:47 PM, ext Cathy.Chan@nokia.com wrote:
> >
> > Maybe it's just me, but as a non-native speaker, I had to think twice
> > to parse the word "but". I'd suggest using ", except" instead.
> >
>
> I don't have a strong preference either way but agree "except" (or
> "except:") is a bit clearer.
>
>
> On 3/25/14 3:17 PM, ext Rick Byers wrote:
>
> > "The touch-action property is restricted to block-level elements and
> > SVG elements to facilitate low-latency touch actions. Future
> > specifications could extend this API to all elements. Authors can use
> > the display CSS property to make other elements generate a block box
> > for use with touch-action."
>
> Good catch. (Although rather than repeat the list, perhaps a new link to
> the normative text above could be used.)
>
> -AB
>
> > *From:*ext Jacob Rossi [mailto:Jacob.Rossi@microsoft.com]
> > *Sent:* Tuesday, March 25, 2014 2:59 PM
> > *To:* Rick Byers
> > *Cc:* public-pointer-events@w3.org; gnanasekar.s@samsung.com; Douglas
> > Schepers
> > *Subject:* RE: Touch-action to SVG elements
> >
> > Spec has been updated:
> >
> >
> https://dvcs.w3.org/hg/pointerevents/raw-file/tip/pointerEvents.html#the-touch-action-css-property
> >
> > -Jacob
> >
> >
>
>
Received on Wednesday, 26 March 2014 22:35:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:26 UTC