[Feature Request]: Web File System API's showOpenFilePicker() should remember previous directory

[absidue]

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.

Electron Version

30.0.2

What operating system are you using?

Windows

Operating System Version

Windows 10 19045.4412

What arch are you using?

x64

Last Known Working Electron version

No response

Expected Behavior

The Web File System API's showOpenFilePicker() function has an option to specify an id. The browser (in this case Electron) should remember the directory that you last selected a file from and if you call the function again with the same ID, it should open the file picker to that directory.

1. Click button to open the file picker
2. Navigate to a directory that isn't the default one
3. Pick a file
4. Click the button again to open the file picker
5. You should be seeing the same directory that you picked the first file from.

Actual Behavior

Electron always opens the file picker to the default location or the well-known directory set in the startIn option.

Testcase Gist URL

https://gist.github.com/absidue/8124af98e9971c17b1455cc6c38aab3d

Additional Information

No response

[codebytere]

@absidue this is not supported at the moment, and explicitly logs that to the console:

[3396:0604/110611.311958:INFO:file_system_access_permission_context.cc(588)] NOTIMPLEMENTED GetLastPickedDirectory

I can certain consider taking a look at adding it in the future though!

[absidue]

Oh goodness! I'm really sorry, I completely missed that log message.

Thank you for implementing the Web File System API in Electron, the stuff that is already implemented works great!

[codebytere]

@absidue no worries :D I can try to give it a go - the main reason I didn't initially was that the feature relies on Chromium mechanics we don't have a comparable existing concept of, so we'd have to roll our own store for per-origin picker settings associated with a given Browser context.

https://chromium-review.googlesource.com/c/chromium/src/+/2645845 is the upstream impl