bootstrap Most components don't support theme/dark mode theme color changes

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue

Even though the current release is only in alpha, the dark mode/theming support is quite suboptimal and it hurts much more than how much it solves.

Defining default theme colors by default should flow through to dark mode.

Components don't respect theme colors correctly when switching to dark mode. Cards, for example, don't use the theme's CSS variables, they use the color's SCSS variables directly, thus the colors defined in _variables-dark don't even matter. This prevents users from defining a dark mode alternative theme, and further, it prevents users from defining additional themes altogether.

The above, for example, can be attributed to the following compiled CSS:

.text-bg-primary {
    color: #fff!important;
    background-color: RGBA(13,110,253,var(--bs-bg-opacity,1))!important;
}

This comes from _color-bg.scss. These rules should always refer to CSS variables instead of the raw SCSS values so they can be overridden at runtime.

The problem is non-fully systematic and inconsistent. bg-#{$color} and text-#{$color} work correctly. text-bg-#{$color} works incorrectly. link-#{$color} is correct, although link-#{$color}:hover and link-#{$color}:active are incorrect.

Reduced test cases

The issue is visible on the Bootstrap docs page.

What operating system(s) are you seeing the problem on?

Windows

What browser(s) are you seeing the problem on?

Microsoft Edge

What version of Bootstrap are you using?

5.3.0-alpha1

Jan 30 '23 12:01 yugabe

I found the following problems that don't respect the current theme:

Emphasis, subtle and border-subtle are derived from the theme colors themselves. Defining them as SCSS variables only causes problems downstream. Should be calculated and set in CSS vars only.
"Light" and "Dark" don't really make sense in light, dark or whatever themes at all, especially seeing how they can be considered their own themes. I suggest these to be removed altogether from the theme colors.
"Primary" is used pretty consistently as an accent and an active color. Secondary, on the other hand, is used almost interchangeably with shades of gray. "Secondary", thus, shouldn't be available to configure either.
Wherever $primary is referenced for example in CSS rules, it won't respect the current theme. Some very serious culprits here are $component-active-bg: $primary !default; and $focus-ring-color: rgba($primary, $focus-ring-opacity) !default;. These should refer to var(--#{prefix}primary) instead, but it'll cause some additional problems, such as $input-focus-border-color: tint-color($component-active-bg, 50%) !default; - this expects a value at build time to function correctly.

Jan 31 '23 12:01 yugabe

Different, but related I think: setting something like $headings-color doesn't work as expected.

Imagine setting $body-color to, say, $gray-700, and $headings-color to $gray-900. You end up with the wrong heading color in, for example, active list group items:

Card titles seems to escape the problem, but only because a) .card-title has higher specificity than h1, etc., and b) the .card-title color is "wrong" — i.e., the same as $body-color rather than darker:

Setting $card-title-color to $headings-color fixes that, but breaks other things:

If I'm doing things the wrong way, obviously I don't know what the right way is. :-)

This isn't a theming issue per se; all of these examples fall into the "light" theme. But. But it seems like some concept is missing. I can't define one universal headings color when that color will be used on various backgrounds?

It seems like anywhere you can define a color — at least, a text color — you need to be able to define two: one for use on "light" backgrounds, and one for use on "dark" backgrounds. The contrast ratio helper would then choose which one to use. Or something like that.

Feb 17 '23 20:02 michaellenaghan

please sir assign this issue me i want to solve this issue

Mar 01 '23 17:03 sanjaygupta45

@sanjaygupta972004 We don't assign issues in this repository. You can directly create a PR if you can fix this issue.

Mar 01 '23 18:03 julien-deramond

ok sir

Mar 02 '23 13:03 sanjaygupta45

"Light" and "Dark" don't really make sense in light, dark or whatever themes at all, especially seeing how they can be considered their own themes. I suggest these to be removed altogether from the theme colors.

I think I'd prefer them to just swap over. If you design/layout in light mode and use .bg-dark. It'll switch to the .bg-light color in dark mode.

Aug 31 '23 14:08 pau1phi11ips

"Light" and "Dark" don't really make sense in light, dark or whatever themes at all, especially seeing how they can be considered their own themes. I suggest these to be removed altogether from the theme colors.

I think I'd prefer them to just swap over. If you design/layout in light mode and use .bg-dark. It'll switch to the .bg-light color in dark mode.

Dark and light should have the names changed but still exist. Generally speaking light is a slightly different color from the background color and dark is higher contrast from the background color. I'd really like to see them keep some color like those two but name them something more appropriate.