GNOME Bugzilla – Bug 729714
a11y: make notifications persistent
Last modified: 2014-07-18 13:53:07 UTC
I just wasted an hour trying to debug a 'broken' keyboard that turned out to be just slow keys turned on by accident. We show a notification that asks me to make a decision, but it is not expanded initially, and disappears without a trace after a few seconds. After that, the only hint is that the a11y menu appeared in the shell, and that is really not obvious enough - Ray and I didn't notice it even though we went in there to turn on the osk.
Created attachment 276093 [details] [review] a11y-keyboard: Make sticky and slow keys notifications critical Since these features change the way the keyboard behaves we shouldn't timeout the notifications automatically and leave users confused, thinking their keyboard is broken, in case they activate them unknowingly and miss the notification. We use the critical urgency level to achieve this since it makes gnome-shell automatically expand the notification, allowing users to act on the actions immediately, and it also means that the notification won't disappear until it's explicitly acknowledged. -- I assume we don't really want persistent notifications as in the "resident" hint spec definition since that would mean that the notification never disappears even after the user clicks on it or one of its buttons. Urgency critical seems to have sane semantics in gnome-shell for this.
Thanks rui, that looks like a great improvement.
Review of attachment 276093 [details] [review]: Sure.
Attachment 276093 [details] pushed as 4dd073d - a11y-keyboard: Make sticky and slow keys notifications critical