New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicate/similar web notifications sent #7902
Comments
I have the same, also in v2.4.2. |
This has been bugging me for a long time, but I finally understand what's going on. This behavior was introduced in 4b94e9c. So I guess we have to replace the notification without triggering a new one, if that's possible at all. EDIT: That's what the |
Hm, this discarded situation is weird, I have a pebble and what I see is this: A first notification arrives, in the format of |
That looks like a bug in the browser, the first notification should be entirely discarded. And it should also not re-notify… I wonder if some properties changing between the two versions cause that… Alternatively, we could postpone displaying a notification to when the subsequent API call returns… |
It seems the push example by google postpones until the API answers: |
…) (mastodon#8396) * Only display web push notifications after API call (fixes mastodon#7902) * Decode then truncate instead of truncating then decoding in webpush serializer
Follow and mention notifications are being sent twice, with slightly different text:
Mentions:
Follows:
master
(If you're a user, don't worry about this).The text was updated successfully, but these errors were encountered: