Do not drop !important
declarations from mixed blocks
#1585
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.
With #1550, handling of
!important
was moved fromalfa-style
toalfa-cascade
.This collided with rule tree creation skipping over blocks with a know selector (physical identity), assuming it would contain the same declarations, since know a (DOM) block with both normal and important declaration would create two (cascade) blocks with the same selector but different importance.
Simply checking importance before skipping the blocks.