-
Notifications
You must be signed in to change notification settings - Fork 57
Dark mode: drop dark variants #2270
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
Dark mode: drop dark variants #2270
Conversation
✅ Deploy Preview for boosted ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| </div> | ||
| </div> | ||
| {{< /example >}} | ||
| Add `data-bs-theme="dark"` to the `.accordion` or any ancestor element to enable a component-specific color mode. [Learn more about our color modes]({{< docsref "/customize/color-modes" >}}). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note for later: we will have to check wether users need to add a background in addition to theme, and if so, mention it there. Same for other components
bb078d6 to
36cb3f0
Compare
36cb3f0 to
70c6f34
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is a first review on what was done, I'll continue to check if nothing was forgotten.
FWIW, for consistency, I'd drop the .dropdown-menu-dark, .navbar-dark and .btn-close-white as well Bootstrap side.
|
|
||
| $mark-padding: 0 .1875em !default; // Boosted mod | ||
| $mark-color: $white !default; // Boosted mod: instead of `$body-color` | ||
| $mark-bg: $black !default; // Boosted mod: instead of `$yellow-100` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Out of PR] We might not need to precise it's a Boosted mod since we are already inside one (since l.719)
|
As dark variants, we might remove as well:
|
Co-authored-by: Louis-Maxime Piton <[email protected]>
Co-authored-by: Louis-Maxime Piton <[email protected]>
Co-authored-by: Louis-Maxime Piton <[email protected]>
louismaximepiton
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two small questions.
Co-authored-by: Louis-Maxime Piton <[email protected]>
Co-authored-by: Louis-Maxime Piton <[email protected]>
louismaximepiton
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👌
Maintaining retro compatibility with dark variants would cause too many issues:
So this PR:
.accordion-dark.dropdown-menu-darkare kept for now since Bootstrap still has it in its documentation. This is also linked to the topics: are headers supposed to usedata-bs-theme="dark"or not. Not in the scope of this PR.button-varianthas its last parameter removed since used only to handle.btn-inverse.btn-inverse.btn-close-whitein the documentation as it is deprecated by Bootstrap but kept it in the code for retro compatibility.navbar-darkinside its DOM... Also linked to the headers, but hope it's gonna work without.navbar-dark. Let's see when we'll develop this component.navbar-darkare kept for now since Bootstrap still has it in its documentation. This is linked to the topic: are headers supposed to usedata-bs-theme="dark"or not. Not in the scope of this PR..btn-close-whitealso still available in Bootstrap