Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

api.Navigator.vibrate - Throwing intervention error of vibration after user already interacted with UI. #8262

Closed
lostncg opened this issue Dec 24, 2020 · 1 comment
Labels
invalid Invalid issues or pull requests (wrong repo, spam, duplicates, etc.). This won't get merged. Sorry!

Comments

@lostncg
Copy link

lostncg commented Dec 24, 2020

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
@lostncg
Copy link
Author

lostncg commented Dec 24, 2020

Move issue to w3c/vibration#25
Issue closed.

@lostncg lostncg closed this as completed Dec 24, 2020
@queengooborg queengooborg added the invalid Invalid issues or pull requests (wrong repo, spam, duplicates, etc.). This won't get merged. Sorry! label Dec 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid Invalid issues or pull requests (wrong repo, spam, duplicates, etc.). This won't get merged. Sorry!
Projects
None yet
Development

No branches or pull requests

2 participants