starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows Terminal Preview - Read-only pane pop-up on tab switch #17894

New Issue
Closed
opened 2026-01-31 05:57:41 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 05:57:41 +00:00
Owner
Copy Link

Originally created by @MikeMM70 on GitHub (Jul 8, 2022).

Windows Terminal version

Windows Terminal Preview Version: 1.15.1862.0

Windows build number

10.0.19044.1766

Other Software

Seems to be on anything I have open in terminal

Steps to reproduce

Open 3 terminal tabs, PowerShell 7.2.5, Windows PowerShell 5.1, or command prompt. Set a keybind to toggle pane read-only mode (mine is set to ctrl-shift-), then toggle one of the tabs to read-only. Click on the 3 tabs in any order. Pop-up stating "Read-only mode enabled" appears both switching to AND from that read-only tab to/from other tabs.
image
image

This doesn't happen in my currently installed non-preview version Windows Terminal Version: 1.13.11431.0 (I should probably update, but I don't use the non-preview version much)

Expected Behavior

Personally, no popups at all, but if you have to, only when switching to the read-only tab. I did not try with split panes, I don't use them much, though I like the feature in theory.

Actual Behavior

Pop-up stating "Read-only mode enabled" appears both switching to AND from that read-only tab to/from other tabs.

I did discover that you can't set the settings tab to read-only, though I can live without that :)

Originally created by @MikeMM70 on GitHub (Jul 8, 2022). ### Windows Terminal version Windows Terminal Preview Version: 1.15.1862.0 ### Windows build number 10.0.19044.1766 ### Other Software Seems to be on anything I have open in terminal ### Steps to reproduce Open 3 terminal tabs, PowerShell 7.2.5, Windows PowerShell 5.1, or command prompt. Set a keybind to toggle pane read-only mode (mine is set to ctrl-shift-\), then toggle one of the tabs to read-only. Click on the 3 tabs in any order. Pop-up stating "Read-only mode enabled" appears both switching to AND from that read-only tab to/from other tabs. ![image](https://user-images.githubusercontent.com/10885147/178005974-cfd12cb6-97fe-4d85-b09e-a0a0461b1913.png) ![image](https://user-images.githubusercontent.com/10885147/178006790-82ea5764-ea65-4b8a-9aaf-5903485eede1.png) This doesn't happen in my currently installed non-preview version Windows Terminal Version: 1.13.11431.0 (I should probably update, but I don't use the non-preview version much) ### Expected Behavior Personally, no popups at all, but if you have to, only when switching to the read-only tab. I did not try with split panes, I don't use them much, though I like the feature in theory. ### Actual Behavior Pop-up stating "Read-only mode enabled" appears both switching to AND from that read-only tab to/from other tabs. I did discover that you can't set the settings tab to read-only, though I can live without that :)
claunia commented 2026-01-31 05:57:43 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 8, 2022):

oh my god, I'm confident that this is because of the focus in/out events. We should probably not suppress those, even in read only mode. Trick is, can we get the input generated for those events past the read-only guard simply?

@zadjii-msft commented on GitHub (Jul 8, 2022): _oh my god_, I'm confident that this is because of the focus in/out events. We should probably not suppress those, even in read only mode. Trick is, can we get the input generated for those events past the read-only guard simply?
claunia commented 2026-01-31 05:57:44 +00:00
Author
Owner
Copy Link

@MikeMM70 commented on GitHub (Jul 8, 2022):

I just updated my non-preview version to 1.14.1861.0 and I get the same bad behavior, just FYI.

Thank you for all the work you all do on making this otherwise awesome software!

@MikeMM70 commented on GitHub (Jul 8, 2022): I just updated my non-preview version to 1.14.1861.0 and I get the same bad behavior, just FYI. Thank you for all the work you all do on making this otherwise awesome software!
claunia commented 2026-01-31 05:57:44 +00:00
Author
Owner
Copy Link

@RedX2501 commented on GitHub (Aug 2, 2022):

I'm still seeing this on 1.15.1862

@RedX2501 commented on GitHub (Aug 2, 2022): I'm still seeing this on 1.15.1862
claunia commented 2026-01-31 05:57:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 2, 2022):

@RedX2501 That makes sense, it looks like #13483 isn't in any release branches yet. The bot should come through and post an update when it does show up in one!

@zadjii-msft commented on GitHub (Aug 2, 2022): @RedX2501 That makes sense, it looks like #13483 isn't in any release branches yet. The bot should come through and post an update when it does show up in one!
claunia commented 2026-01-31 05:57:44 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 5, 2022):

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

Handy links:

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

@ghost commented on GitHub (Aug 5, 2022):

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

Handy links:

@ghost commented on GitHub (Aug 5, 2022): :tada:This issue was addressed in #13483, which has now been successfully released as `Windows Terminal Preview v1.15.200`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.15.200) * [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-TerminalControl Issue-Bug Needs-Triage Priority-1 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#17894
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?