-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Select applications are not moving to their last known zone when creating new windows. #4684
Comments
@francoiswnel |
@enricogior Ah okay. And this design change was implemented between 0.18.0 and 0.19.0? Because my expected behaviour is definitely still the case on 0.18.0 since I'm running that in another environment. I'm fairly certain that the very first Firefox window does not move to its zone though, but perhaps there is already a background process running upon startup. To add my two cents, I think the previous behaviour is still the better compromise and more consistent with expectations. Yes, it's not ideal for a dialog to snap to the top right of the zone, but at least it's still confined to the same zone, i.e. the same expected workspace, and not just left to decide where it wants to appear on its own. Maybe windows that cannot be resized (like dialogs) should be centred within their parent zone. Thoughts? |
I cannot reproduce the problem, for me the first FF window is zoned as expected.
Unfortunately the previous behavior was causing bugs like these: |
@enricogior Thanks for the info. Okay, happy to close this issue then. |
Closing this has |
Environment
Steps to reproduce
Open a new Explorer window with Win+E, or launch a new instance of Firefox, or open a new Firefox window from within Firefox with Ctrl+N.
Expected behavior
The newly created window should move and snap to its last known zone.
Actual behavior
The newly created window does not move or snap to any zones.
Additional Info
Not all applications are affected. The PowerToys settings window still snaps to the last known zone, for example. So does Steam, Device Manager, etc. I can only confirm it with Explorer and Firefox so far. This behaviour started after I upgraded to both Windows 10 2004 and PowerToys 0.19.0 in the same evening, so it could be attributed to either. I can confirm that the expected behaviour is still valid on Windows 10 1909 with PowerToys 0.18.0.
The text was updated successfully, but these errors were encountered: