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

Bug Report Scrollbar not updating while holding enter in powershell #1287

New Issue
Closed
opened 2026-01-30 22:21:11 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 22:21:11 +00:00
Owner
Copy Link

Originally created by @Summon528 on GitHub (May 23, 2019).

Environment

Windows build number: Microsoft Windows [Version 10.0.18898.1000]
Windows Terminal version (if applicable): 3f95d588051723

Any other software?

Steps to reproduce

  1. Open PowerShell in terminal (It works normally in cmd and wsl)
  2. Hold down enter

Expected behavior

Scrollbar should be scrollable after content passed the screen

Actual behavior

Scrollbar is still disabled

Demo video (see the scrollbar only update after the ls command)

Imgur

Originally created by @Summon528 on GitHub (May 23, 2019). <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18898.1000] Windows Terminal version (if applicable): 3f95d588051723 Any other software? ``` # Steps to reproduce 1. Open PowerShell in terminal (It works normally in `cmd` and `wsl`) 2. Hold down <kbd>enter</kbd> <!-- A description of how to trigger this bug. --> # Expected behavior Scrollbar should be scrollable after content passed the screen <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior Scrollbar is still disabled <!-- What's actually happening? --> #### Demo video (see the scrollbar only update after the `ls` command) ![Imgur](https://i.imgur.com/yJDxMoa.gif)
claunia commented 2026-01-30 22:21:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 23, 2019):

Oh hell, this is PSReadline doing something terrible with conpty. Not sure what quite yet, but the same behavior can be repoduced in conhost by running wsl, then powershell.exe. At this point, powershell.exe will be running in a conpty. The problem also goes away if you Remove-Module PSReadline.

My bet is that they're trying to detect the size of the console buffer, and if they're at the bottom, they're scrolling the buffer content upwards (either with the API or VT) instead of just emitting a newline. Since the buffer in conpty is only the size of the viewport, this happens immediately.

@lzybkr or @SteveL-MSFT for commentary.

I could've swore there was an issue for this already, but my memory escapes me

@zadjii-msft commented on GitHub (May 23, 2019): Oh hell, this is PSReadline doing something terrible with conpty. Not sure what quite yet, but the same behavior can be repoduced in conhost by running wsl, then powershell.exe. At this point, powershell.exe will be running in a conpty. The problem also goes away if you `Remove-Module PSReadline`. My bet is that they're trying to detect the size of the console buffer, and if they're at the bottom, they're scrolling the buffer content upwards (either with the API or VT) instead of just emitting a newline. Since the buffer in conpty is only the size of the viewport, this happens immediately. @lzybkr or @SteveL-MSFT for commentary. I could've swore there was an issue for this already, but my memory escapes me
claunia commented 2026-01-30 22:21:12 +00:00
Author
Owner
Copy Link

@lzybkr commented on GitHub (May 23, 2019):

Try PSReadLine 2.0.0-beta4. I recall this being fixed, and if I understand the repro correctly, I'm not reproducing the problem myself.

@lzybkr commented on GitHub (May 23, 2019): Try [PSReadLine 2.0.0-beta4](https://www.powershellgallery.com/packages/PSReadLine/2.0.0-beta4). I recall this being fixed, and if I understand the repro correctly, I'm not reproducing the problem myself.
claunia commented 2026-01-30 22:21:13 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 23, 2019):

Yeah, this was probably lzybkr/PSReadline#724.

@DHowett-MSFT commented on GitHub (May 23, 2019): Yeah, this was probably lzybkr/PSReadline#724.
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 Area-Output Issue-Bug Product-Conpty Product-Powershell Resolution-External
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#1287
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?