You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing this extension, I noticed small differences with tags and styles highlighting that could potentially confuse things a bit
(subsections indicate differences in the attached image)
In my opinion, tags is css should be highlighted the same way as in html, not like a normal class (same color as universal selector *)
Countable values like px, rem, % etc. - assigned to a variable in mixins, do not have highlighting
The values assigned to the variable in mixins have the same highlighting as the css properties. I think it should have like a property value - dark orange
fyi: I don't really know if pseudo-classes shouldn't have the same color as normal properties ;)
Some css properties (like filter, mask, content etc.) have the same highlighting as classes
It's possible that a couple of things I've highlighted are features rather than a bugs ;D
Let me know what you think!
The text was updated successfully, but these errors were encountered:
stolar-xyz
changed the title
Improvements with tags and styles highlighting
Improvements in tags and styles highlighting
Mar 20, 2022
While testing this extension, I noticed small differences with tags and styles highlighting that could potentially confuse things a bit
(subsections indicate differences in the attached image)
*
)px
,rem
,%
etc. - assigned to a variable inmixins
, do not have highlightingmixins
have the same highlighting as the css properties. I think it should have like a property value - dark orangepseudo-classes
shouldn't have the same color as normal properties ;)filter
,mask
,content
etc.) have the same highlighting as classesIt's possible that a couple of things I've highlighted are features rather than a bugs ;D
Let me know what you think!
The text was updated successfully, but these errors were encountered: