Skip to content
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

Docking/window position should be preserved when closing and opening Terminal #1420

Closed
UweKeim opened this issue Jun 22, 2019 · 2 comments
Closed
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@UweKeim
Copy link

UweKeim commented Jun 22, 2019

Steps to reproduce:

  1. Start Terminal.
  2. Press Win+Left key to dock Terminal window to the left half of my monitor. The Terminal window starts at (0|0) left top position.
  3. Exit Terminal.
  4. Start Terminal.

Actual results:

After step 4, the Terminal window starts at some probably random (X|Y) position.

Now I have to repeat above step 2:

  1. Press Win+Left key to dock the Terminal window to the left half of my monitor.

This is really annoying.

Expected results:

The Terminal window should start pixel perfect at the very same position where I closed it the last time. No offset or anything. Just start with the same size and the same position. No matter whether I manually resized the window or whether being docked before.

Google Chrome does this very well, Microsoft Edge based on Chromium does this very well, too, same does e.g. Visual Studio Code. I hope Terminal can do better, too.

Additional information:

I've described a similar issue some years back over at Super User, together with some UI mockups.

@UweKeim UweKeim added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 22, 2019
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 22, 2019
@DHowett-MSFT
Copy link
Contributor

Duplicate of #1387, #1043

@DHowett-MSFT
Copy link
Contributor

Also, just pitching in: I disagree. I might open multiple windows and I absolutely don’t want them all spawning over top of each other.

@DHowett-MSFT DHowett-MSFT added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Jun 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants