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

Resizing window too small breaks prompt line #3889

Closed
davidhewitt opened this issue Dec 9, 2019 · 2 comments
Closed

Resizing window too small breaks prompt line #3889

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

Comments

@davidhewitt
Copy link

Environment

Windows build number: 10.0.19033.0
Windows Terminal version (if applicable): master

Steps to reproduce

  1. Open a new windows terminal.
  2. Fill the screen with output from a command, so that there is at least some history off-screen.
  3. Resize the window horizontally to minimum width
  4. Resize the window back to the original width

Expected behavior

The text and prompt should all reflow so that after resizing back to original size, everything looks like it did before resizing down. After the resize back to full size, typing input should show on the prompt line.

(With one notable exception: the terminal will have scrolled up a bit.)

Actual behavior

The input cursor is no longer on the prompt line, but instead one line below. Typing input shows at the cursor location, but this is now nowhere close to the prompt line.

Screens attached below

Screen before resizing down:

image

Screen after resizing down (note cursor has now broken onto the line after the prompt):

image

Screen after resizing back to original size:

image

Screen after typing some input:

image

@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 Dec 9, 2019
@DHowett-MSFT
Copy link
Contributor

Thanks for the comprehensive report! This is a /dupe of #1465.

@ghost
Copy link

ghost commented Dec 9, 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 Dec 9, 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 Dec 9, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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