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

Drag-Drop file not working with initial/default tab #6536

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

Originally created by @deoradh on GitHub (Feb 20, 2020).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 0.9.433.0

Any other software? No

Steps to reproduce

  1. Start WT, allow first tab to auto-create
  2. Attempt to drag file to first tab, note inability to drop, and no "Copy as path" tooltip
  3. Create new tab
  4. Attempt to drag file to new tab, note "Copy as path" works
  5. Delete first tab
  6. Create new tab of same profile as the default
  7. Attempt to drag file to each tab, note "Copy as path" works for each

Expected behavior

"Copy as path" works for all tabs, including the default

Actual behavior

"Copy as path" appears to not work for the initial, default tab. This does not appear to be a matter of the invoked host (eg, cmd vs PS Core), but behaves like the default tab is simply not registered as a drop target.

Originally created by @deoradh on GitHub (Feb 20, 2020). # Environment ```none Windows build number: 10.0.18363.0 Windows Terminal version (if applicable): 0.9.433.0 Any other software? No ``` # Steps to reproduce 1. Start WT, allow first tab to auto-create 2. Attempt to drag file to first tab, note inability to drop, and no "Copy as path" tooltip 3. Create new tab 4. Attempt to drag file to new tab, note "Copy as path" works 5. Delete first tab 6. Create new tab of same profile as the default 7. Attempt to drag file to each tab, note "Copy as path" works for each # Expected behavior "Copy as path" works for all tabs, including the default # Actual behavior "Copy as path" appears to not work for the initial, default tab. This does not appear to be a matter of the invoked host (eg, cmd vs PS Core), but behaves like the default tab is simply not registered as a drop target.
claunia commented 2026-01-31 00:41:06 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 20, 2020):

I can't reproduce this, even relaunching terminal 10 times. Is there anything else unusual about your environment?

@DHowett-MSFT commented on GitHub (Feb 20, 2020): I can't reproduce this, even relaunching terminal 10 times. Is there anything else unusual about your environment?
claunia commented 2026-01-31 00:41:06 +00:00
Author
Owner
Copy Link

@deoradh commented on GitHub (Feb 20, 2020):

Nope.. I'm not even on any insider rings. I was dragging the same file each time. It was repeatable on my machine across restarts of terminal.

It's not reproducing this morning.

One change since last night: My default profile is Powershell Preview. When it was reproducing I was on preview 3. Since that time I updated to rc2 and juggled some profiles around while I looked at the generator support (nice, btw.. but could use some docs for the user).

Perhaps that had an effect.

@deoradh commented on GitHub (Feb 20, 2020): Nope.. I'm not even on any insider rings. I was dragging the same file each time. It was repeatable on my machine across restarts of terminal. It's not reproducing this morning. One change since last night: My default profile is Powershell Preview. When it was reproducing I was on preview 3. Since that time I updated to rc2 and juggled some profiles around while I looked at the generator support (nice, btw.. but could use some docs for the user). Perhaps that had an effect.
claunia commented 2026-01-31 00:41:07 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 20, 2020):

@deoradh Any chance what you're seeing is actually #4567? That might explain why it seems so random.

@DHowett-MSFT I'm considering pulling #2606 into 1.0 if that's the case. #4567 seems like a much easier/trivial way to hit that bug, and might be worth pulling forward. Thoughts?

@zadjii-msft commented on GitHub (Feb 20, 2020): @deoradh Any chance what you're seeing is actually #4567? That might explain why it seems so random. @DHowett-MSFT I'm considering pulling #2606 into 1.0 if that's the case. #4567 seems like a much easier/trivial way to hit that bug, and might be worth pulling forward. Thoughts?
claunia commented 2026-01-31 00:41:07 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 20, 2020):

Oh! Great pull!

@DHowett-MSFT commented on GitHub (Feb 20, 2020): Oh! Great pull!
claunia commented 2026-01-31 00:41:07 +00:00
Author
Owner
Copy Link

@deoradh commented on GitHub (Feb 20, 2020):

@zadjii-msft -- It's uncertain.

I can repro #2606/#4567, but I cannot state that this was the same. It is possible: My PS startup spews a bunch of text at the start, so I may have found myself dragging to the bottom of the window, where the cursor was, and so by chance never seeing what happens if I was in the upper portion of the pane. But it doesn't explain the impression that this was resolving for all subsequent tabs opened.

But at this point, it looks like I can only give the impression. I can't repro it anymore except for the known bug. (Count this as a vote for pulling forward, anyway.)

@deoradh commented on GitHub (Feb 20, 2020): @zadjii-msft -- It's uncertain. I can repro #2606/#4567, but I cannot state that this was the same. It *is* possible: My PS startup spews a bunch of text at the start, so I may have found myself dragging to the bottom of the window, where the cursor was, and so by chance never seeing what happens if I was in the upper portion of the pane. But it doesn't explain the impression that this was resolving for all subsequent tabs opened. But at this point, it looks like I can only give the impression. I can't repro it anymore except for the known bug. (Count this as a vote for pulling forward, anyway.)
claunia commented 2026-01-31 00:41:07 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 18, 2020):

@deoradh thanks again -- I know we're not a hundred percent sure if it's the same bug, but for now I'm going to track them together. It seems like we the platform (not the Terminal, unfortunately) may have a hit-testing issue in general.

Closing this one in favor of talking about it in #2606. Since 2606 may require changes to Windows, it might not make it for 1.0 -- we're only as agile as our slowest component 😄

@DHowett-MSFT commented on GitHub (Mar 18, 2020): @deoradh thanks again -- I know we're not a hundred percent sure if it's the same bug, but for now I'm going to track them together. It seems like we _the platform_ (not the Terminal, unfortunately) may have a hit-testing issue in general. Closing this one in favor of talking about it in #2606. Since 2606 may require changes to Windows, it might not make it for 1.0 -- we're only as agile as our slowest component :smile:
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-UserInterface Needs-Attention Product-Terminal 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#6536
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?