Path: csiph.com!1.us.feeder.erje.net!3.us.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!usenet.goja.nl.eu.org!news.freedyn.de!speedkom.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Jan Bruns <ebay@abnuto.de>
Newsgroups: comp.lang.javascript
Subject: Re: webpush duplicate notifications
Date: 27 Jun 2022 08:50:17 GMT
Lines: 22
Message-ID: <jht9a9F2p8rU1@mid.individual.net>
References: <jhig9bF9s16U1@mid.individual.net> <jhpvbsFd85oU1@mid.individual.net> <jhq7h0Fd85oU2@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net bBn0zkKm+X7ssUWrwTuYaA9zQGELfDIs9WhBuUYKeiMmT8eA8q
Cancel-Lock: sha1:fY4OBN+Bqytt19hq1ikxVB+pRh0=
User-Agent: Pan/0.145 (Duplicitous mercenary valetism; d7e168a git.gnome.org/pan2)
Xref: csiph.com comp.lang.javascript:40935

Jan Bruns:

> What else could be tried?


Well, after getting payload-data to work using

https://github.com/web-push-libs/ecec

I found out that even that way (without fetch() in the service worker 
code) the duplicate notification problem persisted.

And the problem was: 

For Desktop Chromium, it's not enough to simply call showNotification(). 
The push-event also needs to be waitUntil'ed for the promise returned by  
showNotification().

Gruss

Jan Bruns