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

RE: Haptics CSS extension proposal

From: <kim.1.gronholm@nokia.com>
Date: Wed, 16 Jun 2010 09:35:22 +0200
To: <brad.kemper@gmail.com>, <www-style@w3.org>
Message-ID: <5DCCA44134F9AE4FBDB354CE5E4AF9885876E7A69D@NOK-EUMSG-04.mgdnok.nokia.com>
Hi, and sorry for this sudden burst of e-mails. I had an issue with spam filtering and my mails didn't reach the mailing list at first.

Tying the tactile feedback to the appearance property causes problems when a web developer wants to make a custom visual representation of e.g. a checkbox but still have proper tactile feedback of a checkbox. So in my opinion the visual appearance and haptic properties should be possible to be defined separately.

Br, Kim Grönholm

>-----Original Message-----
>From: ext Brad Kemper [mailto:brad.kemper@gmail.com]
>Sent: 14. kesäkuuta 2010 17:47
>To: Daniel Glazman
>Cc: www-style@w3.org; Gronholm Kim.1 (Nokia-D/Tampere); Barstow Art
>(Nokia-CIC/Boston); Knoll Lars (Nokia-D-Qt/Oslo); Oksanen Ilkka (Nokia-
>D/Espoo); Haverinen Henry (Nokia-D-Qt/Oslo)
>Subject: Re: Haptics CSS extension proposal
>My initial impression is that most of this (aside from 'haptic-tap-
>strength') should be handled by the 'appearance' property, to get a UA-
>appropriate representation of a button, checkbox, etc.. That would also
>handle the :active state of the button, etc. automatically. The state of
>the checkbox or deciding if something is a link or not would be decided
>by the document language and DOM.
Received on Wednesday, 16 June 2010 07:37:18 UTC

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