- From: Anssi Kostiainen <anssi.kostiainen@nokia.com>
- Date: Mon, 14 Nov 2011 15:38:27 +0200
- To: ext Justin Lebar <jlebar@mozilla.com>
- Cc: Jonas Sicking <jonas@sicking.cc>, <public-device-apis@w3.org>, <public-device-status@w3.org>
On 11.11.2011, at 23.16, ext Justin Lebar wrote: >> An implementation should be allowed to disable vibration in any way if it wants to for security or privacy reasons. > > Jonas> I think "is" would be more correct than "should be". > > This is still too restrictive. An implementation may also disable > vibration just because the user asked. Also, I don't know what it > means to disable vibration "in any way." > > How about we add a step to the algorithm, between steps 8 and 9: > > "9) An implementation may abort the algorithm at this point. > > "Non-normative note: For example, an implementation might abort the > algorithm because the user has set a preference indicating that pages > at a given origin should never be able to vibrate the page, or an > implementation might cap the total amount of time a page may cause the > device to vibrate and reject requests in excess of this limit." This looks good to me. I added the step and the non-normative note you proposed to the spec. Thanks! -Anssi
Received on Monday, 14 November 2011 13:38:53 UTC