-
Notifications
You must be signed in to change notification settings - Fork 138
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make resources work after extraction #141
Comments
What do you mean? |
It's a limitation of the browser because you're opening the page from the filesystem. If you use an HTTP server, resources will be displayed as expected. |
Oh, indeed. I'm sorry for the confusion then, I thought this limitation only applied to the single-file archive and not to the extracted contents. |
Note that it used to work in the past, but vendors make the use of the filesystem less and less convenient, probably for security reasons. |
I see. Then the best thing we can do is to warn users about this better, not sure how though. Maybe add a README to the archive that hints at miniserve or something like that? |
I agree, I'll try to document this issue. I'll need to test it in all major browsers first. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I really like the concept of having all resources bundled in a zip file, as opposed to having to embed them as base64 in the html. However, it's a bit unfortunate that the extracted output only works as zip file: when extracting the contents and opening it, all resources are broken. It'd be cool to have both. The idea is that JavaScript is only required for the single-file, and one still has a fully static archive if needed.
I don't know much about how this works internally, but for me it'd be fine if the zip archive contained a separate
index_archive.html
that does this job instead of having everything within a singleindex.html
. (Or maybe swap the names, and haveindex_singlefile.html
instead)(Related to #102 and #119)
The text was updated successfully, but these errors were encountered: