Comment 13 for bug 1295762

>> It's unlikely that developers have a problem understanding that the
>> timeout only applies to a specific kind of notification.
> Being explicit rather than implicit avoids misunderstanding and
> possible "false-positive" bug-reports due to that.

I agree with that sentiment, but think it's the wrong trade-off with
regards to simplicity. We already have precedence for snap decisions
behaving differently when using the standard API (for example, snap
decisions must have at least one action and they're the only
notification type that can be cancelled). Did we see many bug reports
from confused developers for that?

>> Adding additional hints only increases the complexity of the API and
>> makes it harder to switch between different kinds of notifications.
> By design every introduced notification-type serves a very
> specific purpose, that differs in behaviour, visuals and interaction.
> Thus switching between different notification-types is not a common
> thing to do for a developer, unless UX-requirements change later on.

UX requirements change all the time. Also, just because it's not common
doesn't mean we need to make it difficult.

I'll stop arguing about this though if you feel strongly about it. I
don't think we'll be using this API for much longer anyway.