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

Acrylic background not applied at startup #20566

New Issue
Open
opened 2026-01-31 07:17:43 +00:00 by claunia · 12 comments
claunia commented 2026-01-31 07:17:43 +00:00
Owner
Copy Link

Originally created by @davidegiacometti on GitHub (Sep 28, 2023).

Originally assigned to: @zadjii-msft on GitHub.

Windows Terminal version

1.18.2681.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

Just open Terminal.

In the following gif I am just opening Terminal from the taskbar icon and closing it with ALT+F4 multiple times in a row.
Acrylic background is applied only on the first startup (but it's random).

Terminal

Expected Behavior

Acrylic background applied

Actual Behavior

Acrylic background sometimes is not applied

Originally created by @davidegiacometti on GitHub (Sep 28, 2023). Originally assigned to: @zadjii-msft on GitHub. ### Windows Terminal version 1.18.2681.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce Just open Terminal. In the following gif I am just opening Terminal from the taskbar icon and closing it with ALT+F4 multiple times in a row. Acrylic background is applied only on the first startup (but it's random). ![Terminal](https://github.com/microsoft/terminal/assets/25966642/4c937edd-3d9a-4b61-a301-223f10b31581) ### Expected Behavior Acrylic background applied ### Actual Behavior Acrylic background sometimes is not applied
claunia added the Issue-BugNeeds-ReproProduct-TerminalPriority-2Area-Windowing labels 2026-01-31 07:17:44 +00:00
claunia commented 2026-01-31 07:17:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 28, 2023):

Here's a possibly goofy question - those times when it starts up without acrylic applied, if you just start typing on the keyboard, does that show up in the Terminal/? My hypothesis is that this is similar to #15479.

Are you launching the Terminal by shift+clicking on the taskbar?

Are there any other terminals running, or are you using compatibility.allowHeadless?

@zadjii-msft commented on GitHub (Sep 28, 2023): Here's a possibly goofy question - those times when it starts up without acrylic applied, if you just start typing on the keyboard, does that show up in the Terminal/? My hypothesis is that this is similar to #15479. Are you launching the Terminal by shift+clicking on the taskbar? Are there any other terminals running, or are you using `compatibility.allowHeadless`?
claunia commented 2026-01-31 07:17:45 +00:00
Author
Owner
Copy Link

@davidegiacometti commented on GitHub (Sep 28, 2023):

Here's a possibly goofy question - those times when it starts up without acrylic applied, if you just start typing on the keyboard, does that show up in the Terminal/? My hypothesis is that this is similar to #15479.

The windows does have focus, I can type but in order to see the acrylic background I have to focus another windows and go back to the Terminal one.

Are you launching the Terminal by shift+clicking on the taskbar?

Just a single click.
Behavior is the same with SHIFT+Click

Are there any other terminals running, or are you using compatibility.allowHeadless?

Just one single Terminal window.
I don't have compatibility.allowHeadless in the settings JSON.

EDIT: note that I have never experienced the focus issue you have linked and this behavior with acrylic has started yesterday after installing 1.18.2681.0.

@davidegiacometti commented on GitHub (Sep 28, 2023): > Here's a possibly goofy question - those times when it starts up without acrylic applied, if you just start typing on the keyboard, does that show up in the Terminal/? My hypothesis is that this is similar to #15479. The windows does have focus, I can type but in order to see the acrylic background I have to focus another windows and go back to the Terminal one. > Are you launching the Terminal by shift+clicking on the taskbar? Just a single click. Behavior is the same with SHIFT+Click > Are there any other terminals running, or are you using `compatibility.allowHeadless`? Just one single Terminal window. I don't have `compatibility.allowHeadless` in the settings JSON. EDIT: note that I have never experienced the focus issue you have linked and this behavior with acrylic has started yesterday after installing 1.18.2681.0.
claunia commented 2026-01-31 07:17:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 11, 2023):

Okay my dumb hypothesis is that the window has foreground, but isn't activated for some reason. I'm not even sure that's possible but user32 is dark and full of terrors.

Can you try out the following theme?

"theme": "Test",
"themes":
[
    {
        "name": "Test",
        "tab":
        {
            "background": "terminalBackground",
            "showCloseButton": "always",
            "unfocusedBackground": "#00000000"
        },
        "tabRow":
        {
            "background": "#00ff00ff",
            "unfocusedBackground": "#ff0000ff"
        },
        "window":
        {
            "applicationTheme": "dark",
        }
    },
]

That should aggressively change the color of the titlebar, depending on if the window is activated or not. When you first launch the terminal (when acrylic isn't working), which color do you get?

@zadjii-msft commented on GitHub (Oct 11, 2023): Okay my dumb hypothesis is that the window has foreground, but isn't activated for some reason. I'm not even sure that's possible but user32 is dark and full of terrors. Can you try out the following [theme](https://learn.microsoft.com/en-us/windows/terminal/customize-settings/themes)? ```json "theme": "Test", "themes": [ { "name": "Test", "tab": { "background": "terminalBackground", "showCloseButton": "always", "unfocusedBackground": "#00000000" }, "tabRow": { "background": "#00ff00ff", "unfocusedBackground": "#ff0000ff" }, "window": { "applicationTheme": "dark", } }, ] ``` That should aggressively change the color of the titlebar, depending on if the window is activated or not. When you first launch the terminal (when acrylic isn't working), which color do you get?
claunia commented 2026-01-31 07:17:45 +00:00
Author
Owner
Copy Link

@davidegiacometti commented on GitHub (Oct 11, 2023):

After launch
image

After switching back to Terminal
image

It becomes red when Terminal is unfocused.

@davidegiacometti commented on GitHub (Oct 11, 2023): _After launch_ ![image](https://github.com/microsoft/terminal/assets/25966642/b9eccb5f-dba7-4f14-84d6-6d273234f150) _After switching back to Terminal_ ![image](https://github.com/microsoft/terminal/assets/25966642/0f7dda68-0d1d-4691-976f-51be031748e3) It becomes red when Terminal is unfocused.
claunia commented 2026-01-31 07:17:45 +00:00
Author
Owner
Copy Link

@SmileEX commented on GitHub (Oct 18, 2023):

I have the same problem. Is there any solution

@SmileEX commented on GitHub (Oct 18, 2023): I have the same problem. Is there any solution
claunia commented 2026-01-31 07:17:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 18, 2023):

10.0.19045.0

In the following gif I am just opening Terminal from the taskbar icon and closing it with ALT+F4 multiple times in a row.
Acrylic background is applied only on the first startup (but it's random).

Hmm. Okay, here's another dumb question. Is there any other terminal window running when you're doing this? Or even more accurately, any other Terminal process? I wonder if the acrylic isn't getting appropriately applied when we reheat an old window (a la #15424). Like, the theory of that case is

  • You open two Terminal windows ("A" and "B")
  • Close B
  • Open another window, "C"
    • this reuses B's thread)
    • C opens without acrylic applied.

another observation here is that acrylic in the tab row was applied, so it's not just like, a rendering bug. This is more than just the control that's not acrylic, it's acrylic as a whole.

Is there any solution

Not yet. The newly re-written acrylic in Terminal Preview (to allow unfocused acrylic) might help here?

@zadjii-msft commented on GitHub (Oct 18, 2023): > 10.0.19045.0 > > In the following gif I am just opening Terminal from the taskbar icon and closing it with ALT+F4 multiple times in a row. > Acrylic background is applied only on the **first** startup (but it's random). Hmm. Okay, here's another dumb question. Is there any other terminal window running when you're doing this? Or even more accurately, any other Terminal process? I wonder if the acrylic isn't getting appropriately applied when we reheat an old window (a la #15424). Like, the theory of that case is * You open two Terminal windows ("A" and "B") * Close B * Open another window, "C" * this reuses B's thread) * C opens without acrylic applied. another observation here is that acrylic in the tab row _was_ applied, so it's not just like, a rendering bug. This is more than just the control that's not acrylic, it's acrylic as a whole. --- > Is there any solution Not yet. The newly re-written acrylic in [Terminal Preview](https://aka.ms/terminal-preview) (to allow unfocused acrylic) might help here?
claunia commented 2026-01-31 07:17:46 +00:00
Author
Owner
Copy Link

@davidegiacometti commented on GitHub (Oct 18, 2023):

@zadjii-msft no other process or windows running. I have also experienced this the first time I started Terminal after a reboot (note that auto startup is disabled).
Mmm.. I don't think acrylic is applied when the bug is hit (first post gif).

Is this that hard to reproduce for the team?
A few weeks ago I tried to debug it in a local build (without success 😭) and with the unfocused acrylic I was able to see the issue only in the title bar sometimes.

@davidegiacometti commented on GitHub (Oct 18, 2023): @zadjii-msft no other process or windows running. I have also experienced this the first time I started Terminal after a reboot (note that auto startup is disabled). Mmm.. I don't think acrylic is applied when the bug is hit (first post gif). Is this that hard to reproduce for the team? A few weeks ago I tried to debug it in a local build (without success 😭) and with the unfocused acrylic I was able to see the issue only in the title bar sometimes.
claunia commented 2026-01-31 07:17:46 +00:00
Author
Owner
Copy Link

@bingloo commented on GitHub (Oct 19, 2023):

I also had this issue after the Windows 11 app store update yesterday. default set "cmd", When running the bat file, reproduce this issue 100%.
version: 1.18.2822.0

@bingloo commented on GitHub (Oct 19, 2023): I also had this issue after the Windows 11 app store update yesterday. default set "cmd", When running the bat file, reproduce this issue 100%. version: 1.18.2822.0
claunia commented 2026-01-31 07:17:46 +00:00
Author
Owner
Copy Link

@tavrez commented on GitHub (Feb 6, 2024):

This looks fixed in v1.19.10302.0 for me, however tab row is still affected (probably related to #16661)

@tavrez commented on GitHub (Feb 6, 2024): This looks fixed in v1.19.10302.0 for me, however tab row is still affected (probably related to #16661)
claunia commented 2026-01-31 07:17:46 +00:00
Author
Owner
Copy Link

@revanmj commented on GitHub (Feb 11, 2024):

This looks fixed in v1.19.10302.0 for me, however tab row is still affected (probably related to #16661)

Well, I got that issue since this update and never had it before.

Same as above - just launch the Terminal (in my case from Start menu) and it doesn't have Acrylic background until I switch to a different window and back (once in a while just switching to different window will apply Acrylic).

So far it is 100% reproducible, ever since installing v1.19.10302.0 the app never launched with Acrylic applied right from the launch. Have this issue on two computers (laptop and desktop), both with Win11 23H2.

@revanmj commented on GitHub (Feb 11, 2024): > This looks fixed in v1.19.10302.0 for me, however tab row is still affected (probably related to #16661) Well, I got that issue since this update and never had it before. Same as above - just launch the Terminal (in my case from Start menu) and it doesn't have Acrylic background until I switch to a different window and back (once in a while just switching to different window will apply Acrylic). So far it is 100% reproducible, ever since installing v1.19.10302.0 the app never launched with Acrylic applied right from the launch. Have this issue on two computers (laptop and desktop), both with Win11 23H2.
claunia commented 2026-01-31 07:17:47 +00:00
Author
Owner
Copy Link

@revanmj commented on GitHub (Feb 20, 2024):

This looks fixed in v1.19.10302.0 for me, however tab row is still affected (probably related to #16661)

Well, I got that issue since this update and never had it before.

Same as above - just launch the Terminal (in my case from Start menu) and it doesn't have Acrylic background until I switch to a different window and back (once in a while just switching to different window will apply Acrylic).

So far it is 100% reproducible, ever since installing v1.19.10302.0 the app never launched with Acrylic applied right from the launch. Have this issue on two computers (laptop and desktop), both with Win11 23H2.

OK, turns out that latest version started somehow interfering with Mica for Everyone. After I added Terminal process to the blocklist in Mica for Everyone, Acrylic is now properly applied on startup (this was not needed before latest stable).

@revanmj commented on GitHub (Feb 20, 2024): > > This looks fixed in v1.19.10302.0 for me, however tab row is still affected (probably related to #16661) > > Well, I got that issue since this update and never had it before. > > Same as above - just launch the Terminal (in my case from Start menu) and it doesn't have Acrylic background until I switch to a different window and back (once in a while just switching to different window will apply Acrylic). > > So far it is 100% reproducible, ever since installing v1.19.10302.0 the app never launched with Acrylic applied right from the launch. Have this issue on two computers (laptop and desktop), both with Win11 23H2. OK, turns out that latest version started somehow interfering with Mica for Everyone. After I added Terminal process to the blocklist in Mica for Everyone, Acrylic is now properly applied on startup (this was not needed before latest stable).
claunia commented 2026-01-31 07:17:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 5, 2024):

you know what? this may be related to #16745

Another user reported that things got better after adding "compatibility.enableUnfocusedAcrylic": false to the global settings (i.e. next to useAcrylicInTabRow) (then rebooting the Terminal).

@zadjii-msft commented on GitHub (Jun 5, 2024): you know what? this may be related to #16745 Another user reported that things got better after adding `"compatibility.enableUnfocusedAcrylic": false` to the global settings (i.e. next to `useAcrylicInTabRow`) (then rebooting the Terminal).
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-Windowing Issue-Bug Needs-Repro Priority-2 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#20566
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?