starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

When I scroll down or up the wheel, some lines will disappear #19859

New Issue
Closed
opened 2026-01-31 06:55:31 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 06:55:31 +00:00
Owner
Copy Link

Originally created by @Cricle on GitHub (May 11, 2023).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.16.10261.0

Windows build number

10.0.19045.0

Other Software

None

Steps to reproduce

  1. Run other program, generate many lines of content(Like benchmark)
  2. Scroll down or up the wheel(The disappearing row must be moved to an invisible area before it can be seen again)
  3. Some lines will disappear

image

Expected Behavior

Some lines will disappear

Actual Behavior

Nothing to do

Originally created by @Cricle on GitHub (May 11, 2023). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.16.10261.0 ### Windows build number 10.0.19045.0 ### Other Software None ### Steps to reproduce 1. Run other program, generate many lines of content(Like benchmark) 2. Scroll down or up the wheel(The disappearing row must be moved to an invisible area before it can be seen again) 3. Some lines will disappear ![image](https://github.com/microsoft/terminal/assets/26201412/b0985848-ec39-4918-bb2b-2813adcd5a1c) ### Expected Behavior Some lines will disappear ### Actual Behavior Nothing to do
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:55:31 +00:00
claunia commented 2026-01-31 06:55:32 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (May 16, 2023):

Reading https://github.com/nushell/nushell/issues/9166 it does seem a little unclear to me whether this is a bug in Windows Terminal, nushell or starship. I do know however that this is easily reproducible with starship because I had this issue myself before, but I simply assumed that this is a bug in starship.

Reading through the various, linked issues however, I think this might be due to #8698.

@lhecker commented on GitHub (May 16, 2023): Reading https://github.com/nushell/nushell/issues/9166 it does seem a little unclear to me whether this is a bug in Windows Terminal, nushell or starship. I do know however that this is easily reproducible with starship because I had this issue myself before, but I simply assumed that this is a bug in starship. Reading through the various, linked issues however, I think this might be due to #8698.
claunia commented 2026-01-31 06:55:32 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (May 18, 2023):

@lhecker If they're using an SU sequence to scroll (which is the impression I got from your comments on the nushell issue), then this is potentially a dup of #11078.

If the SU is triggered by a terminfo indn command, it's kind of our problem, because we're identifying as xterm-256color, which defines indn as an SU sequence (that's what #11078 is all about). But if they're invoking SU directly, then I'd say it's more their problem, because they're relying on an interpretation of SU which isn't standard.

@j4james commented on GitHub (May 18, 2023): @lhecker If they're using an `SU` sequence to scroll (which is the impression I got from your comments on the nushell issue), then this is potentially a dup of #11078. If the `SU` is triggered by a terminfo `indn` command, it's kind of our problem, because we're identifying as `xterm-256color`, which defines `indn` as an `SU` sequence (that's what #11078 is all about). But if they're invoking `SU` directly, then I'd say it's more their problem, because they're relying on an interpretation of `SU` which isn't standard.
claunia commented 2026-01-31 06:55:32 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (May 18, 2023):

Thank you for looking into this! As you probably already saw they’re invoking it directly. I personally agree with everything you said in #11078 btw - I feel like we should make that change irregardless of the ambiguity of the sequence and that it should best be avoided, if not at least because of indn.

@lhecker commented on GitHub (May 18, 2023): Thank you for looking into this! As you probably already saw they’re invoking it directly. I personally agree with everything you said in #11078 btw - I feel like we should make that change irregardless of the ambiguity of the sequence and that it should best be avoided, if not at least because of `indn`.
claunia commented 2026-01-31 06:55:33 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 18, 2023):

That lines up with the theory we were discussing in triage yesterday. I'll tentatively call this a dupe, with the note that Leonard did have a live repro of this, so it should be fairly easy to validate if the fix for #11078 fixes this.

/dup #11078

@zadjii-msft commented on GitHub (May 18, 2023): That lines up with the theory we were discussing in triage yesterday. I'll tentatively call this a dupe, with the note that Leonard did have a live repro of this, so it should be fairly easy to validate if the fix for #11078 fixes this. /dup #11078
claunia commented 2026-01-31 06:55:33 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (May 18, 2023):

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 (May 18, 2023): 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!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#19859
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?