Created attachment 190377 [details]
Evolution notification with "Default" action

Here is what the notification spec says about an action with the key "default":

"The default action (usually invoked by clicking the notification) should have a key named "default". The name can be anything, though implementations are free not to display it."

Currently, we treat an action called "default" as we treat any other action -
we add an action button for it and don't use it to inform us on what to do when the notification is clicked. For example, this happens for Evolution mail notifications, for which we display an action button that says "Default", which looks pretty silly.

We should either

a) Use the "default" action to inform us on what should happen when a notification is clicked and not display it. The concern there is that we'd like clicking the notification to switch to the application that sent it, and using the "default" action might introduce an inconsistency.

b) Remove the provision for the "default" action from the spec and ask applications that use this action to remove it or be sure to use a meaningful string for it (something other than "Default").