[ 
https://issues.apache.org/jira/browse/CB-14022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429799#comment-16429799
 ] 

jcesarmobile commented on CB-14022:
-----------------------------------

If I call vibrate on device ready event I get an error message pointing to 
https://www.chromestatus.com/feature/5644273861001216

{quote}
Calls to navigator.vibrate will immediately return 'false' if user hasn't 
tapped on the frame or any embedded frame yet. The Vibrate API is being abused 
by malicious sites. This extends what we do for cross-origin iframes to all 
frames including top-level page
{quote}
Looks like it's a new policy.

If I use it on a button click it works fine as I have touched the screen to tap 
the button.

I don't think we can fix this as we only set the permission and use the webview 
implementation, so we can revert the native code we had, or just document this 
as a quirk for Android. [~bowserj] thoughts?

> Vibrate plugin does not work
> ----------------------------
>
>                 Key: CB-14022
>                 URL: https://issues.apache.org/jira/browse/CB-14022
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-android
>    Affects Versions: cordova@7.0.0, cordova-android-7.0.0
>            Reporter: Mahesh Kanniah
>            Assignee: Joe Bowser
>            Priority: Minor
>             Fix For: Master
>
>
> navigator.vibrate does not work.
> Used to work in earlier versions but just fails to work.
> Tested on multiple devices running different android versions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

Reply via email to