Remove Notification's vibrate feature#241
Conversation
Vibration via notifications does not appear to have interoperable browser support. Current implementation status appears to be: * Chromium-based browsers: implemented for Android. * Firefox: [not implemented](https://bugzilla.mozilla.org/show_bug.cgi?id=1273641) after 9 years of development. * WebKit: not implemented. As a result, the feature is not interoperable across browser engines. If there is implementer interest in maintaining this feature, that information would be helpful in determining whether it should remain in the specification.
| Translation: ja https://triple-underscore.github.io/notifications-ja.html | ||
| Translation: zh-Hans https://htmlspecs.com/notifications/ | ||
| Translation: ko https://ko.htmlspecs.com/notifications/ | ||
| Ignore MDN Failure: #dom-notification-vibrate |
There was a problem hiding this comment.
I think we should fix this on the MDN side, ideally before landing.
There was a problem hiding this comment.
agree... was just making the bot happy.
|
@saschanaz, is this ok on with you? @foolip, you ok with this change from the Chrome side? |
|
Moz is happy with the removal. |
- Remove `Ignore MDN Failure` suppressor for #dom-notification-vibrate; the MDN data should be fixed upstream instead - Restore "or vibrations" to the silent preference description; the silent flag suppresses vibrations independently of the vibrate feature
The algorithm had a single step, so inline it at the call site and remove the "Alerting the end user" section.
|
Can this be merged? @foolip ping? |
|
I haven't worked on this feature in Chromium, looping in @beverloo who originally shipped this: I can't find use counters for this so I don't know anything about feasibility of removal. For now, please assume Google would object to removal. I understand that won't change implementer interest, but we want everything we ship to be spec'd somewhere, so some action is needed here. |
|
happy to move it to compat spec if that helps. |
|
I'm not sure how that helps? |
|
I'm going to defer to @beverloo here as someone who helped ship the original implementation, and as someone with more knowledge here to make the final decision about supporting this feature. Like @foolip has said above, I can't seem to find a lot of metrics about its usage, but allowing web developers to show notifications and support vibrations patterns through the API seems like a reasonable behavior to be supported. |
|
Android deprecated support for per-notification vibration patterns with Android 8, so availability will be rare at best now. No concerns at all with this removal. |
|
Thanks @beverloo! Nothing further from me either, if it's gone from Android I'm sure we can eventually remove it from Chromium. |
|
Filed MDN issue mdn/mdn#825 cc @hamishwillee for guidance |
|
Could someone please file a Chrome bug for me? |
|
@marcoscaceres created crbug.com/511304741 for you. |
|
@whatwg/documentation could you all help with updating MDN so it no longer references this document for the vibrate feature? That way we can land this PR and remove it completely. |
annevk
added
do not merge yet
6 participants
Remove vibration support from notifications
This PR removes vibration support from notifications.
The feature does not have interoperable browser implementations.
Current implementation status appears to be:
As a result, the feature is effectively a single-engine extension.
The generic Vibration API (
Navigator.vibrate) remains available for user agents that support vibration.If there is implementer interest in maintaining this feature, that information would be helpful in determining whether it should remain in the specification.
(See https://whatwg.org/working-mode#changes for more details.)(https://github.com/whatwg/meta/blob/main/COMMITTING.md) to use.
💥 Error: 422 Unprocessable Entity 💥
PR Preview failed to build. (Last tried on May 9, 2026, 12:44 PM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 Spec Generator - Spec Generator is the web service used to build bikeshed/ReSpec specs
🔗 Related URL
Error output:
[ { "lineNum": null, "messageType": "warning", "text": "Skipped generating some MDN panels, because the following IDs weren't present in the document. Use `Ignore MDN Failure` if this is expected.\n #dom-notification-vibrate" }, { "lineNum": null, "messageType": "failure", "text": "Did not generate, due to errors exceeding the allowed error level." } ]This seems to be an issue with the Spec Generator service. PR Preview doesn't manage this service and so has no control over it. If you've identified an issue with it, you can report the issue to the maintainers of Spec Generator directly. Please be courteous. Thank you!
If you don't have enough information above to solve the error by yourself or if the issue doesn't seem related to Spec Generator, you can file an issue with PR Preview.