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

Background color changes by itself sometimes #10289

New Issue
Closed
opened 2026-01-31 02:17:26 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 02:17:26 +00:00
Owner
Copy Link

Originally created by @vadimkantorov on GitHub (Aug 25, 2020).

Compare:
Tab 1:
image
Tab 2:
image

I didn't do anything to change bg color of the first tab, it happened by itself.

Originally created by @vadimkantorov on GitHub (Aug 25, 2020). Compare: Tab 1: ![image](https://user-images.githubusercontent.com/1041752/91201021-3ac18a00-e700-11ea-9d9b-b04b84248049.png) Tab 2: ![image](https://user-images.githubusercontent.com/1041752/91201042-43b25b80-e700-11ea-9ff7-1ac8d838f14d.png) I didn't do anything to change bg color of the first tab, it happened by itself.
claunia added the Resolution-Duplicate label 2026-01-31 02:17:26 +00:00
claunia commented 2026-01-31 02:17:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 25, 2020):

That looks to me like acrylic turned itself off. Sometimes that just happens, by OS policy. I think there are some dupes for that floating around...

@zadjii-msft commented on GitHub (Aug 25, 2020): That looks to me like acrylic turned itself off. Sometimes that just happens, by OS policy. I think there are some dupes for that floating around...
claunia commented 2026-01-31 02:17:27 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Aug 26, 2020):

It looks super-weird (especially given that this does not apply uniformly to all tabs) - at first I thought that my laptop ran out of power and screen has been dimmed for power saving.

@vadimkantorov commented on GitHub (Aug 26, 2020): It looks super-weird (especially given that this does not apply uniformly to all tabs) - at first I thought that my laptop ran out of power and screen has been dimmed for power saving.
claunia commented 2026-01-31 02:17:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 26, 2020):

@vadimkantorov What OS version are you on? This might be #7047

(#1414 is also a related discussion)

@zadjii-msft commented on GitHub (Aug 26, 2020): @vadimkantorov What OS version are you on? This might be #7047 (#1414 is also a related discussion)
claunia commented 2026-01-31 02:17:28 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Aug 26, 2020):

Windows 10 version 2004, build 19041

@vadimkantorov commented on GitHub (Aug 26, 2020): Windows 10 version 2004, build 19041
claunia commented 2026-01-31 02:17:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 26, 2020):

Yep, that'll do it. I'm pretty confident you're seeing the affects of #7047. I believe that's a bug they're gonna service, but I'm not totally sure about its status. I'd follow #7047 for updates.

/dup #7047

@zadjii-msft commented on GitHub (Aug 26, 2020): Yep, that'll do it. I'm pretty confident you're seeing the affects of #7047. I _believe_ that's a bug they're gonna service, but I'm not totally sure about its status. I'd follow #7047 for updates. /dup #7047
claunia commented 2026-01-31 02:17:28 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 26, 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 (Aug 26, 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:17:28 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Aug 26, 2020):

Is it that "transparency" does not work? Or is it that "transparency" gets enabled by itself? It seems the latter in my case...

@vadimkantorov commented on GitHub (Aug 26, 2020): Is it that "transparency" does not work? Or is it that "transparency" gets enabled by itself? It seems the latter in my case...
claunia commented 2026-01-31 02:17:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 26, 2020):

Basically, the OS incorrectly decides that your system can't support acrylic (when it really can), so it disables it. It's not consistent though, which is why it seems like sometimes it doesn't work.

@zadjii-msft commented on GitHub (Aug 26, 2020): Basically, the OS incorrectly decides that your system can't support acrylic (when it really can), so it disables it. It's not consistent though, which is why it seems like sometimes it doesn't work.
claunia commented 2026-01-31 02:17:29 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Aug 26, 2020):

Maybe it's again related to low CPU/RAM resources. But it looks supper weird. I'd prefer whole terminal downgraded or an option to always start it without Acrylic, rather than downgrading just one tab out of many

@vadimkantorov commented on GitHub (Aug 26, 2020): Maybe it's again related to low CPU/RAM resources. But it looks supper weird. I'd prefer whole terminal downgraded or an option to always start it without Acrylic, rather than downgrading just one tab out of many
claunia commented 2026-01-31 02:17:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 26, 2020):

It's actually caused by a bug in DWM. It incorrectly doesn't re-populate the properties for the monitor or something - I don't really understand the bug. I do know that the bug is fixed already internally, so it won't be too long before it rolls out to Insiders.

The Terminal unfortunately doesn't really have any way to know if acrylic will or not work when we ask for it. That's not really something that XAML exposes to us, and I'm not really sure it's worth our effort to add some mitigation code on our side for a bug that's already fixed.

@zadjii-msft commented on GitHub (Aug 26, 2020): It's actually caused by a bug in DWM. It incorrectly doesn't re-populate the properties for the monitor or something - I don't really understand the bug. I do know that the bug is fixed already internally, so it won't be too long before it rolls out to Insiders. The Terminal unfortunately doesn't really have any way to know if acrylic will or not work when we ask for it. That's not really something that XAML exposes to us, and I'm not really sure it's worth our effort to add some mitigation code on our side for a bug that's _already fixed_.
claunia commented 2026-01-31 02:17:29 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Aug 26, 2020):

When I remove focus from Terminal, light-black turns back into dark-black. So yeah, probably DWM fix is the right place for the fix

@vadimkantorov commented on GitHub (Aug 26, 2020): When I remove focus from Terminal, light-black turns back into dark-black. So yeah, probably DWM fix is the right place for the fix
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#10289
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?