-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Fails to handle CSS variables (breaks Tailwind) #446
Labels
bug
Something isn't working
Comments
lishaduck
added a commit
to PSDTools/psdtools.github.io
that referenced
this issue
Jan 19, 2025
And off of the play CDN. Unfortunately, Fontaine has issues with Tailwind’s generated styles, see unjs/fontaine#446. Also, @tailwindcss/forms is really ugly with our styles. Fixes: #5.
lishaduck
added a commit
to PSDTools/psdtools.github.io
that referenced
this issue
Jan 20, 2025
And off of the play CDN. Unfortunately, Fontaine has issues with Tailwind’s generated styles, see unjs/fontaine#446. Also, @tailwindcss/forms is really ugly with our styles. Fixes: #5.
lishaduck
added a commit
to PSDTools/psdtools.github.io
that referenced
this issue
Jan 20, 2025
And off of the play CDN. Unfortunately, Fontaine has issues with Tailwind’s generated styles, see unjs/fontaine#446. Also, `@tailwindcss/forms` is really ugly with our styles. Fixes: #5.
lishaduck
added a commit
to PSDTools/psdtools.github.io
that referenced
this issue
Jan 21, 2025
And off of the play CDN. Unfortunately, Fontaine has issues with Tailwind’s generated styles, see unjs/fontaine#446. Also, `@tailwindcss/forms` is really ugly with our styles. Fixes: #5.
lishaduck
added a commit
to PSDTools/psdtools.github.io
that referenced
this issue
Jan 21, 2025
And off of the play CDN. Unfortunately, Fontaine has issues with Tailwind’s generated styles, see unjs/fontaine#446. Also, `@tailwindcss/forms` is really ugly with our styles. Fixes: #5.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐛 The bug
The generated CSS has
var(--somefont,
deleted whenfont-family
is set to a css function (which Tailwind does), making the CSS both incorrect and invalid.🛠️ To reproduce
https://stackblitz.com/edit/github-c4h1vdcx-t23wu9nq?file=index.css
🌈 Expected behaviour
It'd properly handle css variables.
ℹ️ Additional context
PostCSS parses this leniently, but it's invalid CSS, which LightningCSS's stricter parser catches.
The text was updated successfully, but these errors were encountered: