Bug 40263 – Add support for CSS Haptic properties

• Status: RESOLVED
• Resolution: WONTFIX
• Component: New Bugs

[Kim Grönholm]

Haptics is technology to apply tactile feedback to user's sense of touch
to emulate natural feel as feedback to an action
(http://en.wikipedia.org/wiki/Haptic_technology). With touch UI, the
simplest use of haptics is to provide sensory feedback with vibra when
clicking a link or pressing a button. Technologies are available to
simulate more realistic feel of physical keys or buttons.

On a mobile touch device, the user experience can be significantly
improved by using haptic feedback. Haptic feedback is commonly
implemented to predefined HTML components like <button>, but the
challenge for a web developer is that there is no way to apply haptics
to custom javascript components. Implementing feedback through a simple
javascript api is challenging as the feedback needs to be instantaneous
with substantially less than 100ms delay.

For a web developer, CSS is the most straightforward way to implement custom
javascript components with tactile feedback. For this we need to add support
for simple CSS haptic properties.

[Kim Grönholm]

Created attachment 58087 [details]
Adds CSS Haptic properties and values

[Kim Grönholm]

Created attachment 58166 [details]
Adds CSS haptic properties and values

Updated patch with necessary interfaces

[Eric Seidel (no email)]

What spec covers this?

[Eric Seidel (no email)]

Comment on attachment 58166 [details]
Adds CSS haptic properties and values

Please link to the spec you're implementing in the ChangeLog.

[Kim Grönholm]

Created attachment 58752 [details]
 Adds CSS haptic properties and values

Added a link to the Haptics CSS specification to the Changelog.

The specification can be found from:
http://portaali.org/~ilkkao/w3c/CSS/css3-haptics.html

[Kenneth Rohde Christiansen]

Comment on attachment 58752 [details]
 Adds CSS haptic properties and values

Given the comments on the www-style mailing list, I am not sure we should let this in the tree in it's current form.

[Simon Fraser (smfr)]

I agree with Kenneth. If Nokia need this, they should keep this in their own source tree for now.

[Dave Hyatt]

I agree.  The comments from www-style imply that this is unlikely to survive in this current form.  It's just going to change too much.

[Ademar Reis]

No need to block bug 32653 anymore, as haptics support has been reverted from 2.1

[Simon Fraser (smfr)]

Should we Resolve WONTFIX then?

[Kenneth Rohde Christiansen]

(In reply to comment #10)
> Should we Resolve WONTFIX then?

I would be fully OK with that.