Comment 14 for bug 436975

First of all, Mirco is doing a great job on this. I closely followed the development of notify-osd and I must say that the idea of this kind of notifications is awesome. Also the notify-osd implementation is super cool too.

But I have to agree with Edder Rojas, Adrian Glaubitz and Paul Leger. Leaving that gap there looks as if there is something wrong with the notification system. As there would be a notification that is invisible and without a timeout. Confusing, none the least.

I can see where this idea is originated from, I guess. The decision was taken because if you want to display synchronous notifications among other (possible) notifications, you need to be able to track them. So, reserving a gap for this seemed like a good idea. But it isn't, in my -- and apparently other people's -- opinion.

I would suggest as a possible solution that notification bubbles should always respect the gravity setting (without the reserved gap) AND if a synchronous notification bubble appears, the other already displayed bubbles slide down and create that reserved space when necessary so the synchronous notifications can appear at the top (if gravity is set to NE).