So ... <input type="file"> works inside webviews, duh!
It's not the ideal UX, but it's a workaround for now.
Now I'm wondering whether this UX is better than to try loading a 1.9 GB file into memory... But then where do you put the limit. I could add a command to open a "standalone" H5Web webview with a file picker like this but then discoverability would be a problem.
I think I'll wait to see what the performance is like with a provider that can do range requests (cf. https://github.com/silx-kit/h5web/issues/1264), as this might give us a more generic solution.
So ...
<input type="file">works inside webviews, duh!It's not the ideal UX, but it's a workaround for now.
Now I'm wondering whether this UX is better than to try loading a 1.9 GB file into memory... But then where do you put the limit. I could add a command to open a "standalone" H5Web webview with a file picker like this but then discoverability would be a problem.
I think I'll wait to see what the performance is like with a provider that can do range requests (cf. https://github.com/silx-kit/h5web/issues/1264), as this might give us a more generic solution.