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

Request: Smooth+Pixel Precise Scrolling #11766

New Issue
Closed
opened 2026-01-31 02:56:47 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 02:56:47 +00:00
Owner
Copy Link

Originally created by @xiiok on GitHub (Dec 10, 2020).

Description of the new feature/enhancement

I would absolutely die and go to heaven if smooth and precise (i.e. animated and pixel-by-pixel) scrolling were implemented. One of the top reasons I started using Edge Chromium over Chrome was due to the slightly better smooth scrolling implementation.

Being able to easily read text while scrolling smoothly and precisely is a game... changer...! Especially, if you have a free scroll wheel like the MX Master 3 and/or a 120Hz+ monitor.

Proposed technical implementation details (optional)

Implementing something like this is outside of my wheelhouse, but I found some great information on the topic here: https://pavelfatin.com/scrolling-with-pleasure/

I understand that the pure intent of a terminal emulator is to display single lines as quickly and efficiently as possible. But from a UX perspective, smooth/precise scrolling feels sooo good with the right peripherals.

Let me know your thoughts please! 😁

Originally created by @xiiok on GitHub (Dec 10, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement I would absolutely die and go to heaven if smooth _and_ precise (i.e. animated and pixel-by-pixel) scrolling were implemented. One of the top reasons I started using Edge Chromium over Chrome was due to the slightly better smooth scrolling implementation. Being able to easily read text while scrolling smoothly and precisely is a game... changer...! Especially, if you have a free scroll wheel like the MX Master 3 and/or a 120Hz+ monitor. # Proposed technical implementation details (optional) Implementing something like this is outside of my wheelhouse, but I found some great information on the topic here: https://pavelfatin.com/scrolling-with-pleasure/ I understand that the pure intent of a terminal emulator is to display single lines as quickly and efficiently as possible. But from a UX perspective, smooth/precise scrolling feels sooo good with the right peripherals. Let me know your thoughts please! 😁
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 02:56:47 +00:00
claunia commented 2026-01-31 02:56:48 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Dec 10, 2020):

I think this is probably a duplicate of #1400 and #1980.

@j4james commented on GitHub (Dec 10, 2020): I think this is probably a duplicate of #1400 and #1980.
claunia commented 2026-01-31 02:56:48 +00:00
Author
Owner
Copy Link

@xiiok commented on GitHub (Dec 10, 2020):

It sure is a dupe. I searched and everything...sigh. My Google-Fu wasn't strong enough today.
Thanks for the tags; if this feature is considered I hope my description and linked resource may still come in handy to whomever. The guy knows his scrolling... he links a repo of related code examples too https://github.com/pavelfatin/scrolling-with-pleasure

Edit: Actually, now that I've read through the related issues, this isn't exactly a dupe. It looks like there's been really 3 different scrolling related discussions as @Livven mentioned in #1400 here

The original request in #1400 was to smoothly scroll lines in as they are output. I'm looking at scrolling up and down in the window to read lines that have already been printed. Like the high-precision scrolling in Edge and Chrome mentioned in #1980 which shouldn't necessarily have been marked as a dupe imo. Very similar features, though likely different enough in implementation?

Example: https://www.youtube.com/watch?v=6n31SO1HJAI

@xiiok commented on GitHub (Dec 10, 2020): ~It sure is a dupe. I searched and everything...sigh. My Google-Fu wasn't strong enough today.~ Thanks for the tags; if this feature is considered I hope my description and linked resource may still come in handy to whomever. The guy knows his scrolling... he links a repo of related code examples too https://github.com/pavelfatin/scrolling-with-pleasure Edit: Actually, now that I've read through the related issues, this isn't exactly a dupe. It looks like there's been really 3 different scrolling related discussions as @Livven mentioned in #1400 [here](https://github.com/microsoft/terminal/issues/1400#issuecomment-602264540) The original request in #1400 was to smoothly scroll lines in as they are output. I'm looking at scrolling up and down in the window to read lines that have already been printed. Like the high-precision scrolling in Edge and Chrome mentioned in #1980 which shouldn't necessarily have been marked as a dupe imo. Very similar features, though likely different enough in implementation? Example: https://www.youtube.com/watch?v=6n31SO1HJAI
claunia commented 2026-01-31 02:56:49 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Dec 10, 2020):

It's not my call to make, but personally I prefer related issues like these to be closed as dupes, so whoever takes on the feature will be aware of the various use cases that could affect the design. If it turns out that a PR is only going to address one part of the problem, we can always raise follow-up issues, or reopen the ones that had previously been closed as dupes.

@j4james commented on GitHub (Dec 10, 2020): It's not my call to make, but personally I prefer related issues like these to be closed as dupes, so whoever takes on the feature will be aware of the various use cases that could affect the design. If it turns out that a PR is only going to address one part of the problem, we can always raise follow-up issues, or reopen the ones that had previously been closed as dupes.
claunia commented 2026-01-31 02:56:49 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 11, 2020):

I'm inclined to call it a duplicate -- not exactly because we'll fix them both, but because they require the same underpinnings and we would be remiss in doing one of them but not the other.

Thanks for the discussion(, and the quick duplicate, James 😄)

/dup #1400

@DHowett commented on GitHub (Dec 11, 2020): I'm inclined to call it a duplicate -- not exactly because we'll fix them both, but because they require the same underpinnings and we would be remiss in doing one of them but not the other. Thanks for the discussion(, and the quick duplicate, James :smile:) /dup #1400
claunia commented 2026-01-31 02:56:49 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 11, 2020):

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 commented on GitHub (Dec 11, 2020): 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!
claunia commented 2026-01-31 02:56:49 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 11, 2020):

I copied your description to 1400!

@DHowett commented on GitHub (Dec 11, 2020): I copied your description to 1400!
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-Feature 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#11766
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?