STEPS TO REPRODUCE 1. Receive a message on Telegram or Element 2. Let the notification time out 3. Open history pop-up OBSERVED RESULT Buttons with weird, ugly, inappropriate names. See attached screenshots. EXPECTED RESULT Not that, I guess? The button should have a sane, user-comprehensible name. If this is impossible because the action name is a technical thing not intended to be shown to the user, then come up with a different label for the button.
Created attachment 179835 [details] Notification from Element
Created attachment 179836 [details] Notification from Telegram
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5353
That's interesting, Telegram looks very different for me (6.3.3 with my patch manually applied). Makes me wonder if there's something that landed in master that changed something wrt how actions are displayed? Gonna compile from master and have a look at what's going on
Created attachment 179837 [details] Telegram notification on 6.3.3 w/ manual patch
App-foo.bar sounds like a GTK action. Maybe it's a difference between GTK notifications, portal or whatever.
Telegram is Qt. I also notice the reply action is missing from Nate's screenshot, which is weird
Probably has to do with which Telegram versions you have installed, and where from
Yeah I've got 5.13 from Flatpak.
Git commit c8c4440522a264a02b831df4c14b5a2350e0d71b by Kai Uwe Broulik. Committed on 14/04/2025 at 08:24. Pushed by broulik into branch 'master'. Notifications: Ignore default action label for non-KDE apps Most apps don't seem to expect the default action be visible to the user even though the spec says not to make any assumptions. For KDE apps we can assume a user of KNotification (which uses the same action API as the user-facing butons) does something sensible. M +7 -1 libnotificationmanager/notification.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/c8c4440522a264a02b831df4c14b5a2350e0d71b