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.Notifications.Notify.

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_.

-- 
notify-send ignores the expire timeout parameter
https://bugs.launchpad.net/bugs/390508
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to