-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce :user-valid
& :user-invalid
variants
#12370
base: main
Are you sure you want to change the base?
Conversation
It looks like the pseudo elements are not yet added to https://github.com/cssnano/cssnano/blob/master/packages/postcss-merge-rules/src/lib/ensureCompatibility.js, because they are part of the Selectors Level 4 spec. Should I unmerge the rules in the test for now or should we wait for this feature to land until support is added in |
6b4dc07
to
d55fc3f
Compare
d55fc3f
to
9784aaa
Compare
Hey! You might have noticed that I forced pushed to this branch. The reason is because the PR now uses The code is ported as-is, so no API changes of your feature happened while moving it to the new codebase. I also made sure to add you as a co-author because you still deserve all the credit 💪 |
Hi @RobinMalfait! Is it possible to have it in v3, or it will only be available in v4? |
Any updates / timeline on this? Looking forward to these inputs! |
Yes, you can use arbitrary properties: |
9784aaa
to
7bd0851
Compare
Co-authored-by: Robin Malfait <[email protected]>
7bd0851
to
27aa8d6
Compare
(just rebased this PR) |
We use "custom" pseudo-element while waiting for Tailwind support: tailwindlabs/tailwindcss#12370
We use "custom" pseudo-element while waiting for Tailwind support: tailwindlabs/tailwindcss#12370
|
See
Just landed in Chrome, Firefox & Safari: