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

[PR #15262] [MERGED] Fix Present1 params when scrolling the entire viewport #30549

New Issue
Open
opened 2026-01-31 09:41:30 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:41:30 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/microsoft/terminal/pull/15262
Author: @lhecker
Created: 4/28/2023
Status: ✅ Merged
Merged: 5/8/2023
Merged by: @lhecker

Base: main ← Head: dev/lhecker/atlas-engine-fixup

📝 Commits (4)

  • abe47eb Fix Present1 params when scrolling the entire viewport
  • 07915b5 Use feature flagging
  • fb4c66a Merge remote-tracking branch 'origin/main' into dev/lhecker/atlas-engine-fixup
  • 52d6966 Forgot to write back to _api.scrollOffset

📊 Changes

4 files changed (+131 additions, -115 deletions)

View changed files

📝 src/features.xml (+10 -0)
📝 src/renderer/atlas/AtlasEngine.cpp (+108 -113)
📝 src/renderer/atlas/AtlasEngine.r.cpp (+12 -1)
📝 src/renderer/atlas/common.h (+1 -1)

📄 Description

This commit makes a few changes to avoid bugs, but they basically boil
down to: When we scroll by an entire viewport worth of content, we must
ensure that the scroll offset is 0, because otherwise the scroll rect
(that's basically the viewport, but excluding the scroll offset) will
end up being empty, which the Present1 API chokes on. This commit
avoids this situation by shuffling around some code to first calculate
the dirty rows, then check if it affects all of them and in that case
sets the scroll offset to 0, and only then finally actually does any
scrolling if there's still something to scroll.

Validation Steps Performed

  • Start pwsh
  • Zoom in twice with Ctrl+Scrollwheel
  • Print a few viewports worth of text
  • Press Ctrl+L
  • No errors ✅

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/microsoft/terminal/pull/15262 **Author:** [@lhecker](https://github.com/lhecker) **Created:** 4/28/2023 **Status:** ✅ Merged **Merged:** 5/8/2023 **Merged by:** [@lhecker](https://github.com/lhecker) **Base:** `main` ← **Head:** `dev/lhecker/atlas-engine-fixup` --- ### 📝 Commits (4) - [`abe47eb`](https://github.com/microsoft/terminal/commit/abe47eb7ed892776b2760eb0c45d7294674a580d) Fix Present1 params when scrolling the entire viewport - [`07915b5`](https://github.com/microsoft/terminal/commit/07915b5184935861d83ae3eefbca34994390c3ae) Use feature flagging - [`fb4c66a`](https://github.com/microsoft/terminal/commit/fb4c66ab01ecb333e67bde70ef748e3e6303d26f) Merge remote-tracking branch 'origin/main' into dev/lhecker/atlas-engine-fixup - [`52d6966`](https://github.com/microsoft/terminal/commit/52d6966b482549e5af78380bf89ca7d093a8c5ec) Forgot to write back to _api.scrollOffset ### 📊 Changes **4 files changed** (+131 additions, -115 deletions) <details> <summary>View changed files</summary> 📝 `src/features.xml` (+10 -0) 📝 `src/renderer/atlas/AtlasEngine.cpp` (+108 -113) 📝 `src/renderer/atlas/AtlasEngine.r.cpp` (+12 -1) 📝 `src/renderer/atlas/common.h` (+1 -1) </details> ### 📄 Description This commit makes a few changes to avoid bugs, but they basically boil down to: When we scroll by an entire viewport worth of content, we must ensure that the scroll offset is 0, because otherwise the scroll rect (that's basically the viewport, but excluding the scroll offset) will end up being empty, which the `Present1` API chokes on. This commit avoids this situation by shuffling around some code to first calculate the dirty rows, _then_ check if it affects all of them and in that case sets the scroll offset to 0, and only then finally actually does any scrolling if there's still something to scroll. ## Validation Steps Performed * Start pwsh * Zoom in twice with Ctrl+Scrollwheel * Print a few viewports worth of text * Press Ctrl+L * No errors ✅ --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-31 09:41:30 +00:00
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 pull-request
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#30549
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?