NOTE: For teams integrating with night mode this message should provide helpful guidance. Compatibility issues in the new night mode will arrive when colors outside the standard palette provided by Codex have been used. We recommend teams make use of Codex design tokens where possible. You can enable night mode locally by installing Minerva and adding $wgMinervaNightMode = [ "base" => true, "loggedin" => true, "amc" => true ]; to LocalSettings.php
NOTE: Where not possible to use Codex tokens make sure to always set a background and color rather than just background and assumption that text will be #333.
NOTE: As a last resort or for OOUI elements you can consider adding the skin-invert class temporarily to the element to trigger a CSS filter. The intention is to remove this later on, so this should only be used by teams/products to buy themselves an extra 3 months to take care of updating their code.
Background & User story
Why are we doing this ticket?
- This ticket will cover secondary menus (navigational elements and other pages within one to two clicks of the article namespace) to appear in night mode
How does it connect to our overall plans? What goal does it link to?
- See task tree
What previous/central documentation exists?
https://www.mediawiki.org/wiki/Reading/Web/Accessibility_for_reading
User story
As a users, I want menus to appear in night mode consistently, so that I am not surprised by many pages appearing in day mode
Requirements
All pages that can be accessed within 2 clicks by a logged in user (AMC disabled) should be handled in night mode.
These pages are:
- diff page
- edit page
- nearby (Codex)
- mobile settings (Codex)
- search page
- contributions (OOUI)
- notifications (OOUI)
- history page (OOUI)
- watchlist (OOUI)
- talk page (OOUI)
- Special:Log (OOUI)
For each of these pages we should either:
- revert entire page to light mode
- adapt the page for night mode.