cascade-layers : add support for scope and container at rules
#612
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
…ntainer--unassuming-old-english-sheepdog-d6805b4382
…ntainer--unassuming-old-english-sheepdog-d6805b4382
Antonio-Laguna
approved these changes
Sep 14, 2022
…ntainer--unassuming-old-english-sheepdog-d6805b4382
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.
I think this is the right way to add support for
@scopeand@container.I initially thought it would be complicated to resolve the issue and didn't immediately attempt a fix. But it seems that just adding it them the list of
allowedParentAtRuleswas enough.See : #610
These two at rules no longer affect the layer order.
very low prio as very few people use
@layerand even less will be using it with@containeror@scope