Re: [vibration] api.Navigator.vibrate - Throwing intervention error of vibration after user already interacted with UI. (#25)

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](https://www.chromestatus.com/feature/5644273861001216).

User activation itself is part of [the HTML spec](https://html.spec.whatwg.org/#user-activation-processing-model) 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](https://html.spec.whatwg.org/#activation-triggering-input-event), right? If so, it might be better to file an issue against the HTML spec itself.

-- 
GitHub Notification of comment by rakuco
Please view or discuss this issue at https://github.com/w3c/vibration/issues/25#issuecomment-758576396 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 12 January 2021 10:55:06 UTC