-
Notifications
You must be signed in to change notification settings - Fork 12
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
Search: Input text is white on white on dark mode #420
Comments
Also having this problem that the search input text is white and not visible in dark mode. |
We don't currently support dark mode by default yet (e.g. it's not possible to set a CSS class to make search modal dark). However, we do have a bunch of @mhilbrunner @rjwills28 If you are not able to make dark mode working properly with the current set of |
Thanks for the reply @humitos - I was able to come up with a workaround for this issue but will also have a look at the |
We're going to start a basic implementation of a dark mode here to start. |
What I mentioned in the meeting is a mix of two patterns. We'd still use variable underneath, but we don't require theme maintainers or users to set all of these variables to achieve a dark mode. @layer defaults {
:root[data-theme="light"],
:root:not([data-theme="dark"]) {
color-scheme: light;
--readthedocs-flyout-background-color: ...;
--readthedocs-notification-background-color: ...;
...
}
:root[data-theme="dark"] {
color-scheme: dark;
--readthedocs-flyout-background-color: ...;
--readthedocs-notification-background-color: ...;
...
}
} Just as an example, this specifies the dark mode as an attribute on Using <meta name="color-scheme" content="dark light" /> For more info: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta/name#color-scheme If |
Search: Input text is white on white on dark mode OS/browsers. It also seems the
--readthedocs-search-color
CSS var isn't actually set for us on https://docs.godotengine.org/en/latest, so this may be an issue on our end?For now, I've disabled the search addon due to #419.
The text was updated successfully, but these errors were encountered: