Allow opening very large files manually from inside the webview #41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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. silx-kit/h5web#1264), as this might give us a more generic solution.