Re: Haptics CSS extension proposal

Hi there,

On Fri, Jun 25, 2010 at 3:55 AM,  <kim.1.gronholm@nokia.com> wrote:
> 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.

What about standard html forms, such as buttons? I see that you have
haptic-tap-type, which defines "button" etc. but isnt this very
specific?

I think we should follow CSS3-UI (http://www.w3.org/TR/css3-ui/) and
use <appearance> for this. I believe this can currently be used with
appearance: and font:

input[type=button] {
  appearance:push-button; /* expected from UA defaults */
  font:push-button;
}

> Using the combination of WAI-ARIA and the appearance properties has the same issues as described above. If we want to be able to define tactile feedback without defining some specific appearance or ARIA role (or other way around), we need to have an own interface for specifying it. The interface we are proposing is simple and covers well the current key use case described above. It is also nicely expandable in the future if tactile feedback technologies evolve and enable more sophisticated features.

Have you already considered how it might involve, or do you have some
more sophisticated use-cases in mind that you want to use in the
future?

Cheers,
Kenneth

--
Kenneth Rohde Christiansen
Technical Lead / Senior Software Engineer
Qt Labs Americas, Nokia Technology Institute, INdT
Phone  +55 81 8895 6002 / E-mail kenneth.christiansen at openbossa.org

Received on Friday, 25 June 2010 12:46:17 UTC