Remove Notification's vibrate feature#241
Open
marcoscaceres wants to merge 3 commits intowhatwg:mainfrom
Open
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.
annevk
approved these changes
Mar 15, 2026
notifications.bs
Outdated
| 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 |
Member
There was a problem hiding this comment.
I think we should fix this on the MDN side, ideally before landing.
Member
Author
There was a problem hiding this comment.
agree... was just making the bot happy.
marcoscaceres
commented
Mar 15, 2026
Member
Author
|
@saschanaz, is this ok on with you? @foolip, you ok with this change from the Chrome side? |
Member
|
Moz is happy with the removal. |
saschanaz
suggested changes
Mar 15, 2026
Comment on lines
+84
to
+85
| initially null. When true, indicates that no sounds should be made. When null, indicates that | ||
| producing sounds should be left to platform conventions. |
Member
There was a problem hiding this comment.
This should be kept intact, because notifications can still make vibrations regardless of Vibration API?
| <a for=notification>vibration pattern</a>, if any. | ||
| </ol> | ||
| </div> | ||
| <p>The <dfn>alert steps</dfn> for alerting the end user about a given <a for=/>notification</a> are |
Member
There was a problem hiding this comment.
Not necessarily something should be done in this PR, but this can probably just be inlined.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.