Repository navigation
[Fix] Dragging files into the chat input fails unless Shift is held #2184
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
Draft
zoomote2
wants to merge
1
commit into
main
Choose a base branch
from
fix/chat-drag-drop-no-shift-2t9fhxuwf9qlx
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+79
−2
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two of these five types can never match a real drag in the webview, and the matching itself is case-sensitive against an API that lowercases.
DataTransfer.typeslowercased. VS Code's owncontainsDragTypehelper (vs/platform/dnd/browser/dnd.ts) lowercases both sides for exactly this reason, with the comment "somehow the types are lowercase". Sotypes.includes("ResourceURIs")can never succeed.DataTransfers.RESOURCESis"ResourceURLs", not"ResourceURIs"(verified invs/base/browser/dnd.tson current main and 1.96; this repo pins VS Code types at 1.100).application/vnd.code.filesis not a VS Code type.fillEditorsDragDatasetstext/plain,text/uri-list,application/vnd.code.uri-list(INTERNAL_URI_LIST),ResourceURLs, andCodeEditors; the internal constants areCodeDataTransfers.EDITORS = "CodeEditors"andCodeDataTransfers.FILES = "CodeFiles".The fix still works today because Explorer/editor-tab drags also carry
application/vnd.code.uri-listandtext/uri-list, which happen to be all-lowercase and match exactly. But the two dead entries give false confidence — the new tests pass only because they synthesize exact-case payloads Chromium cannot produce — and acceptance would silently regress to the issue #2139 behavior if VS Code ever stops setting the uri-list types. Comparing case-insensitively (mirroringcontainsDragType) and using the real type names removes both risks: