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.

Sign up for GitHub

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

Jump to bottom

Terminal exits when window is dragged to other screen (with different DPI setting) #3355

Closed
mstevens83 opened this issue Oct 28, 2019 · 2 comments
Closed

Terminal exits when window is dragged to other screen (with different DPI setting) #3355

mstevens83 opened this issue Oct 28, 2019 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@mstevens83
Copy link

Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): 0.6.2951.0

Steps to reproduce

  • Start Windows Terminal
  • Drag window to other screen (which happens to run at a different DPI/scaling setting)
  • Terminal exits :-/

My first screen (on which Terminal initially opened) is set 150% scaling, the second one (on which Terminal dies) is at 100%.

Expected behavior

Terminal should continue working on other screen.

Actual behavior

After releasing the drag&drop operation the window briefly (~1s) seems to be usable, but then it just closes.
@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 Oct 28, 2019
@zadjii-msft
Copy link
Member

This sounds awfully similar to #3303 - I'm just going to mark this as a dupe. Thanks!

/dup #3303

@ghost
Copy link

ghost commented Oct 28, 2019

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Oct 28, 2019
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Oct 28, 2019
@zadjii-msft zadjii-msft mentioned this issue Nov 1, 2019
Closed
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mstevens83 @zadjii-msft