- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Thu, 27 Mar 2014 07:41:27 -0400
- To: Jacob Rossi <Jacob.Rossi@microsoft.com>, Rick Byers <rbyers@google.com>
- CC: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
On 3/26/14 6:58 PM, ext Jacob Rossi wrote: > > I don’t have a problem removing the sentence. As you said, I don’t > really think it makes a difference whether the sentence exists or > not—the decision to or not to expand it to other elements would be > made on its own merits at that point in time (not on whether the > previous spec allowed or disallowed it). > I did a quick investigation to try to understand why that note was added to the spec ... The changeset that added the Note is from April 18 2013 [CS] (after LC#1 and before CR#1). The change is based on a resolution made during the April 9 call [Mins] to address one of the comments Boris made [BZ]. I agree with the proposal to remove the sentence. However, I think it would be good to ask Boris to review the normative changes (i.e "Applies to: ...") as well as the Note. -Thanks, AB [CS] <https://dvcs.w3.org/hg/pointerevents/rev/1fca9785e96f> [BZ] <http://lists.w3.org/Archives/Public/public-pointer-events/2013AprJun/0016.html> [Mins] <http://www.w3.org/2013/04/09-pointerevents-minutes.html#item06> > *From:*Rick Byers [mailto:rbyers@google.com] > *Sent:* Wednesday, March 26, 2014 3:34 PM > *To:* Jacob Rossi > *Cc:* Arthur Barstow; Cathy.Chan@nokia.com; > public-pointer-events@w3.org; gnanasekar.s@samsung.com > *Subject:* Re: Touch-action to SVG elements > > On Wed, Mar 26, 2014 at 4:15 PM, Jacob Rossi > <Jacob.Rossi@microsoft.com <mailto: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? >
Received on Thursday, 27 March 2014 11:42:36 UTC