-
Notifications
You must be signed in to change notification settings - Fork 24
iframe hardening #169
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
Merged
+41
−11
Merged
iframe hardening #169
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The vast majority of EPUB publications don't need localStorage, so in the real world it probably won't hurt to disable it, but just FYI: disabling
localStoragekills interactive features in some EPUBs (reflow and fixed layout), for example where the user can enter their name for a personalised story, or where some progress data is stored to deliver a contextual user experience. In Thorium Desktop each publication has its own origin so the store is shared amongst all book chapters but doesn't leak out, there is some built-in isolation already (I guess the web reader cannot make this assumption).Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I was quite involved in this topic – you may remember I was the one who accidentally discovered Apple Books.app used the same domain for all books and local storage was consequently global/shared, and they had to rush a new release as it went public on Twitter. 😶
At some point there were talks and some spec draft for suborigins or something like that.
I'm not holding my breath as it was a long long time ago and I'm not finding anything relevant. 😬
Edit: And well it wouldn't be a toolkit concern anyway.