Dark mode has become a popular feature for all electronic mediums, from desktops to mobile apps to web. Modern browsers broadly support the preferred-color-scheme @media selector allowing a site to automatically match the user's device preference, and many websites allow a user to forcibly set dark mode, such as the StackExchange family of sites.
However, it can't be done by the themes alone. The backdrop_get_logo() function returns a single graphic without consideration for the light or dark mode. The Backdrop logo, for example, works well with light mode pages, less so with dark mode.
To fully support Dark Mode in Backdrop, the following items would need to be included:
- [ ] Support for light/dark logos and automatic inclusion of the right logo in theme functions.
- [ ] Support in one or more stock themes, in particular Basis and Seven.
- [ ] A system-level, user-overridable setting (similar to timezones) for dark mode allowing for "light", "dark", or "auto" (follow device preference) that modules and themes can use to include the appropriate CSS.
- [ ] CSS cache support that won't send cached dark mode CSS to a light mode user.
- [ ] Color module support
- [ ] Backwards compatibility for themes and modules that have no notion of "dark mode."
- [ ] Update black PNG icons (to SVGs? https://github.com/backdrop/backdrop-issues/issues/364)
See also #3990 and #3991.
Recent comments
well @herb I cannot believe it, but the webform module was there in modules on the disc, but missing in the listed modules, so I delete the module folder, and downloaded it again. Then...
My Webform Worksheets have disappeared
The only thing I can think of is to make sure Webform module is enabled and that the content type that needs to contain the webforms has Webform enabled for it. Edit the content type and make...
My Webform Worksheets have disappeared
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists