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 reason we got rid of that is because inline could also be on the vertical axis. On top of that, that selector you're adding it's also more specific than the original (which is wrong). It's 0,1,0 vs 0,2,0
But the semantics is wrong, so how does it solves this?
You require users to compile their css twice, and make load the correct file... it is much worse in my opinion then the specificity bump.
Regarding vertical axis, I'm not sure what is the problem with previous implementation...
So compiling twice the css is the recommended way to go? it won't work in meta frameworks like Next.js, Remix since you don't own the build.
Sad, I'll stick to v7, thank you.
What would you want to propose?
In previous version (v7) the css that was generated supports both direction (like it should be with logical properties).
This preserves the same semantics of logical properties, the "same" css code supports both directions.
Starting
v8, it generates only one direction (as specified in the plugin options), this breaks the semantics above.Suggested solution
Maybe it is possible to add an plugin option to generate both direction at once, like it was in
v7Additional context
No response
Validations
Would you like to open a PR for this feature?
The text was updated successfully, but these errors were encountered: