No keybinding for near maximise without maximising completely

Bug #891659 reported by Jonathan Perkin on 2011-11-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ayatana Design

Bug Description

I don't like full-screen maximisation, especially as there are annoying interactions between the hidden dock and e.g. trying to click on the back button in a full-screened firefox (more often than not I will hit the side of the screen, triggering the dock to appear and covering the button I want to hit). Thus I tend to use windows which take up all of the screen except for the dock and the top bar.

I'd really really like an option to make this easy to do, preferably overriding the behaviour of double-click-in-titlebar/maximise button. At the moment I need to manually and very carefully position windows in this layout, and when re-opening an application which I have previously laid out in this manner, it is re-opened in full-screen maximisation - i.e. my position/size was not saved correctly, meaning I have to do it all over again.

Paul Sladen (sladen) wrote :

Thank you. I believe the core issue raised about is the lack of a keybinding option, or other method, for near-maximisation (resizing the height/width of the display, minus the space taken for the Launcher and Top bar).

There's several issues mentioned here (including whether applications should re-open in their previous spatial position), but perhaps those can be left for other bugs.

tags: added: poweruser

The core issue will be addressed by allowing the dock to be locked in
place, and some careful placement of back buttons and other sensitive
items, as well as reveal heuristics when the launcher is hidden.

In that light, I think it's fine to have a means to bind a key of the
users choice to the resizing of the window to take up all space except
the launcher and panel, but I don't think we want to assign a dedicated
key for that function, as it's certainly not common practice.


To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers