There's no permissions associated with vibrate. So if the function is not there then it means that the hardware is lacking a vibration motor.
/ Jonas On Fri, Mar 7, 2014 at 12:39 AM, JOSE MANUEL CANTERA FONSECA <[email protected]> wrote: > Yes, but the function could not be there either because the app does not > have permissions or because the user have not granted those permissions (in > the prompt). So the developer could not distinguish the situation and offer > the user the proper options and messages. > ________________________________ > De: Jonas Sicking [[email protected]] > Enviado: jueves, 06 de marzo de 2014 17:10 > Para: JOSE MANUEL CANTERA FONSECA > CC: [email protected]; Marcus Cavanaugh > Asunto: Re: [b2g] Vibrate API Feature Detection (Flatfish?) > > For most other APIs in the webplatform you check if you can use an API by > checking if the functions are there. I'd rather be consistent with that as > it is something that web developers are familiar with. > > / Jonas > > On Mar 5, 2014 2:00 PM, "JOSE MANUEL CANTERA FONSECA" <[email protected]> wrote: >> >> El 12/02/14 12:19, "Jonas Sicking" <[email protected]> escribió: >> >> >Hmm.. We should probably make the function not exist if the hardware >> >doesn't support vibration. >> >> Provided that the same problem may arise with other APIs (telephony, etc.) >> What about having a capabilities API that allows to query what >> capabilities are supported and what are not by a specific device? >> >> > >> >/ Jonas >> > >> >On Tue, Feb 11, 2014 at 2:50 PM, Marcus Cavanaugh <[email protected]> >> >wrote: >> >> There's a bug[1] filed for removing the Vibrate option from Clock if >> >> the >> >> hardware doesn't support vibration. According to the IDL docs for >> >> navigator.vibrate, " If the device does not have a vibrator, this >> >>function >> >> does nothing.", so I can't just feature detect on "navigator.vibrate". >> >> >> >> Is there any existing API or feature detect implemented to actually >> >>detect >> >> whether a device has a vibration motor? >> >> >> >> Marcus >> >> >> >> [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=964770 >> >> _______________________________________________ >> >> dev-b2g mailing list >> >> [email protected] >> >> https://lists.mozilla.org/listinfo/dev-b2g >> >_______________________________________________ >> >dev-b2g mailing list >> >[email protected] >> >https://lists.mozilla.org/listinfo/dev-b2g >> > >> >> >> >> ________________________________ >> >> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar >> nuestra política de envío y recepción de correo electrónico en el enlace >> situado más abajo. >> This message is intended exclusively for its addressee. We only send and >> receive email on the basis of the terms set out at: >> http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar > nuestra política de envío y recepción de correo electrónico en el enlace > situado más abajo. > This message is intended exclusively for its addressee. We only send and > receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
