WebCord icon indicating copy to clipboard operation
WebCord copied to clipboard

Notifications lack messages or won't even show when webcord is minimised

Open Meister1593 opened this issue 2 years ago • 5 comments

Aknowledgements

  • [X] I have checked that there's no other issue describing the same or similar problem that I currently have, regardless if it has been closed or open.

  • [ ] I can confirm that this is not an issue with the Discord website, but it is a problem specific to the WebCord itself. I have tested if this bug occurs on Chromium/Chrome or any other Chromium-based browser that uses unpatched/upstream Chromium engine. ~~(Actually, there is no notifications on web version at all as far as i am aware)~~

  • [ ] I have tried running the build from the master branch and it does not have any fixes implemented according to my issue.

  • [ ] My issue describes one of the unstable and/or not fully implemented features.

  • [ ] I have found a workaround to mitigate or temporarily fix this issue in affected releases (please write it in Additional context section below).

Operating System / Platform

🐧️ Linux

Operating system architecture

x64 (64-bit Intel/AMD)

Electron version

19.0.8

Application version

3.4.0

Bug description

I'm on gnome and notifications about new messages only appear to be like: image Message looks a bit different when i open any friend tab and it will show actually notification with that tab, and not the user from whom i got the message. This notification should have both talking user profile picture, name and his message instead, and no "is ready" sign.

As for no notifications - when i minimize (close the window) the app, it doesn't seem to give any desktop notifications at all. On regular discord it gives notifications just fine when minimized.

Additional context

I used Fedora Silverblue 36 linux distribution, under wayland, flatpak webcord (before i tried running it with wayland native, but it crashed so i did not test it further) Edit: I tried running wayland after i enabled wayland socket in flatseal, it worked, but there is no notifications at all.


Mod edit: Uncheck the checkbox that describes the state of occurance of this bug in Discord web version. See https://github.com/SpacingBat3/WebCord/issues/183#issuecomment-1188998742.

Meister1593 avatar Jul 16 '22 09:07 Meister1593

Try RPM, Flatpaks are maintained by the community and this could be an issue with Flatpak sandboxing.

SpacingBat3 avatar Jul 16 '22 22:07 SpacingBat3

Try RPM, Flatpaks are maintained by the community and this could be an issue with Flatpak sandboxing.

Both RPM and appimage versions have exactly the same behaviour, i don't believe this is a bug, this is more likely to be a feature yet to be implemented?

Meister1593 avatar Jul 18 '22 17:07 Meister1593

Both RPM and appimage versions have exactly the same behaviour, i don't believe this is a bug, this is more likely to be a feature yet to be implemented?

For me notifications works normally, but I'm on XFCE. But even if there would be something wrong with it, it is likely an Electron issue.

In reality, nothing is implemented about the notifications, they're directly handled by Chromium/Electron itself. And WebCord's Electron version is different from Discord and even if it would be equal Discord bases on its own Electron fork, so it could be fixed or implemented another way.

SpacingBat3 avatar Jul 18 '22 18:07 SpacingBat3

I got a friend tested Appimage version too, but this time on Fedora Kinoite 36 (plasma spin instead of gnome), and there was no notifications at all compared to regular discord. Plasma was both wayland and xorg, exactly the same behaviour. I'm gonna test Gnome xorg a bit later, but i expect that it will be pretty much the same as on wayland.

Meister1593 avatar Jul 18 '22 22:07 Meister1593

Actually, there is no notifications on web version at all as far as i am aware

There're. If they weren't, it wouldn't work on WebCord as well. And to display them you have to enable them in Discord settings (and give the notifications permission in WebCord's settings). I guess you should uncheck this until you test it on Chromium?

SpacingBat3 avatar Jul 19 '22 12:07 SpacingBat3

Since a lot has changed once this issue has been reported, I will close it for now. You can re-open it by reporting if the bug still occurs on the latest WebCord release.

SpacingBat3 avatar Aug 14 '22 14:08 SpacingBat3