Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Notification badge is not showing the counter on windows 11 pwa #27575

Closed
chagai95 opened this issue Jun 14, 2024 · 3 comments
Closed

Notification badge is not showing the counter on windows 11 pwa #27575

chagai95 opened this issue Jun 14, 2024 · 3 comments
Labels
A-Notifications S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter Z-Experimental

Comments

@chagai95
Copy link
Contributor

Steps to reproduce

install element as a pwa

Outcome

What did you expect?

notification counter

What happened instead?

none is shown

Operating system

Windows 11

Browser information

Chrome

URL for webapp

No response

Application version

No response

Homeserver

No response

Will you send logs?

No
@dosubot dosubot bot added A-Notifications S-Minor Impairs non-critical functionality or suitable workarounds exist labels Jun 14, 2024
@t3chguy
Copy link
Member

t3chguy commented Jun 14, 2024

Logs would be needed here. We do call setAppBadge so something in the browser is stopping it working. https://developer.mozilla.org/en-US/docs/Web/API/Navigator/setAppBadge claims to work on Chrome on Windows

@t3chguy t3chguy added X-Needs-Info This issue is blocked awaiting information from the reporter Z-Experimental labels Jun 14, 2024
@chagai95
Copy link
Contributor Author

Somehow it started working now, I refreshed, maybe it was stuck somewhere, I also sent logs, thx!

@t3chguy
Copy link
Member

t3chguy commented Jun 14, 2024

Unfortunately the logs do not shed any light on any failures with Navigator::setAppBadge so this issue seems to be entirely on the browser's side. In light of that + the fact that a refresh fixed it I will be closing this issue

@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Notifications S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect X-Needs-Info This issue is blocked awaiting information from the reporter Z-Experimental
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@t3chguy @chagai95