notify-sharp inappropriately swallows all notification actions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-sharp |
New
|
Unknown
|
|||
notify-sharp (Ubuntu) |
Fix Released
|
Low
|
Ken VanDine |
Bug Description
Binary package hint: giver
Giver is currently using notifications to present the recipient of a transfer with an option to accept or deny a file.
However, implementations like notify-osd do not let applications use notifications for such interactions, and instead encourage the use of better interaction mechanisms, like a dialog box or a morphing application window.
Note: this bug started as #347081. It was triggered by a change in notify-sharp that silently omits actions in a notification request if the remote server does not support the capability.
See https:/
Related branches
affects: | giver (Ubuntu) → notify-sharp (Ubuntu) |
summary: |
- giver should check the notification server capabilities + notify-sharp inappropriately swallows all notification actions |
Changed in notify-sharp: | |
assignee: | bratsche → ken-vandine |
Changed in notify-sharp: | |
status: | Unknown → New |
Cody, can you remove the check in notify-sharp? The library should really not make such decisions for the application.