Skip to content
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

Add an option to not set the sandbox attribute #1580

Open
BloodlineL opened this issue Sep 30, 2024 · 2 comments
Open

Add an option to not set the sandbox attribute #1580

BloodlineL opened this issue Sep 30, 2024 · 2 comments

Comments

@BloodlineL
Copy link

The sandbox attribute will report an error in the console. I hope that the file is completely static. If this poses a security risk, at least remove the sandbox attribute when both allow-scripts and allow-same-origin are set. In this case, the security is no different from not setting the sandbox attribute, and there will be no error in the console.
01
02

gildas-lormeau added a commit to gildas-lormeau/single-file-core that referenced this issue Oct 3, 2024
@gildas-lormeau
Copy link
Owner

gildas-lormeau commented Oct 3, 2024

Thank you, the sandbox warning(s) should be fixed in the next version. The error should not exist (Blocked script...). How can I reproduce it?

@BloodlineL
Copy link
Author

The full error message is "Blocked script execution in 'about:srcdoc' because the document's frame is sandboxed and the 'allow-scripts' permission is not set.", but I can't reproduce it now, maybe it's because I updated Chrome, or it's caused by other plugins, sorry for the trouble.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants