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

[lostncg]

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

• Query: api.Navigator.vibrate
• MDN URL: https://developer.mozilla.org/en-US/docs/Web/API/Vibration_API
• Report started: 2020-12-24T05:50:02.542Z

[rakuco]

User activation handling seems to be an implementation-specific feature at this point: it's not mentioned in the spec and was added to Blink in M60.

User activation itself is part of the HTML spec these days though, and if I understood this issue correctly the idea in this issue is to add more events to the list of activation triggering input events, right? If so, it might be better to file an issue against the HTML spec itself.

[johannhof]

FYI i filed #29 for having this in the spec. I agree that this issue can probably be closed as vibrate doesn't govern user activation rules.

[anssiko]

Thanks @johannhof, followed up in #29.