use all empty area to drag open indicator

[Omer Akram]

Trying to use Ubuntu touch on my phone, I often try to close an open indicator (e.g. sound menu) but the target is mostly missed. My suggestion is that all the area of an indicator that is not occupied by any of the component should be sensible to drag.

[Vesa Rautiainen (vesar)]

I don't fully understand this error description. When any indicator menu is open the only way to close it is to drag from the bottom handle upwards. The whole handle area is currently sensible to touch and menu can be closed from any area. I don't see how otherwise it could be. So setting to invalid.

[Omer Akram (om26er)]

I understand the description might not have been clear enough. Let me explain again.

When an indicator is opened you have to drag up with a handle to close it but that handle is at the bottom of the screen and in my real world usage I have found myself not being able to close the indicator if I am not concentrating too much on the phone. In Android 4.2 the part of the indicator that is not occupied by any of the widgets in their notification menu is drag-able to the upside to close the menu so that if you are not able to fully aim for the the drag handle of the opened menu, it will still close.

[Michał Sawicz (saviq)]

This could be reiterated upon.

[Vesa Rautiainen (vesar)]

Thanks for the clarification Omer! Whilst I see the benefit of using unoccupied menu area space for close swiping I don't think this is extremely critical.

Then there are technical challenges included. The indicators container is owned by the shell and it gives the menu space for plugins to render themselves. So shell doesn't really know how far down each plugin is occupied. Also event though menu plugin doesn't have enough content (e.g. listview with just few items) to occupy the whole menu space (leaving some space at the bottom) it might be that it still want draw the whole listview from top to bottom in case there will be more items in the future. I could image for example Incoming menu acting like that.

So I think this all is a good idea and might be a usability improvement I would give this quite low priority at this point.