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

Use Mica Alt as tab bar's backdrop instead of bare Mica #19315

New Issue
Closed
opened 2026-01-31 06:39:52 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:39:52 +00:00
Owner
Copy Link

Originally created by @fitojb on GitHub (Feb 4, 2023).

When using Mica as the terminal's background, there is no visual differentiation between the app's UI and the terminal content or SUI. This can be fixed by using MicaAlt in the tab bar, as tabbed Windows Explorer and Windows Notepad do.

image

Originally created by @fitojb on GitHub (Feb 4, 2023). When using Mica as the terminal's background, there is no visual differentiation between the app's UI and the terminal content or SUI. This can be fixed by using MicaAlt in the tab bar, as tabbed Windows Explorer and Windows Notepad do. ![image](https://user-images.githubusercontent.com/554953/216754052-7868b792-0547-4478-9441-d5e0b55cc4a8.png)
claunia commented 2026-01-31 06:39:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 5, 2023):

So, this is an interesting scenario. We can only have one Mica surface for the entirety of the Terminal window, since we're using the DwnSetWindowAttribute version of mica. We can either get Mica or alt mica, but not both. I believe that Explorer is either using WinUI 3, or multiple XAML islands to try and achieve the combo effect, neither of which are really options for the Terminal window.

I think we're unfortunately just going to have to reject this request, for architectural reasons. We might be able to revisit if we ever move to WinUI 3, but that seems indefinitely far out for the time being.

@zadjii-msft commented on GitHub (Feb 5, 2023): So, this is an interesting scenario. We can only have one Mica surface for the entirety of the Terminal window, since we're using the DwnSetWindowAttribute version of mica. We can either get Mica or alt mica, but _not both_. I believe that Explorer is either using WinUI 3, or multiple XAML islands to try and achieve the combo effect, neither of which are really options for the Terminal window. I think we're unfortunately just going to have to reject this request, for architectural reasons. We might be able to revisit if we ever move to WinUI 3, but that seems indefinitely far out for the time being.
claunia commented 2026-01-31 06:39:55 +00:00
Author
Owner
Copy Link

@yjlin0224 commented on GitHub (Jun 18, 2023):

@zadjii-msft If now it is impossible to use both Mica and Mica Alt, how about add an option to use Mica Alt only?

@yjlin0224 commented on GitHub (Jun 18, 2023): @zadjii-msft If now it is impossible to use both Mica and Mica Alt, how about add an option to use Mica Alt only?
claunia commented 2026-01-31 06:39:56 +00:00
Author
Owner
Copy Link

@BreeceW commented on GitHub (May 6, 2024):

This should be reopened. The effect achieved in apps using Mica Alt like Explorer is not done by using both Mica and Mica Alt, but rather by laying a solid color brush (built in to WinUI 2 as LayerOnMicaBaseAltFillColorDefault which is SolidColorBrush #733A3A3A in dark mode) on top of just Mica Alt. Therefore there is no architectural issue in applying the Windows 11 design guidelines to Terminal in this case and using Mica Alt.

So a XAML Islands window with DwmSetWindowAttribute DWMWA_SYSTEMBACKDROP_TYPE DWMSBT_TABBEDWINDOW and a panel with the brush LayerOnMicaBaseAltFillColorDefault woud look like this:
XAML Island window with a tab view with translucency over Mica Alt
And this provides the visual contrast requested in the issue.

@BreeceW commented on GitHub (May 6, 2024): This should be reopened. The effect achieved in apps using Mica Alt like Explorer is not done by using both Mica and Mica Alt, but rather by laying a solid color brush (built in to WinUI 2 as `LayerOnMicaBaseAltFillColorDefault` which is SolidColorBrush #733A3A3A in dark mode) on top of just Mica Alt. Therefore there is no architectural issue in applying the Windows 11 design guidelines to Terminal in this case and using Mica Alt. So a XAML Islands window with `DwmSetWindowAttribute` `DWMWA_SYSTEMBACKDROP_TYPE` `DWMSBT_TABBEDWINDOW` and a panel with the brush `LayerOnMicaBaseAltFillColorDefault` woud look like this: ![XAML Island window with a tab view with translucency over Mica Alt](https://github.com/microsoft/terminal/assets/18747724/e1f9cc9f-1227-4199-a640-60a5d0eeb939) And this provides the visual contrast requested in the issue.
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-Theming External-Blocked-WinUI3 Needs-Tag-Fix Needs-Triage Resolution-Won't-Fix
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#19315
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?