Issue 638388  has been merged into this issue.

 Issue 507703  has been merged into this issue.

Emily, would you mind documenting (2) at the WICG interventions github whenever you have something worth sharing more broadly?

We have (1) at https://github.com/WICG/interventions/issues/25.

I've added (2) to the intervention backlog (bit.ly/proposed-interventions) and assigned you as the PM to drive it* with Bin Lu marked as tentative engineer owner. We'll ping you / read the relevant bug for updates (e.g. following up with spec/interventions requirements & process, quarterly newsletter).

Best,


*: let me know if you would prefer that someone else takes care of it :)

I have not once seen this api used in a non abusive way and as a web developer I have zero interest in using it. If the permissions cannot be altered I'd rather see the feature completely removed until that has been implemented. There isn't even an option to disable vibration globally in the settings.

When we've broken vibrate in the past, we've definitely heard from people who are using it legitimately. As per https://www.chromestatus.com/features/5644273861001216 vibrate requires a user gesture from Chrome 60 onwards. 

We believe this will address the abuse of this API, but if you see any abusive uses of vibrate in Chrome 60 or later, we'd love to hear about them so we can see what ca be done to mitigate it further.

Closing the bug assuming that the recent complains were from older Chrome's. We can reopen or open new bugs if people are still seeing problems in Chrome 60+.