Support 'full' paths for dropped files in the HTML5 ondrop event.

[krpano]

An important use-case for native-apps is the ability to receive files as input via drag-and-drop.

HTML5 has already nice APIs for controlling file dropping, but it is missing a possibility to get the real full paths of the dropped files.

In NW.js and Electron the 'File' HTML5 API was extended with a 'path' attribute that contains the full path:
https://docs.nwjs.io/en/latest/References/Changes%20to%20DOM/#fileitempath

Here an example:
https://ourcodeworld.com/articles/read/288/how-to-handle-drag-and-drop-file-feature-in-electron-framework

Please add that or a something similar to WebView2 too!

Thanks!
Klaus

AB#29710956

[pagoe-msft]

@krpano,

This is a great suggestion and something we will look into enabling

[FabioHEPL]

Any updates about this issue ?

[d2phap]

Looking forward to seeing this soon implemented

[Flaflo]

Since this has been tracked over a year ago, how is this one going? @pagoe-msft @champnic

[champnic]

Unfortunately no update on this one yet.

[cbastuckOT]

We're also looking for a solution to resolve full file paths

• in the Drag & Drop case
• when using <input type="file" /> element.

Would be great if we could declare domains as trusted to access picked files within our C++ application hosting the WebView2

[darbid]

+1 from me for this feature. I would like to check if the file being dropped is a Outlook .MSG file that is encrypted and thus reject it and/or decrypt it and then allow the new file to be dropped.

[victorthoang]

@krpano @darbid @cbastuckOT @Flaflo @d2phap

Thanks for your patience. The WebView2 team understands this is an important feature and would like to discuss further to create a solution that would best suit your needs. However before continuing on potential solutions, we would like to know some background on the specific situation you are facing. Could anyone please provide some details to some of these questions we had below:

• What is the goal you are trying to achieve with the drag and drop feature?
• What is the underlying problem you are facing in your internal development?
• Is there a specific solution/path that you'd like to see for us to get his accomplished? (e.g. Implement something like an OnFilesDropped event that contains the path(s) of the dropped element ID, or add a path field to the DOM API for trusted URL's, etc.)
• Will there be a need for file upload as well as download?

Thanks all.

[darbid]

• What is the goal you are trying to achieve with the drag and drop feature?

I want to be able to intercept the dragging and dropping of mail message files (.msg) either from file or from the Outlook client.

• What is the underlying problem you are facing in your internal development?

User dop encrypted Outlook messages, completes some form details and then uploads. The website rejects it all as the file was encrypted.

• Is there a specific solution/path that you'd like to see for us to get his accomplished? (e.g. Implement something like an OnFilesDropped event that contains the path(s) of the dropped element ID, or add a path field to the DOM API for trusted URL's, etc.)

I think I would be happy with how drag and drop is implemented for standard WPF/WinForms elements. I would like to receive notice of the drag, get access to the file, be able to alter the file being dropped and then let drop continue.

• Will there be a need for file upload as well as download?

I am not sure I understand this one.

[victorthoang]

@darbid I will probably need to rephrase my last question. It was in regards to the upload context menu (file picker). For example, some apps have multiple ways to upload a file. One is Drag & Drop. Another is when a user clicks "browse..." or similar, and then picks a file from a window that allows the user to choose a file from their computer/directory.

[krpano]

In all cases (filepicker, drag&drop) I would only want to get the full path.
The usage case is to use these file paths (of large files with sizes up to several gigabytes) and then to process them directly on native/C++ side.

So the Webview2 is only the front-end/UI and the actual processing is done in the back-end with C++ and therefore a direct access to the files is required.