Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drag & Drop Folder to Elevated Terminal Not Working #18048

Closed
arpan3t opened this issue Oct 14, 2024 · 4 comments
Closed

Drag & Drop Folder to Elevated Terminal Not Working #18048

arpan3t opened this issue Oct 14, 2024 · 4 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@arpan3t
Copy link

arpan3t commented Oct 14, 2024

Windows Terminal version

1.20.11781.0

Windows build number

10.0.19045

Other Software

No response

Steps to reproduce

  1. Open Windows Terminal as administrator.
  2. Open File Explorer (explorer.exe) to a directory that contains a subdirectory.
  3. Drag subdirectory from File Explorer to elevated Windows Terminal new tab icon.

Expected Behavior

New tab using default profile should open with the working directory of the subdirectory that was dragged over, as detailed here.

Actual Behavior

🚫Windows Unavailable mouse pointer icon is displayed, and dropping the folder does nothing.

Tried launching explorer.exe from the same elevated Windows Terminal but get the same results. Looks like the drag & drop feature only works for non-elevated Windows Terminal processes, which does work in the same environment btw. Not sure if this is intentional to prevent some sort of privilege escalation scenario or something, but it's not a deal imo. Just saw the feature in the documentation, but I doubt I'd use it regularly. Maybe just add a note to the documentation that it only works in non-elevated Windows Terminals.

@arpan3t arpan3t added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Oct 14, 2024
@DHowett
Copy link
Member

DHowett commented Oct 14, 2024

Not sure if this is intentional to prevent some sort of privilege escalation scenario or something

This is a Windows platform restriction that is also present in the original console host. The clipboard is the only "approved" way to get content from a medium-integrity process to a high-integrity one on the same Window Station.

We'll add a documentation note! Sorry!

@DHowett DHowett closed this as completed Oct 14, 2024
@c834606877
Copy link

So many users raise issue here, it indicates that this Drag&Drop feature is necessary for daily usage.
So, Please make it as a optional feature for those users want use it at take self own risk way!
Do NOT break the user's usage habits. even you have strong security reason, you can take a msgbox as warning.

@lhecker
Copy link
Member

lhecker commented Oct 21, 2024

There can't possibly be "user's habits" yet, since what you're asking for has never worked on any Windows version before. But we'll definitely take it into consideration for future versions.

@Quaraxkad
Copy link

Quaraxkad commented Dec 28, 2024

This is a Windows platform restriction that is also present in the original console host. The clipboard is the only "approved" way to get content from a medium-integrity process to a high-integrity one on the same Window Station.

Are you sure that's right? For me, drag+drop of a file or folder does work in normal conhost window but NOT Terminal. Since switching to Terminal as my default i have not been able to drag+drop files or folders to "paste" their paths. I used this extensively in conhost. I searched and see a lot of posts about similar issues but they're almost all unclear if they're talking about the same feature I am.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

5 participants