starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Azure Cloud Shell has acrylic on with default settings #10095

New Issue
Closed
opened 2026-01-31 02:12:23 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 02:12:23 +00:00
Owner
Copy Link

Originally created by @jim-liu on GitHub (Aug 11, 2020).

Environment

Windows build number: 2004 build 19041
Windows Terminal version (if applicable): 1.1.2021

Steps to reproduce

  1. In settings.json, make sure nothing is inside profiles.defaults
  2. In Windows Terminal, open a Windows PowerShell tab, and notice that acrylic is off
  3. Open an Azure Cloud Shell tab, and notice that acrylic is on
  4. In Settings.json, set profiles.defaults.useAcrylic to false
  5. Switch back to the Azure Cloud Shell tab, and notice that acrylic is off

Expected behavior

Because https://aka.ms/terminal-profiles-schema states that profiles.defaults.useAcrylic defaults to false, I expect/assume an Azure Cloud Shell tab would have acrylic off by default.

Actual behavior

Azure Cloud Shell tabs have acrylic on by default.

Originally created by @jim-liu on GitHub (Aug 11, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: 2004 build 19041 Windows Terminal version (if applicable): 1.1.2021 ``` # Steps to reproduce 1. In **settings.json**, make sure nothing is inside **profiles.defaults** 1. In Windows Terminal, open a Windows PowerShell tab, and notice that acrylic is off 1. Open an Azure Cloud Shell tab, and notice that acrylic is on 1. In **Settings.json**, set **profiles.defaults.useAcrylic** to `false` 1. Switch back to the Azure Cloud Shell tab, and notice that acrylic is off # Expected behavior Because https://aka.ms/terminal-profiles-schema states that **profiles.defaults.useAcrylic** defaults to `false`, I expect/assume an Azure Cloud Shell tab would have acrylic off by default. # Actual behavior Azure Cloud Shell tabs have acrylic on by default.
claunia commented 2026-01-31 02:12:25 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (Aug 11, 2020):

I was surprised to see acrylic there.

https://github.com/microsoft/terminal/blob/fda80eaf64b6f4bb41f248f5c6b355d672ad64f8/src/cascadia/TerminalApp/AzureCloudShellGenerator.cpp#L39-L41

If the non-default color scheme and acrylic are required by some branding guideline, then perhaps Windows Terminal should write those settings of the Azure Cloud Shell profile to settings.json when it creates that file. Doing so would at least make it easier to understand which settings are making Azure Cloud Shell look different from other profiles.

@KalleOlaviNiemitalo commented on GitHub (Aug 11, 2020): I was surprised to see acrylic there. <https://github.com/microsoft/terminal/blob/fda80eaf64b6f4bb41f248f5c6b355d672ad64f8/src/cascadia/TerminalApp/AzureCloudShellGenerator.cpp#L39-L41> If the non-default color scheme and acrylic are required by some branding guideline, then perhaps Windows Terminal should write those settings of the Azure Cloud Shell profile to settings.json when it creates that file. Doing so would at least make it easier to understand which settings are making Azure Cloud Shell look different from other profiles.
claunia commented 2026-01-31 02:12:25 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 12, 2020):

Fair points.

@DHowett commented on GitHub (Aug 12, 2020): Fair points.
claunia commented 2026-01-31 02:12:25 +00:00
Author
Owner
Copy Link

@KnapSac commented on GitHub (Sep 8, 2020):

I'd like to take a look at fixing this, should the acrylic settings be written to the settings.json file, or should they be removed entirely?

@KnapSac commented on GitHub (Sep 8, 2020): I'd like to take a look at fixing this, should the acrylic settings be written to the settings.json file, or should they be removed entirely?
claunia commented 2026-01-31 02:12:25 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 8, 2020):

Meh, you can probably just remove it from the Azure generator and be done with it 😄

@DHowett commented on GitHub (Sep 8, 2020): Meh, you can probably just remove it from the Azure generator and be done with it :smile:
claunia commented 2026-01-31 02:12:25 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 22, 2020):

:tada:This issue was addressed in #7573, which has now been successfully released as Windows Terminal v1.3.2651.0.🎉

Handy links:

@ghost commented on GitHub (Sep 22, 2020): :tada:This issue was addressed in #7573, which has now been successfully released as `Windows Terminal v1.3.2651.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.3.2651.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 02:12:25 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 22, 2020):

:tada:This issue was addressed in #7573, which has now been successfully released as Windows Terminal Preview v1.4.2652.0.🎉

Handy links:

@ghost commented on GitHub (Sep 22, 2020): :tada:This issue was addressed in #7573, which has now been successfully released as `Windows Terminal Preview v1.4.2652.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.4.2652.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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-Settings good first issue Issue-Bug Priority-3 Product-Terminal Resolution-Fix-Committed
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#10095
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?