- From: <tomomi.imura@nokia.com>
- Date: Wed, 12 Feb 2014 23:09:35 +0000
- To: <public-web-mobile@w3.org>
On 2/11/14 9:24 AM, "ext Marcos Caceres" <w3c@marcosc.com> wrote: >Please see below... the same applies for this group, as vibration is >highly relevant to mobile devices. People are encouraged to review and >respond individually, but it might also be nice to have a group response. > I just wonder if there is any ways for a user to disable (mute) this feature, not entirely disabling a phone to vibrate, but per site. Or some sort of an UI indication so the user would know when the site buzzes. It may be confusing if a phone vibrate when you are not expecting. Usually, when your phone buzzes, you know you are getting a message etc. because you do see it coming on the notification system. And by the way, have you seen this? http://shkspr.mobi/blog/2014/01/malicious-use-of-the-html5-vibrate-api/ There are some interesting "malicious" use cases like faking a call. I would like to see actually useful use cases besides gaming though. tomomi > >Thanks! > >-- >Marcos Caceres > > >Forwarded message: > >> From: Arthur Barstow <art.barstow@nokia.com> >> To: public-webapps <public-webapps@w3.org> >> Date: Tuesday, February 11, 2014 at 5:09:24 PM >> Subject: RfC: LCWD of Vibration API; deadline March 4 >> >> This is a Request for Comments for the Device API WG's February 11 LCWD >> of the Vibration API: >> >> <http://www.w3.org/TR/2014/WD-vibration-20140211/> >> >> Individual WG members are encouraged to provide individual feedback. >> >> If anyone in WebApps wants to propose an official WG response, please >>do >> so ASAP, in reply to this e-mail so the WG can discuss it. >> >> Comments should be sent to public-device-apis @ w3.org (http://w3.org), >>with a subject >> prefix of [vibration] by March 4. >> >> -Thanks, AB >> >> On 2/11/14 12:00 PM, Hirsch Frederick (Nokia-CTO/Boston) wrote: >> > The Device API Working Group [1] has published a third Last Call >>working draft of the "Vibration API" specification today, 11 February >>2014 [2] and requests review comments from your groups (Web Applications >>WG, HTML WG). We are also interested in comments from others. >> > >> > The changes, based on review feedback during CR, are noted in the >>status section (with links to diffs) and include allowing >>implementations to truncate long vibrations, specifying how concurrent >>invocations in different browsing contexts are handled and clarifying >>the processing vibration patterns algorithm. >> > >> > The draft is available at >>http://www.w3.org/TR/2014/WD-vibration-20140211/ >> > >> > The Last Call period ends 4 March 2014 (3 weeks) - please send >>comments to the DAP public mailing list with "[vibration]" at the start >>of the Subject line. Indications of support for the changes are welcome. >> > >> > Thanks >> > >> > regards, Frederick >> > >> > Frederick Hirsch, Nokia >> > Chair, W3C DAP Working Group >> > >> > [1] http://www.w3.org/2009/dap/ >> > >> > [2] http://www.w3.org/blog/news/archives/3653 > > >
Received on Wednesday, 12 February 2014 23:11:46 UTC