Proper dataurl charset handling #275
Merged
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
- fix for handling data urls with charsets, e.g., data:text/html;charset=utf-8;base64,...
- properly decode unicode charsets
|
Hey @cyntler, Anything I can/should do to help this get merged? Or any reason you think it shouldn't be merged? |
|
@CodeSmith32 I merged it. |
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.
Currently, when viewing data urls with charsets, the app crashes because the header isn't stripped and base64 decoding (window.atob) throws an error due to invalid base64 chars. This uses a regex for stripping the header with any charset, but also extracts the charset and uses TextDecoder to convert the binary string into a unicode string before being written to the iframe (if necessary).