Fix #232#234
Merged
Merged
Conversation
…child dom nodes instead of getting them from the dom
Closed
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.
Fixes issue #232 (Broken functionalities when karax used with grammarly or languagetool (and possibly other extensions))
Switched off the assertions that were triggering (only on release)
Changed the diff procedure to use the stored dom nodes (in vdom) instead of getting them from the dom (where they are now not in the expected order)
Tested on some manual recreations of the issue (inserting new elements before/inbetween/after nodes managed by karax) and on the test suite