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

Irrelevant Caret Browsing warning when pressing F7 on keyboard #5637

New Issue
Closed
opened 2026-01-31 00:17:57 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 00:17:57 +00:00
Owner
Copy Link

Originally created by @shytikov on GitHub (Dec 18, 2019).

Environment

Windows build number: 10.0.18362.0 
Windows Terminal version (if applicable): 0.7.3451.0

Steps to reproduce

  • Open WindowsTerminal
  • Press F7

Expected behavior

Action binded to F7 should be triggered

Actual behavior

Irrelevant IE window pops up.

image

This is especially stupid if pressing F7 has contextual meaning, like create folder in two-panel manager like Far or in any other console application.

image

This behavior actually blocks list of most recent commands in cmd too (which is core functionality):

image

Caret browsing does not make sense in this context and I don't get why we have pieces of IE sticking out of terminal...

Originally created by @shytikov on GitHub (Dec 18, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: 10.0.18362.0 Windows Terminal version (if applicable): 0.7.3451.0 ``` # Steps to reproduce * Open `WindowsTerminal` * Press `F7` # Expected behavior Action binded to `F7` should be triggered # Actual behavior Irrelevant `IE` window pops up. ![image](https://user-images.githubusercontent.com/1185905/71087769-4df97e80-219d-11ea-8c09-0aa42b7f4047.png) This is especially stupid if pressing `F7` has contextual meaning, like create folder in two-panel manager like `Far` or in any other console application. ![image](https://user-images.githubusercontent.com/1185905/71088117-09221780-219e-11ea-867d-6f8475402c10.png) This behavior actually blocks list of most recent commands in `cmd` too (which is core functionality): ![image](https://user-images.githubusercontent.com/1185905/71088271-569e8480-219e-11ea-9a35-4ed4167212dc.png) Caret browsing does not make sense in this context and I don't get why we have pieces of `IE` sticking out of `terminal`...
claunia added the Needs-TriageResolution-Duplicate labels 2026-01-31 00:17:57 +00:00
claunia commented 2026-01-31 00:17:58 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 19, 2019):

why we have pieces of IE

It's a fair question. It's partly answered in https://github.com/microsoft/terminal/issues/638#issuecomment-510999193.

@DHowett-MSFT commented on GitHub (Dec 19, 2019): > why we have pieces of `IE` It's a fair question. It's partly answered in https://github.com/microsoft/terminal/issues/638#issuecomment-510999193.
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 Needs-Triage Resolution-Duplicate
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#5637
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?