Fix regression on x-ignore when removed #4458
Merged
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.
Release v3.14.4 introduce an _x_marker property to flag elements that were already initialised so they don't get initialised again when moved around (I think it was causing some issues in Livewire). However the code was also marking as initialised elements that were skipped by x-ignore.
This causes issues if x-ignore is removed and people calls initTree on the element: the subtree is initialised but the parent is skipped even if it wasn't previously initialised so, if it has x-data, it will trigger errors.
See #4457
This PR changes the logic so _x_marker is not added when the element has x-ignore