W3C home > Mailing lists > Public > www-style@w3.org > June 2010

Re: Haptics CSS extension proposal

From: Brad Kemper <brad.kemper@gmail.com>
Date: Fri, 25 Jun 2010 08:07:29 -0700
Cc: <www-style@w3.org>
Message-Id: <52A852BA-D50D-4AA0-B0D5-F1C65FA646EE@gmail.com>
To: <kim.1.gronholm@nokia.com>

On Jun 24, 2010, at 11:55 PM, <kim.1.gronholm@nokia.com> wrote:

> To Brad Kemper:
> Regarding the use of the appearance property to specify tactile feedback: Clearly the tactile feedback is a new thing, and what is the best way for enabling developers to define tactile feedback for web elements, is not a simple question. We evaluated different possibilities and realized that this is a new distinct feature and therefore needs a new distinct interface. I understand your initial impression as it is normal that when a new feature like this evolves, first we want to think if and how it would fit to the existing frameworks. We thought about this with the conclusion that it certainly needs its own interface.
> Currently the key use case is to be able to create custom JS controls that have the same tactile feedback than native controls of the underlying platform. This is independent from the appearance, would you agree? Same goes for links: It should be possible to implement a custom control that feels like a link without actually being a traditional link.

I don't know. Currently, there are visual and behavior qualities of some OS controls that are hard or impossible to recreate using just CSS and DIVs, even without haptics. I think it would certainly be reasonable to have haptics in JavaScript, and since you are talking about JS controls, that would seem to be enough (use touch events to trigger them).
Received on Friday, 25 June 2010 15:08:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:47 UTC