Add Fx132 support for Notification.silent #24631
Merged
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.
Summary
Firefox 132 supports the
Notification.silent
property.This PR adds Fx support to that data point.
See the shipping bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1809028
Test results and supporting details
I wrote a quick test case to test the property: see https://silent-notifications-test.glitch.me/.
I found the results somewhat inconclusive:
n.silent
returnstrue
.n.silent
returnstrue
(it supports the property).n.silent
returnsundefined
(it doesn't support the property).This suggests that Fx 132 does support it, but there is something going on with the actual notification firing. Is it buggy, or did I do something wrong with the permissions code? I will ask the Fx devs to look at it.
Related issues
Docs issue: mdn/content#36119