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
The automatically generated classnames would have lower specificity than inline styles but we could mitigate that by either adding !important to every rule 😱 or asking the user to add an ID of #uninlined somewhere to their project and generating CSS that looks like this:
What if there was a kind of
uninline
project that meant that projects using inline styles could use a component that expected only classes?As an author I write a component like this:
As a user on a project that uses inline styles, I could be doing something like this:
The automatically generated classnames would have lower specificity than inline styles but we could mitigate that by either adding
!important
to every rule 😱 or asking the user to add an ID of#uninlined
somewhere to their project and generating CSS that looks like this:Adding the
#uninlined
id could be optional but if it's mandatory it will mean much fewer specificity surprises down the track.Basically an inline styles to ICSS compiler. Thoughts?
The text was updated successfully, but these errors were encountered: