-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Lux 5.1.2 h* handling font color inside bg-* #1186
Comments
Hey @ekrichbaum, thanks for the bug report. Bootstrap has similar problems if you apply Another is to use |
I did have the card class applied. card text-white bg-primary to the card itself. Inside card-body there is a simple h2 tag where the color overrides (only on lux). The second stanza above is from other themes and does work as well as removing the color tag specifically from h2. As comparables... Zephyr overrides that color as well but it is still visible with 212529 inside the h2.. Spacelab and Morph use a .card .h2 stanza as you suggested above to inherit color instead of the 2d2d2d set in the .h*. Cerulean overrides it with the stanza above by setting specifically #fff. And most never set the font color inside the h2 tag. Personally, I like the idea of just removing the color of the h2 but that could cause other things I didn't see in my example. The .bg-* override is pretty specific or the .card override. Any of those fix the issue. |
Do you want a second issue raised on Zephyr as a similar thing? It is at least readable in that case. Just not consistent. |
Thanks for the follow-up. I'm pushing a fix for Lux and Zephyr. Can you confirm it works for you. And if you spot the issue in any other themes, please let me know. |
@thomaspark That fixed it. Thanks! |
h2 (for example) is borked inside of elements with bg-primary (for example).
In lux, the h* color is set:
which causes very dark on dark. Several other themes deal with that in:
but others just remove the color specifically from the h* element.
Removing the color attribute fixed my issue. I didn't try adding in the override specific so that may or may not be the cleanest solution.
The text was updated successfully, but these errors were encountered: