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

Using an Unfocused Appearance resets any runtime palette and cursor changes #16198

New Issue
Open
opened 2026-01-31 05:00:28 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 05:00:28 +00:00
Owner
Copy Link

Originally created by @j4james on GitHub (Dec 18, 2021).

Windows Terminal version

1.12.3472.0

Windows build number

10.0.19041.1348

Other Software

No response

Steps to reproduce

  1. Open the Settings in Windows Terminal and go to the Profiles Defaults section.
  2. On the Appearance tab, enable the Unfocused Appearance option (you don't need to change any of the properties though).
  3. Open a WSL bash shell.
  4. Change the default background palette to red using an OSC 11 sequence:
    printf "\e]11;rgb:44/00/00\e\\"
  5. Change the cursor shape to a filled box (something other than your default) with a DECSCUSR sequence:
    printf "\e[1 q"
  6. Switch focus to another application and then switch back again.

Expected Behavior

When the focus returns, I'd expect the background color to be red again, and the cursor to be a filled box again.

Actual Behavior

The background color changes back to the original color scheme, and the cursor returns to the original value in the settings.

I'm not sure there is a good way to fix this though. Perhaps we should be saving the active settings when the app loses focus, and then restoring them when it gains focus again, rather than resetting everything? That doesn't handle all edge case, but it's probably better than nothing.

Otherwise I suppose we could say that runtime changes to these settings aren't expected to work if you've configured an Unfocused Appearance. But if we're going to take that approach, then I think we should really be disabling those sequences completely. Having them appear to work, but then get "randomly" reset just seems like a bug.

Originally created by @j4james on GitHub (Dec 18, 2021). ### Windows Terminal version 1.12.3472.0 ### Windows build number 10.0.19041.1348 ### Other Software _No response_ ### Steps to reproduce 1. Open the Settings in Windows Terminal and go to the _Profiles Defaults_ section. 2. On the _Appearance_ tab, enable the _Unfocused Appearance_ option (you don't need to change any of the properties though). 3. Open a WSL bash shell. 4. Change the default background palette to red using an `OSC 11` sequence: `printf "\e]11;rgb:44/00/00\e\\"` 5. Change the cursor shape to a filled box (something other than your default) with a `DECSCUSR` sequence: `printf "\e[1 q"` 6. Switch focus to another application and then switch back again. ### Expected Behavior When the focus returns, I'd expect the background color to be red again, and the cursor to be a filled box again. ### Actual Behavior The background color changes back to the original color scheme, and the cursor returns to the original value in the settings. I'm not sure there is a good way to fix this though. Perhaps we should be saving the active settings when the app loses focus, and then restoring them when it gains focus again, rather than resetting everything? That doesn't handle all edge case, but it's probably better than nothing. Otherwise I suppose we could say that runtime changes to these settings aren't expected to work if you've configured an _Unfocused Appearance_. But if we're going to take that approach, then I think we should really be disabling those sequences completely. Having them appear to work, but then get "randomly" reset just seems like a bug.
claunia added the Issue-BugPriority-3Product-TerminalArea-TerminalControl labels 2026-01-31 05:00:28 +00:00
claunia commented 2026-01-31 05:00:29 +00:00
Author
Owner
Copy Link

@Archomeda commented on GitHub (Oct 4, 2024):

I came across this problem as well in #17997. It resets my background color back to its original color when using this feature.

Also another note: this also occurs when ctrl+tabbing between tabs.

@Archomeda commented on GitHub (Oct 4, 2024): I came across this problem as well in #17997. It resets my background color back to its original color when using this feature. Also another note: this also occurs when ctrl+tabbing between tabs.
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-TerminalControl Issue-Bug Priority-3 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#16198
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?