Drag and Drop "dotfile" to File Explorer creates file without leading "dot"

[christianzingg]

• VSCode Version: 1.30.2 (user setup)
• OS Version: Windows_NT x64 10.0.17763

Steps to Reproduce:

1. Open Folder in VS Code that contains a "dotfile" e.g. ".gitignore", ".env", ".htaccess"
2. Drag and Drop a "dotfile" to the windows file explorer. The pasted file name does not contain leading "dot" e.g. "gitignore" instead of ".gitignore"

Does this issue occur when all extensions are disabled?: Yes

[isidorn]

Can you reproduce this with latest vsocde insiders?

[christianzingg]

Yes, tested with:
Version: 1.31.0-insider (user setup)
Commit: 1b57516
Date: 2019-01-28T06:21:00.148Z

[isidorn]

Sorry for the slow response.I can not reproduce this.
If you still see this can you please attach a .gif showing this?

[christianzingg]

Sure - meanwhile with version 1.32.2

• Folder "C:\Drag" with files ".env" and "test.txt" opened in VSCode
• Drag&Drop ".env" file to Explorer Folder "C:\Drop"
• The dropped file is named without leading dot

[isidorn]

I can repro this both on Mac and Win.
I verified that we set the correct dataTransfer, but it seems that the OS or electron somehow deletes the dot.
@bpasero would know more. Might you have an idea why is this happening?

[bpasero]

@isidorn that is not the transfer relevant for the native explorer, can you check this line instead:

event.dataTransfer.setData(DataTransfers.DOWNLOAD_URL, [MIME_BINARY, basename(firstSource.resource), firstSource.resource.toString()].join(':'));

[oliverholliday]

This also happens when dragging from VSCode to Directory Opus so I don't think it's specifically an Explorer bug.

[isidorn]

@bpasero that line looks decent. The basename correctly returns .env. However after that line is exectued I am not sure how to check the data in the event.dataTransfer content. Whatever I check in chrome dev tools it does not have the actual data
So let me know if you would like me to check something precisely, I feel like I am walking in the dark here.

[bpasero]

@isidorn this could easily be an Electron issue, so the easiest would be to spin up Electron Fiddle and just try to reproduce with a simple test case that involves a file with leading dot.

[isidorn]

@christianzingg This is an electron issue. I was kind enough and filled this electron/electron#17394

[wmertens]

Triage: the linked electron issue was closed without resolution on account of the age. Perhaps it should be reopened if this wasn't fixed by newer electron releases?

[isidorn]

@wmertens If you can please create a new issue in the electron repository.

[wmertens]

@isidorn if you can reproduce it in a recent version, you should be able to reopen your original issue. I was just doing a drive-by triage

[deepak1556]

Issue is in chromium runtime and is present in recent versions as well.

[vscodenpa]

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!