Windows 10 bereikte EO (einde ondersteuning) op 14 oktober 2025. Als je Windows 10 gebruikt, lees dan dit artikel.

Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Show web push notifications using Windows 10 / OSX native API

  • 2 antwoorden
  • 1 heeft dit probleem
  • 175 weergaven
  • Laatste antwoord van maaxxify

chall3ng3r
chall3ng3r

Why native API? Because when there's a new web push notification and user misses it, there's no way to find out what it was. Using OS's native API will allow the notification to be kept in Notification Panel unit users sees it and dismiss it.

I believe Linux too have some sort of native notification APIs too.

It'd be really awesome to have native notifications support on operating systems which now have pretty good notifications APIs.

Why native API? Because when there's a new web push notification and user misses it, there's no way to find out what it was. Using OS's native API will allow the notification to be kept in Notification Panel unit users sees it and dismiss it. I believe Linux too have some sort of native notification APIs too. It'd be really awesome to have native notifications support on operating systems which now have pretty good notifications APIs.

Alle antwoorden (2)

user1929
user1929

On macOS, Firefox should be using the native API already - are you seeing something else?

On Windows, this is currently being worked on; you can click the "follow" button here to get notified when this feature is added.

maaxxify
maaxxify

In NIghtly 67 on Windows 10 this feature still hasn't landed, although the corresponding thread on Bugzilla is marked as resolved.

https://bugzilla.mozilla.org/show_bug.cgi?id=1155505

Any clues what's happening with this?