Fix webkit contenteditable span insertion bug #101
Merged
Conversation
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
peyerluk
force-pushed
the
fix-contenteditable-span-insertion
branch
from
61ea986 to
fc145b7
Compare
peyerluk
added a commit
that referenced
this pull request
Apr 17, 2015
…tion Fix webkit contenteditable span insertion bug
Merged
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.
Webkits contenteditable inserts spans when there is a styled node that starts just outside of the selection and is contained in the selection and followed by other textNodes. And this bug only occurs if the selection is at the beginning of the contenteditable.
Chrome Issue:
https://code.google.com/p/chromium/issues/detail?id=335955