Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Provide drag-space options for maximized windows

more options

When Firefox isn't maximized, the top left corner has a drag space dedicated to dragging the window. It is also possible to optionally configure additional drag space on the top of the window. However, both of these areas disappear on maximized windows.

Currently, to move a maximized window onto another screen, one has to "restore" the window and then drag the window. That's one step too many since there's no reason why one shouldn't be able to just drag a maximized window and have it automatically detach and attach to the next window as is possible with other software. Firefox just needs the option to individually allow the separate drag spaces to be configured to be visible for maximized windows to allow this.

Suggestion: both of the drag spaces, i.e., the top drag space and the top left corner drag space, should have a setting each for both non-maximized windows and maximized windows in order to provide the ultimate in user preference configurability.

When Firefox isn't maximized, the top left corner has a drag space dedicated to dragging the window. It is also possible to optionally configure additional drag space on the top of the window. However, both of these areas disappear on maximized windows. Currently, to move a maximized window onto another screen, one has to "restore" the window and then drag the window. That's one step too many since there's no reason why one shouldn't be able to just drag a maximized window and have it automatically detach and attach to the next window as is possible with other software. Firefox just needs the option to individually allow the separate drag spaces to be configured to be visible for maximized windows to allow this. Suggestion: both of the drag spaces, i.e., the top drag space and the top left corner drag space, should have a setting each for both non-maximized windows and maximized windows in order to provide the ultimate in user preference configurability.

All Replies (6)

more options

Hi,

The people who answer questions here, for the most part, are other Firefox users volunteering their time (like me), not Mozilla employees or Firefox developers.

If you want to leave feedback for Firefox developers, you can go to the Firefox Help menu and select Submit Feedback... or use this link. Your feedback gets collected by a team of people who read it and gather data about the most common issues.


I believe the reasoning behind the design is because users don't normally need to drag a maximized window, but it's common for them to drag a resized window.

Modified by Wesley Branton

more options

Thank you. Feedback now submitted.


A great design should never assume how users operate but provide the flexibility for the design to mold itself to its users. In fact, the assumption that users don't normally need to drag a maximized window stems from single-monitor system; on multi-monitor systems, this is, however, a much more common operation.

more options

Can you drag using the usually empty area just to the left of the minimize button?

The various blank areas are shown/hidden using style rules, so you probably can keep a blank area displayed all the time with some custom CSS in a userChrome.css file.

more options

I don't have a blank area there because of how my system is configured. However, the thing is, the top left area should not jump around the place depending on what state the window is in but remain in one place. If it shifts around, then the user has to always be on their toes and it breaks their focus. Good user interface design keeps things consistent and predictable.

I may be able to modify the CSS but this is a really a feature that should be part of the core of Firefox and not have to be hacked.

more options

Okay, if you just wanted to make a suggestion and not get workarounds, then never mind.

more options

I appreciate the time you've taken to suggest a workaround but I really think the core of the issue needs to be resolved which is why I raised the feedback as per Wesley's suggestion above.