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

first click in settings is ignored #17841

New Issue
Open
opened 2026-01-31 05:56:03 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 05:56:03 +00:00
Owner
Copy Link

Originally created by @george-tsiros on GitHub (Jul 1, 2022).

Windows Terminal version

'wt' is not recognized as an internal or external command, operable program or batch file.

Windows build number

Microsoft Windows [Version 10.0.22000.739]

Other Software

n.a.

Steps to reproduce

click window system icon
move mouse down to Settings option
click
move mouse to any option in the settings tab
click the option
click it again

Expected Behavior

the first click works

Actual Behavior

the first click does not work

https://www.youtube.com/watch?v=dyfAAZnYHxk

Originally created by @george-tsiros on GitHub (Jul 1, 2022). ### Windows Terminal version 'wt' is not recognized as an internal or external command, operable program or batch file. ### Windows build number Microsoft Windows [Version 10.0.22000.739] ### Other Software n.a. ### Steps to reproduce click window system icon move mouse down to `Settings` option click move mouse to any option in the settings tab click the option click it again ### Expected Behavior the first click works ### Actual Behavior the first click does not work https://www.youtube.com/watch?v=dyfAAZnYHxk
claunia added the Help WantedIssue-BugPriority-3Product-TerminalArea-SettingsUI labels 2026-01-31 05:56:03 +00:00
claunia commented 2026-01-31 05:56:04 +00:00
Author
Owner
Copy Link

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

This is weird. I think I was briefly able to repro this by making sure to keep the mouse in the leftmost are of the window, like, where the nav view is. But it was very fragile - it was very easy to snap out of that bugged state. And of course, as soon as I tried to get a screen recording, I could no longer repro.

It almost seemed like it had something to do with the UI first loading up... like, after a little bit of time, the UI finished loading and then even the first click would work. It's hard to describe.

Without a super consistent repro, I suspect we won't be able to investigate this fully 😕

@zadjii-msft commented on GitHub (Jul 5, 2022): This is weird. I think I was briefly able to repro this by making sure to keep the mouse in the leftmost are of the window, like, where the nav view is. But it was _very_ fragile - it was very easy to snap out of that bugged state. And of course, as soon as I tried to get a screen recording, I could no longer repro. It almost seemed like it had something to do with the UI first loading up... like, after a little bit of time, the UI finished loading and then even the first click would work. It's hard to describe. Without a super consistent repro, I suspect we won't be able to investigate this fully 😕
claunia commented 2026-01-31 05:56:04 +00:00
Author
Owner
Copy Link

@george-tsiros commented on GitHub (Jul 6, 2022):

do you have animations enabled in windows

@george-tsiros commented on GitHub (Jul 6, 2022): do you have animations enabled in windows
claunia commented 2026-01-31 05:56:05 +00:00
Author
Owner
Copy Link

@george-tsiros commented on GitHub (Jul 7, 2022):

This is weird. I think I was briefly able to repro this by making sure to keep the mouse in the leftmost are of the window, like, where the nav view is. But it was very fragile - it was very easy to snap out of that bugged state. And of course, as soon as I tried to get a screen recording, I could no longer repro.

It almost seemed like it had something to do with the UI first loading up... like, after a little bit of time, the UI finished loading and then even the first click would work. It's hard to describe.

Without a super consistent repro, I suspect we won't be able to investigate this fully 😕

what do you need from me

@george-tsiros commented on GitHub (Jul 7, 2022): > This is weird. I think I was briefly able to repro this by making sure to keep the mouse in the leftmost are of the window, like, where the nav view is. But it was _very_ fragile - it was very easy to snap out of that bugged state. And of course, as soon as I tried to get a screen recording, I could no longer repro. > > It almost seemed like it had something to do with the UI first loading up... like, after a little bit of time, the UI finished loading and then even the first click would work. It's hard to describe. > > Without a super consistent repro, I suspect we won't be able to investigate this fully 😕 what do you need from me
claunia commented 2026-01-31 05:56:05 +00:00
Author
Owner
Copy Link

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

Windows Terminal version

1.16.2352.0

Windows build number

10.0.22973.0

Other Software

No response

Steps to reproduce

  1. Launch Terminal with a profile tab and an unfocused settings UI tab
  2. Reorder the tabs
  3. Open settings UI tab
  4. Settings UI page elements are unclickable, but nav view items are

Expected Behavior

Should be able to click items on the settings UI after reordering.

Actual Behavior

Nav view is clickable, but content in the page and the save buttons aren't. Looks like it's because the page isn't initialized properly if the elements aren't loaded before reordering tabs?

@zadjii-msft commented on GitHub (Sep 8, 2022): > ### Windows Terminal version > 1.16.2352.0 > > ### Windows build number > 10.0.22973.0 > > ### Other Software > _No response_ > > ### Steps to reproduce > 1. Launch Terminal with a profile tab and an _unfocused_ settings UI tab > 2. Reorder the tabs > 3. Open settings UI tab > 4. Settings UI page elements are unclickable, but nav view items are > > ### Expected Behavior > Should be able to click items on the settings UI after reordering. > > ### Actual Behavior > Nav view is clickable, but content in the page and the save buttons aren't. Looks like it's because the page isn't initialized properly if the elements aren't loaded before reordering tabs?
claunia commented 2026-01-31 05:56:05 +00:00
Author
Owner
Copy Link

@jamespack commented on GitHub (Jul 9, 2023):

This one is kinda weird. If you leave the bounds of the window with the pointer and come back it prevents that. Seems that none of the ui items in the settings page are actually focused and setting it manually doesnt seem to help.

@jamespack commented on GitHub (Jul 9, 2023): This one is kinda weird. If you leave the bounds of the window with the pointer and come back it prevents that. Seems that none of the ui items in the settings page are actually focused and setting it manually doesnt seem to help.
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-SettingsUI Help Wanted Issue-Bug Priority-3 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#17841
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?