api.Navigator.vibrate - Throwing intervention error of vibration after user already interacted with UI. #8262
Labels
invalid
Invalid issues or pull requests (wrong repo, spam, duplicates, etc.). This won't get merged. Sorry!
Google Chrome Version 87.0.4280.88 (Official Build) (x86_64)
What information was incorrect, unhelpful, or incomplete?
Missing one Vibration API to check whether developer can trigger vibration or not.
What did you expect to see?
Allow me to trigger vibration when user interact with UI elements.
Did you test this? If so, how?
I tried to trigger vibration after element clicked (click and on hold), and trigger event in touchmove, but if finger still on hold, vibrate API will still assume user not yet interact, and throw error below.
[Intervention] Blocked call to navigator.vibrate because user hasn't tapped on the frame or any embedded frame yet: .
MDN page report details
api.Navigator.vibrate
The text was updated successfully, but these errors were encountered: