Unfortunately, notification-daemon returns a "default" action when the bubble is clicked, regardless of whether the application has registered it, and I'm told that some applications rely on this behavior. This means that Notify OSD's fallback alerts have to provide a way of triggering the "default" action, as well as a way of closing the alert without action. That is, they need to provide both an "OK" button and a "Cancel" button, even though these buttons will often do the same thing. I've updated the spec to mention this. <https://wiki.ubuntu.com/NotifyOSD?action=diff&rev2=119&rev1=118>
-- If bubble is replaced by alert window (infinite timeout, actions), window has unneeded OK/Cancel https://bugs.launchpad.net/bugs/343904 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
