You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The native web API showOpenFilePicker(), showSaveFilePicker() and showDirectoryPicker() do not return native path of the local file.
Expected/Proposed Behavior
The returned FileSystemFileHandle object or FileSystemDirectoryHandle object contain native path of the local file, such as path.
Additional Info
Compared to creating an <input type="file">, this is a more convenient way to show a file picker.
In addition, support for setting MIME type groups is also very useful.
The text was updated successfully, but these errors were encountered:
ssnangua
changed the title
Native file picker API do not return native path of the local file
Native file picker APIs do not return native path of the local file
Apr 11, 2024
For historical reasons, the value IDL attribute prefixes the filename with the string "C:\fakepath". Some legacy user agents actually included the full path (which was a security vulnerability). As a result of this, obtaining the filename from the value IDL attribute in a backwards-compatible way is non-trivial.
Issue Type
Current/Missing Behavior
The native web API
showOpenFilePicker()
,showSaveFilePicker()
andshowDirectoryPicker()
do not return native path of the local file.Expected/Proposed Behavior
The returned
FileSystemFileHandle
object orFileSystemDirectoryHandle
object contain native path of the local file, such aspath
.Additional Info
Compared to creating an
<input type="file">
, this is a more convenient way to show a file picker.In addition, support for setting MIME type groups is also very useful.
The text was updated successfully, but these errors were encountered: