Bug 388086

Summary:	showPassiveNotification() should be able to have a close button
Product:	[Frameworks and Libraries] frameworks-kirigami	Reporter:	Nate Graham <nate>
Component:	general	Assignee:	Marco Martin <notmart>
Status:	RESOLVED NOT A BUG
Severity:	wishlist	CC:	bugseforuns
Priority:	NOR
Version:	5.41.0
Target Milestone:	Not decided
Platform:	Other
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=403792 https://bugs.kde.org/show_bug.cgi?id=403791
Latest Commit:		Version Fixed In:

Description Nate Graham 2017-12-20 18:23:10 UTC

Kirigami's showPassiveNotification should have an easy facility to add a close button to the notification.

Right now, there is no easy way to do this, which is problematic for the following use cases:
- Short text with a long timer; the message annoyingly sticks around far after the user has finished reading it
- Long text with any length timer: the message disappears before the user has finished reading it

If these notifications could be given a close button, then developers could use a very long timeout, confident that the user could dismiss the message at their leisure once they've finished reading it. Right now they can't easily do that, so the message always sticks around for too long, or disappears too early.

Comment 1 Nate Graham 2017-12-20 18:27:59 UTC

It's true that you can click or touch the notification to dismiss it, but that's not obvious, and there's no reason you'd even try to do that on the desktop (in Desktop UIs, generally things don't disappear when you click on them). I didn't find out that this was possible until I started reading Kirigami's source code.

Comment 2 Nate Graham 2019-05-02 22:21:57 UTC

Nah. The real problem is that Discover is misusing these to display important information and should use actual dialogs and inlineMessages instead. See Bug 403791.