Skip to content

notification-spec: Give notification daemons some more information regarding actions

Per notifictaion spec notification can have actions but we currently can't say whether

  1. the action should be available on the lock screen (prime example is e.g. the action to stop an alarm clock)
  2. the action would need the lock screen to unlock to be useful (e.g. if you have an application that notifies you that disk space is scarce and there's an "Explore" action that opens the application to look what uses up space you'd need unlock but for the above alarm example you wouldn't need unlock)
  3. whether the notification body or summary contains sensitive information so that it's content shouldn't be shown on the lock screen.

Having this would help mobile platforms as they usually have more lockscreen interaction than current desktop environments.

For 3. we could add an additional hint like sensitive. It seems android does something like that. The values public, secret and private look like a good start to me.

For 1. we could also use a hint lockscreen-actions = [true|false]. The default here could be based on sensitive. We'd then use another hint lockscreen-actions-unlock = [ action-prefix1, action-prefix2, ... ] for those that want unlock.

I'm happy to file an MR but wanted to sort out the initial direction first.