-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
bug: Fallback background-colors don't use opacity like oklch #2715
Comments
Thank you @kriskratz
for reporting issues. It helps daisyUI a lot 💚
|
This is what I added into my tailwind css to fix it for now: Also I defined I may have missed some stuff... but this is a good starting point. Let me know if there's a better way.
|
What version of daisyUI are you using?
4.4.24
Which browsers are you seeing the problem on?
All old browsers
Reproduction URL
https://arobotcandream.com/wordpress-change-favicon-site-logo-with-full-site-editor-fse-theme/
Describe your issue
Fallback colors can't use opacity the way they are set, so they don't display correctly in older browsers. And the fallback color for code blocks (--fallback-bc) doesn't seem to work at all in Safari v12.5 on my old iPhone 6.
I upgraded to v4.4.24, but it doesn't seem to solve the issue.
Here is an example from the generated CSS. Browsers using fallback colors will see a nearly black background for code blocks, and modern browsers will see that color at 10% opacity. In this case its defined,
--fallback-bc: #1f2937
This is what it looks like with the Light theme:
Would separating the fallback background onto another line work instead? And fallback colors can be defined in rgb instead
--fallback-bc-rgb: 88, 0, 5;
This is what I expect, and using background-color on two lines like that achieves this look for me:
The text was updated successfully, but these errors were encountered: