allow for more complex selectors in parseSelector#6684
Merged
artf merged 3 commits intoGrapesJS:devfrom Apr 1, 2026
Merged
Conversation
tomekczm
changed the title
artf
approved these changes
Apr 1, 2026
Member
|
Thank you @tomekczm |
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.
this allowes you to have a selector with additional pseudoclasses like :not(.some-class-name) which would previously get interpreted as 2 seperate selectors
main benefit from this change is that if you add :not(.gjs-selected) to all your states in selectorManager, the default one becomes a preview of your component as stateless rather than a life preview, which also fixes a issue where if your component is in dragMode absolute and some state offsets the position, making the dragging glitchy