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

acrylicOpacity not working on a two monitor setup when screen looses focus #3881

New Issue
Closed
opened 2026-01-30 23:32:24 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 23:32:24 +00:00
Owner
Copy Link

Originally created by @lcs-felix on GitHub (Sep 15, 2019).

Environment

Windows build number: 10.0.18980.0

Windows Terminal version (if applicable): 0.4.2382.0

Steps to reproduce

Two displays setup: in my case, an LG monitor, used as the primary monitor, connected through an HDMI cable to a Dell Inspiron 14 5000.

Expected behavior

I have the following configs on my profile.json file (just a fragment of the file):

        {
          "acrylicOpacity": 0.85,
          "closeOnExit": true,
          "colorScheme" : "Solarized Dark",
          "commandline": "wsl.exe -d Ubuntu-18.04",
          "cursorColor": "#FFFFFF",
          "cursorShape": "vintage",
          "fontFace" : "Fira Code",
          "fontSize": 12,
          "guid": "{2c4de342-38b7-51cf-b940-2309a097f518}",
          "historySize": 9001,
          "icon": "ms-appx:///ProfileIcons/{9acb9455-ca41-5af7-950f-6bca1bc9722f}.png",
          "name": "Ubuntu",
          "padding": "10, 0, 10, 0",
          "snapOnInput": true,
          "useAcrylic": true
        },

The opacity would work besides the focused screen at the moment. Example: if my terminal is open on Dell display, even I move the focus to LG display, the opacity must stay working.

For reference purposes, that's like iTerm2 behaves.

Actual behavior

Actually, when I change the display focus, the terminal opacity is disabled. This recorded video capture tries to illustrate the behavior. At second 00:07 I click on the other display that leads to opacity losing. When I click again on the second display with the open terminal, the opacity is enabled.

Originally created by @lcs-felix on GitHub (Sep 15, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18980.0 Windows Terminal version (if applicable): 0.4.2382.0 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Two displays setup: in my case, an LG monitor, used as the primary monitor, connected through an HDMI cable to a Dell Inspiron 14 5000. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> I have the following configs on my `profile.json` file (just a fragment of the file): ```json { "acrylicOpacity": 0.85, "closeOnExit": true, "colorScheme" : "Solarized Dark", "commandline": "wsl.exe -d Ubuntu-18.04", "cursorColor": "#FFFFFF", "cursorShape": "vintage", "fontFace" : "Fira Code", "fontSize": 12, "guid": "{2c4de342-38b7-51cf-b940-2309a097f518}", "historySize": 9001, "icon": "ms-appx:///ProfileIcons/{9acb9455-ca41-5af7-950f-6bca1bc9722f}.png", "name": "Ubuntu", "padding": "10, 0, 10, 0", "snapOnInput": true, "useAcrylic": true }, ``` The opacity would work besides the focused screen at the moment. Example: if my terminal is open on Dell display, even I move the focus to LG display, the opacity must stay working. For reference purposes, that's like iTerm2 behaves. # Actual behavior <!-- What's actually happening? --> Actually, when I change the display focus, the terminal opacity is disabled. [This recorded video capture](https://youtu.be/8HKNohf7Fms) tries to illustrate the behavior. At second 00:07 I click on the other display that leads to opacity losing. When I click again on the second display with the open terminal, the opacity is enabled.
claunia added the Resolution-By-DesignNeeds-TriageNeeds-Tag-Fix labels 2026-01-30 23:32:24 +00:00
claunia commented 2026-01-30 23:32:25 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 15, 2019):

This is, unfortunately, by design. System policy dictates (and Windows controls this, not Terminal(!)) that only a currently-active window can be displayed with the acrylic effect.

@DHowett-MSFT commented on GitHub (Sep 15, 2019): This is, unfortunately, by design. System policy dictates (and Windows controls this, not Terminal(!)) that _only a currently-active window_ can be displayed with the acrylic effect.
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 Needs-Tag-Fix Needs-Triage Resolution-By-Design
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#3881
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?