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

Text antialiasing doesn't work properly when moving between monitors of different scale #20373

New Issue
Open
opened 2026-01-31 07:11:51 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 07:11:51 +00:00
Owner
Copy Link

Originally created by @phealy on GitHub (Aug 15, 2023).

Windows Terminal version

1.18.1462.0

Windows build number

10.0.22621.2134

Other Software

This occurs with all software I tested (Powershell, cmd, WSL).

Steps to reproduce

  1. Have two monitors at different scale factors (I reproduced this with a 15" 2560x1440 monitor at 125% scale and a 27" 2560x1440 monitor at 100% scale).
  2. Have Terminal on one monitor (it is most easily seen if you start on the 125% monitor).
  3. Drag or use shift+win+right to move Terminal to the other monitor.
  4. Observe that the font is now blurry:
    • On the 125% monitor:
      image
    • After moving to the 100% monitor:
      image
    • Changing the size of the window (maximize, restore, drag a border in or out, whatever) fixes the rendering:
      image
    • Changing the font size via ctrl and +/- does not fix the antialiasing.

Expected Behavior

Font antialiasing maintains quality when moved to a new window.

Actual Behavior

Font antialiasing has reduced quality (font is blurry) until the window size is changed.

This appears like it might be related to #6210, but it's a different symptom - while the column count does change as in that issue, this is specifically about antialiasing.

Originally created by @phealy on GitHub (Aug 15, 2023). ### Windows Terminal version 1.18.1462.0 ### Windows build number 10.0.22621.2134 ### Other Software This occurs with all software I tested (Powershell, cmd, WSL). ### Steps to reproduce 1. Have two monitors at different scale factors (I reproduced this with a 15" 2560x1440 monitor at 125% scale and a 27" 2560x1440 monitor at 100% scale). 2. Have Terminal on one monitor (it is most easily seen if you start on the 125% monitor). 3. Drag or use shift+win+right to move Terminal to the other monitor. 4. Observe that the font is now blurry: - On the 125% monitor: ![image](https://github.com/microsoft/terminal/assets/3046014/e90668d7-c40b-46fd-807b-8bcb897bea0f) - After moving to the 100% monitor: ![image](https://github.com/microsoft/terminal/assets/3046014/e955a2a0-2690-4b53-81cc-425393c46226) - Changing the size of the window (maximize, restore, drag a border in or out, whatever) fixes the rendering: ![image](https://github.com/microsoft/terminal/assets/3046014/8747c631-56a2-41ac-94c4-7099bff47619) - Changing the font size via ctrl and +/- does *not* fix the antialiasing. ### Expected Behavior Font antialiasing maintains quality when moved to a new window. ### Actual Behavior Font antialiasing has reduced quality (font is blurry) until the window size is changed. This appears like it might be related to #6210, but it's a different symptom - while the column count does change as in that issue, this is specifically about antialiasing.
claunia added the Area-RenderingIssue-BugProduct-TerminalArea-TerminalControl labels 2026-01-31 07:11:51 +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 Area-Rendering Area-TerminalControl Issue-Bug Product-Terminal
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#20373
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?