You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is to track features to be implemented in the notification server.
"persistent" capability
Summary
"body" capability
CloseNotification method
NotificationClosed signal (NB. This is critical because it is required by the spec.)
"sound" capability (NB. Although we play sound, we need to support the "sound-file" and "suppress-sound" hints to be XDG compliant.)
ActionInvoked signal (NB. This partially ovelaps with the "actions" capability. This signal can however be used without the cap to invoke the notification itself (and not a specific action). XDG spec states this is optional.)
"actions" capability
"icon-static" capability
ActivationToken signal (NB. cutie-wlc needs to support xdg-activation-v1 for this.)
I personally believe the other capabilities defined by the spec are not desired in our use case. If you think otherwise, please leave a comment.
The text was updated successfully, but these errors were encountered:
This issue is to track features to be implemented in the notification server.
"persistent"
capability"body"
capabilityCloseNotification
methodNotificationClosed
signal (NB. This is critical because it is required by the spec.)"sound"
capability (NB. Although we play sound, we need to support the"sound-file"
and"suppress-sound"
hints to be XDG compliant.)ActionInvoked
signal (NB. This partially ovelaps with the"actions"
capability. This signal can however be used without the cap to invoke the notification itself (and not a specific action). XDG spec states this is optional.)"actions"
capability"icon-static"
capabilityActivationToken
signal (NB. cutie-wlc needs to support xdg-activation-v1 for this.)I personally believe the other capabilities defined by the spec are not desired in our use case. If you think otherwise, please leave a comment.
The text was updated successfully, but these errors were encountered: