Comment 195 for bug 390508

Revision history for this message
quequotion (quequotion) wrote :

>Fewer notifications is a lose term. I can easily abuse the current functionality and keep triggering notifications. I just can't have them disappear as quickly as I might like, ie it doesn't respect the timeout.

Indeed. Canonical's policy does nothing to affect the number of possible notifications.

This "feature" serves only to limit the functionality and convenience of notifications.

How clearly do I have to say this?

There is nothing good about ignoring the timeout parameter.

There is no logical reason to ignore the timeout parameter.

If we are going to use notifications at all they must acknowledge the timeout parameter.