New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSS Remedy without specificity #88
Comments
Given that global usage of Internet Explorer is sitting at around 1%, do we really need to worry about it? Old versions of Firefox, Chrome and Safari also don't support |
The IE support was actually mostly because CSS Remedy currently does support it as stated in the README |
Even without IE in mind this pseudo-class is too fresh support-wise to base/migrate entire libraries around. |
Another consideration is cascade layers. Even less well-supported than |
@BassOfBass is it though? 馃 At this point, this couldn't even be improved with If remove dead browsers and consider the browserslist default of >.5%, it doesn't look all that bad |
@Th3S4mur41 |
I'm not saying that As @WesCook mentioned, cascade layers might even be a more flexible solution to reach the same goal. But browser support for that is worse so far. The But this library being supposed to be the base class, reducing the specificity should not have any impact in most cases. So, I'd say that the only downside to this so far would be browser support. |
The major version upgrade would indeed be the only feasible solution. Except the next major version would be "1.0.0" in context of this repo, which would give it a "released" impression, not just a major version up. |
It would be great if every definition in the remedy.css could be enclosed in a
:where()
to remove the specificity.Although the fallback for IE would probably mean duplicating the code with an hack 馃槱
The reason for this issue is the following:
In styles written for e.g. design systems in a way that they can easily be overwritten (e.g. for instance like in open-props from @argyleink) css remedy takes precedence.
Another solution for the problem could also come from Cascade layers, but we're not there yet with the browser support
The text was updated successfully, but these errors were encountered: