fix: ensure the pointer-init class is removed when updating the "locked" state #6312
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.
The locking mechanism does not work as expected when unlocking an element.
This is due to the fact that both
pointer-init
andno-pointer
classes are present on the element.When unlocking and then locking the element, we expect the element to remain locked.
This PR ensures that
pointer-init
is removed along with the other classes to avoid conflict.Reproduction in https://app.grapesjs.com/