Broken Display when docked #21306

Closed
opened 2026-01-31 07:39:23 +00:00 by claunia · 9 comments
Owner

Originally created by @IPdotSetAF on GitHub (Feb 24, 2024).

Windows Terminal version

1.18.231114001

Windows build number

19045.4046

Other Software

npm -> nodeJS v18

Steps to reproduce

  • clone any nodeJS based repo
  • inside the inside the folder run command npm install
  • dock the terminal window to right or left side of the screen
  • npm can not clear the last line and rewrite it anymore (it can only append lines).

Expected Behavior

last line should be deleted and rewritten.

Actual Behavior

when terminal is docked, lines can not be cleaned, lines will only append.

Originally created by @IPdotSetAF on GitHub (Feb 24, 2024). ### Windows Terminal version 1.18.231114001 ### Windows build number 19045.4046 ### Other Software npm -> nodeJS v18 ### Steps to reproduce - clone any nodeJS based repo - inside the inside the folder run command `npm install` - dock the terminal window to right or left side of the screen - npm can not clear the last line and rewrite it anymore (it can only append lines). ### Expected Behavior last line should be deleted and rewritten. ### Actual Behavior when terminal is docked, lines can not be cleaned, lines will only append.
Author
Owner

@zadjii-msft commented on GitHub (Feb 27, 2024):

npm can not clear the last line and rewrite it anymore (it can only append lines).

That sounds like gutter turds are back? I've got a couple questions to help ID the root cause here:

  • Can you select the text in that last row, or is it not actually selectable?
  • Was there text in that row before you docked the Terminal? Or was it blank?
  • Can you share a screenshot/?

Also, can you try Windows Terminal v1.19.10302.0? Sharing your settings might also help here, to know which renderer is in use.

@zadjii-msft commented on GitHub (Feb 27, 2024): > npm can not clear the last line and rewrite it anymore (it can only append lines). That _sounds_ like gutter turds are back? I've got a couple questions to help ID the root cause here: * Can you select the text in that last row, or is it not actually selectable? * Was there text in that row before you docked the Terminal? Or was it blank? * Can you share a screenshot/? Also, can you try [Windows Terminal v1.19.10302.0](https://github.com/microsoft/terminal/releases/tag/v1.19.10302.0)? Sharing your settings might also help here, to know which renderer is in use.
Author
Owner

@IPdotSetAF commented on GitHub (Feb 27, 2024):

Thanks for the reply @zadjii-msft

  • Can you select the text in that last row, or is it not actually selectable?

yes the text is selectable (when its working as it should (terminal is not docked))

  • Can you share a screenshot/?
  • Not Docked :
    Screenshot 2024-02-27 161839

  • Docked :
    Screenshot 2024-02-27 161902

  • Was there text in that row before you docked the Terminal? Or was it blank?

I don't remember that, unfortunately.

which renderer is in use.

I am using the default renderer (NOT AtlasEngine)

@IPdotSetAF commented on GitHub (Feb 27, 2024): Thanks for the reply @zadjii-msft > * Can you select the text in that last row, or is it not actually selectable? yes the text is selectable (when its working as it should (terminal is not docked)) > * Can you share a screenshot/? - Not Docked : ![Screenshot 2024-02-27 161839](https://github.com/microsoft/terminal/assets/60518834/c9d66bb2-86e2-4047-af51-d2fc4ce4c42d) - Docked : ![Screenshot 2024-02-27 161902](https://github.com/microsoft/terminal/assets/60518834/11248cfc-e7ca-4edf-96cb-ec0a06024a94) > * Was there text in that row before you docked the Terminal? Or was it blank? I don't remember that, unfortunately. > which renderer is in use. I am using the default renderer (NOT AtlasEngine)
Author
Owner

@lhecker commented on GitHub (Feb 27, 2024):

So, what happens if you do use AtlasEngine?

@lhecker commented on GitHub (Feb 27, 2024): So, what happens if you do use AtlasEngine?
Author
Owner

@IPdotSetAF commented on GitHub (Feb 28, 2024):

So, what happens if you do use AtlasEngine?

same bug.

@IPdotSetAF commented on GitHub (Feb 28, 2024): > So, what happens if you do use AtlasEngine? same bug.
Author
Owner

@carlos-zamora commented on GitHub (Feb 28, 2024):

Thanks for testing that out. Got a few more questions for you:

  • What if instead of docking, you resize the window?
  • What if you dock the window first before running it?
  • Does this repro in console host (conhost.exe)?
@carlos-zamora commented on GitHub (Feb 28, 2024): Thanks for testing that out. Got a few more questions for you: - What if instead of docking, you resize the window? - What if you dock the window first before running it? - Does this repro in console host (conhost.exe)?
Author
Owner

@IPdotSetAF commented on GitHub (Feb 29, 2024):

  • What if instead of docking, you resize the window?

That works fine.

  • What if you dock the window first before running it?

This also works fine

  • Does this repro in console host (conhost.exe)?

IDK, I will try this out and let you know.

@IPdotSetAF commented on GitHub (Feb 29, 2024): > * What if instead of docking, you resize the window? That works fine. > * What if you dock the window first before running it? This also works fine > * Does this repro in console host (conhost.exe)? IDK, I will try this out and let you know.
Author
Owner

@IPdotSetAF commented on GitHub (Mar 5, 2024):

  • Does this repro in console host (conhost.exe)?

No, it does not.

@IPdotSetAF commented on GitHub (Mar 5, 2024): > * Does this repro in console host (conhost.exe)? No, it does not.
Author
Owner

@carlos-zamora commented on GitHub (Mar 6, 2024):

Thanks for your help. We're actually going to mark this as a /dup of #15976 so that we can track this all in one issue.

@carlos-zamora commented on GitHub (Mar 6, 2024): Thanks for your help. We're actually going to mark this as a /dup of #15976 so that we can track this all in one issue.
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Mar 6, 2024):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Mar 6, 2024): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21306