Fix bug with font tags in chrome #1
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
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.
This pull request is related to the following trello card: https://trello.com/c/OQYYcv8m/18-5-quill-fixes-4
It fixes (in a hacky way) the issue that I filed here: slab/quill#783. The decision to fork parchment was made after a lot of consideration - We need to fork Parchment because the handling code for mutations in the DOM is located inside Parchment. There may be a way to fix it in Quill that is more high-level, but after a lot of digging into, I can't figure it out in a reasonable amount of time, and I have simply filed an issue on the main Quill repo. This PR will fix the bug for our product, and should Quill release a bugfix later on, we can point back to the original Parchment.