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

Broken rendering/editing/caret experience with emoji sequences #15960

New Issue
Open
opened 2026-01-31 04:53:27 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:53:27 +00:00
Owner
Copy Link

Originally created by @andrew-z on GitHub (Nov 25, 2021).

Windows Terminal version

1.11.2921.0

Windows build number

10.0.22000.0 (actual patch: 22000.348, corresponds to 11C)

Other Software

No response

Steps to reproduce

Open Terminal and type certain emoji sequences.

I didn't do full testing, but this happens especially prominently with emoji 13.0 and 13.1. Examples: transgender flag 🏳️‍⚧️, black cat 🐈‍⬛, polar bear 🐻‍❄️, mending heart ❤️‍🩹 (needs Win11 11C to render correctly). Some older sequences are broken as well, e.g. some variants of family emoji 👨‍👩‍👧. All of these are ZWJ sequences (can contain multiple ZWJs).

Expected Behavior

Emoji sequence is rendered as a single glyph with no invisible characters in the run. Backspace, caret movement and selection treat this glyph as an indivisible entity.

Actual Behavior

From what I observe, it seems that there's an issue (or multiple issues) with many emoji sequences rendering and editing experience:

  • Emoji itself is rendered correctly, but is surrounded with multiple invisible characters (perhaps incorrectly calculated due to multiple codepoints in the cluster). I see that Terminal uses DirectWrite for itemizing the string, so perhaps it's not using the APIs correctly leading to a mismatch between displayed glyph and length of the run reserved for its rendering. DirectWrite (including text shaping engine) itself is updated already to handle emoji up to 13.1 correctly.
  • Caret is moving between invisible characters. Backspace is deleting invisible characters, affecting the rendering.
  • Selection will pick up individual constituents of the sequence (which are not rendered)
Originally created by @andrew-z on GitHub (Nov 25, 2021). ### Windows Terminal version 1.11.2921.0 ### Windows build number 10.0.22000.0 (actual patch: 22000.348, corresponds to 11C) ### Other Software _No response_ ### Steps to reproduce Open Terminal and type certain emoji sequences. I didn't do full testing, but this happens especially prominently with emoji 13.0 and 13.1. Examples: transgender flag 🏳️‍⚧️, black cat 🐈‍⬛, polar bear 🐻‍❄️, mending heart ❤️‍🩹 (needs Win11 11C to render correctly). Some older sequences are broken as well, e.g. some variants of family emoji 👨‍👩‍👧. All of these are ZWJ sequences (can contain multiple ZWJs). ### Expected Behavior Emoji sequence is rendered as a single glyph with no invisible characters in the run. Backspace, caret movement and selection treat this glyph as an indivisible entity. ### Actual Behavior From what I observe, it seems that there's an issue (or multiple issues) with many emoji sequences rendering and editing experience: - Emoji itself is rendered correctly, but is surrounded with multiple invisible characters (perhaps incorrectly calculated due to multiple codepoints in the cluster). I see that Terminal uses DirectWrite for itemizing the string, so perhaps it's not using the APIs correctly leading to a mismatch between displayed glyph and length of the run reserved for its rendering. DirectWrite (including text shaping engine) itself is updated already to handle emoji up to 13.1 correctly. - Caret is moving between invisible characters. Backspace is deleting invisible characters, affecting the rendering. - Selection will pick up individual constituents of the sequence (which are not rendered)
claunia added the Resolution-Duplicate label 2026-01-31 04:53:27 +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 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#15960
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?