Comment 128 for bug 390508
Revision history for this message
| stenzn (stenzn) wrote Re: notify-send ignores the expire timeout parameter | #128 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
The first sentence of the design spec for notify-osd clearly says it should implement the Desktop Notifications Specification.
The first line of the Desktop Notifications Specification says, "The following messages MUST be supported by all implementations." There is no ambiguity.
notify-osd does not use the expire_timeout parameter of org.freedesktop
expire_timeout INT32
...
<<< If -1, the notification's expiration time is dependent on the notification server's settings, >>> and may vary for the type of notification. If 0, never expire.
notify-osd always acts as though expire_timeout is -1. Nothing in the spec says "feel free to ignore this in your implementation", or "developers beware- implementations are free to ignore this and still be called compliant (i.e. don't expect this to actually work)".
Clearly, this is a bug (that it's by choice is irrelevant).
Apps written to be fully compliant with the Desktop Notifications Specification using the expire_timeout parameter have notifications that do not work correctly on Ubuntu. That is _unacceptable_.