Should fade popup when (text-)cursor is within bounding box

[Paul Sladen]

Binary package hint: notify-osd

With a default Firefox configuration, the highly useful search box is in the top-right hand corner. If a notification comes in whilst typing in the search box it impossible to see what is being typed.

IIRC, there is currently code to dull/fade a notification if the mouse cursor is moved into the bounding box of the notification popup; ideally this behaviour should be extended to the active text cursor in the focused window.

(FWIW, this is the first time that libnotify has frustrated me!).

[Mirco Müller (macslow)]

This is a very hard to solve problem. The currently implemented "fixed slot allocation" scheme eases this a little bit, since the more frequent async. notifications (e.g. im-message), are placed in the lower of the two "slots" reserved for notifications. Thus if your browser is maximized the search-entry-widget is not covered by the notification-bubble.

[frankster (wtfrank)]

My mouse doesn't like to stay still on my screen (cos the cord pushes it around), so I can't move the cursor to the search box to remove the notification as the notification keeps coming back until it times out, so I have to wait 10 seconds until I can type into the search box. seriously, seriously frustrating. Particularly when there are lots of notifications coming in (e.g. tweets from gwibeer).

The effect is that this part of the screen is unusable for any keyboard controls or feedback. It would almost be better if the notification was there permanently - at least applications could resize themselves around it.

There is a desperate need for a proper way of cancelling the notification via keyboard; an X button on the notification is pretty much ruled out because of the "disappear on mouse movement" functionality (which is a good thing on balance I think, it just opens up this issue which needs a solution).