-
Notifications
You must be signed in to change notification settings - Fork 111
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
Wrong CSS generated #185
Comments
Hi, what's your project set up like? Is there Sass processing configured or anything like that? |
It's using tailwind with postcss, using To fix it temporarily, I cloned cargo leptos and added a new config to ignore processing css, so it simply copies the file without any browserquery or anything. |
I don't believe this has anything to do with cargo leptos. Tried a quick test, and tailwindcss doesn't mangle it either. Something is going on with pre-/post-processing in your config, I'd look there. Here's a quick rundown of what I tried:
|
Does #194 fix your issue? EDIT: nevermind, it shouldn't. Regardless, it's lightningcss that converts the names: playground |
Coming back to this, I think this would be the more "standard" css: input[type="checkbox"].btn, input[type="radio"].btn {
width: auto;
-webkit-appearance: none;
-moz-appearance: none;
appearance: none;
} And then when you add :is(input[type="checkbox"], input[type="radio"]).btn {
width: auto;
-webkit-appearance: none;
-moz-appearance: none;
appearance: none;
} Lightningcss parses these correctly. Your version as is works in the browser, but is a bit unusual, the class selector goes after the attribute usually while yours is reversed. |
Thank you for the input @prscoelho |
Closing as this is an issue with lightningcss and not us. Feel free to open an issue there |
I am using a simple css file:
However, when building with
cargo leptos build
, it generates the following css intarget/site/pkg/app.css
:The text was updated successfully, but these errors were encountered: