ferdium
Bug: Clicking on notification doesn't open relevant context in Ferdium
Avoid duplicates
- [X] I have searched the issues tracker for a bug report similar to mine, in vain
Ferdium Version
6.0.0-nightly.60
What Operating System are you using?
Windows
Operating System Version
Windows 10 Home 21H1
What arch are you using?
x64
Last Known Working Ferdium version
No response
Expected Behavior
Clicking on a notification should open the relevant context (service, channel, thread, etc... )
Actual Behavior
Ferdium opens to wherever (service, thread, etc...) you had open previously. It doesn't take you to where the notification came from.
Steps to reproduce
- with notifications turned on, trigger a slack or whatsapp message
- click on the windows notification
- the relevant ferdium will not open
Debug link
No response
Screenshots
No response
Additional information
No response
No change, clicking Ferdium notifications just opens Ferdium to wherever it was already open, not to the notification specifically.
Same behaviour in 6.2.4 Can anyone point me to the code that handles notifications in Macos or anything that could help debugging this? Thanks.
Sad to see this still isn't fixed. Manjaro Linux with xfce
Slack notification only sends you to the service, not the specific context that triggered the notification. Same goes for Discord
If using those apps in the browser, the notifications work as expected, sending you to exactly what triggered the notification.
I would have assumed that those same notifications should work identically in Ferdium since it's basically using the browser app versions of those services.
