Closed Bug 1809284 Opened 3 years ago Closed 2 years ago

Add support for Web Notifications API's silent flag

Categories

(GeckoView :: General, task)

All
Android
task

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1796766

People

(Reporter: csadilek, Unassigned)

Details

From github: https://github.com/mozilla-mobile/fenix/issues/18145.

What is the user problem or growth opportunity you want to see solved?

As described in the Web Notifications API standard, the browser should support a silent flag for notifications:

serviceWorkerRegistration.showNotification('Example', { silent: true })

Currently Firefox ignores this flag and always plays a sound.

How do you know that this problem exists today? Why is this important?

At Pushpad we received requests from customers for this option. Chrome and derivates already support it and should be easy to implement in Firefox.

Who will benefit from it?

Users will benefit from it since they can receive updates that are not time-sensitive, without disturbing them for each notification.

Please fix this since it is important for the user experience: e.g. a web app may want to mute a conversation, or a news website prefers to disable the sound since notifications are not urgent, etc.

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

Verdi says:

Commenting for UX - this looks good.

https://github.com/mozilla-mobile/fenix/issues/18145#issuecomment-1397381901

See the GitHub issue for screenshots and implementation suggestions.

Since this bug is about the Web Notifications API, the GeckoView component might be a better place for this bug.

Severity: -- → N/A
Type: defect → task
Component: General → Core
Product: Fenix → GeckoView
Summary: Notification silent flag for web notifications → Add support for Web Notifications API's silent flag

Closing as a duplicate of bug 1796766 which already landed.

Status: NEW → RESOLVED
Closed: 2 years ago
Duplicate of bug: 1796766
Resolution: --- → DUPLICATE
Component: Core → General
You need to log in before you can comment on or make changes to this bug.