more robust data uri with base64 encoded data. Handle whitespaces.#621
Merged
danfickle merged 1 commit intoDec 18, 2020
Conversation
syjer
marked this pull request as draft
December 17, 2020 15:30
syjer
marked this pull request as ready for review
December 17, 2020 15:31
Owner
|
Thanks mate. I like your picture. Resembles me, maybe! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR allow a more robust handling of base64 encoded data that contains whitespaces.
Chrome&co are able to render them.
I've noticed few issues related to this problem: