Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

Notifications Not Working

  • 1 valiny
  • 1 manana an'ity olana ity
  • 181 views
  • Valiny farany nomen'i dojima

dojima
dojima
more options

Hello. I'm using a brand-new installation of Firefox 78.0.1 on a freshly installed copy of Windows 10 Pro. The only way I can get Firefox to display any notifications is by having alerts.useSystemBackend set to true. While this is set to false, notifications will not work. If I use this site to test them, it just says, 'queued for display', followed immediately by 'closed'. I've also tried creating a new profile and testing it again with no success. All sites were granted notification permissions in each case.

Thanks for any help.

Hello. I'm using a brand-new installation of Firefox 78.0.1 on a freshly installed copy of Windows 10 Pro. The only way I can get Firefox to display any notifications is by having alerts.useSystemBackend set to true. While this is set to false, notifications will not work. If I use [https://www.bennish.net/web-notifications.html this] site to test them, it just says, 'queued for display', followed immediately by 'closed'. I've also tried creating a new profile and testing it again with no success. All sites were granted notification permissions in each case. Thanks for any help.

Vahaolana nofidina

I managed to fix this and other issues by disabling the launcher process (browser.launcherProcess.enabled = false). It probably has something to do with the way I use Windows.

Hamaky an'ity valiny ity @ sehatra 👍 0

All Replies (1)

dojima
dojima Tompon'ny fanontaniana
more options

Vahaolana Nofidina

I managed to fix this and other issues by disabling the launcher process (browser.launcherProcess.enabled = false). It probably has something to do with the way I use Windows.