Despite the fact that dark mode is a popular feature, it is adopted by only a few websites. Google recently introduced a new feature in Chrome that allowed its users to enable a dark theme for any website. The feature named Forced Dark Mode worked regardless of the fact that the site supports explicitly dark mode or not.
The new option forced all websites to use darker tones for the website’s content. For example, if a website has a light theme and it doesn’t support dark mode by default, it will show black text on a white background. However, users had the option to enable a dark theme with the introduction of Forced Dark Mode.
Chrome users had to enable a Chrome flag – Force dark mode for web content to enable the hidden feature. The flag once enabled, showed white text on a dark background. The feature worked by inverting the color to your text to its exact opposite in the browser.
No Option To Enable Forced Dark Mode
If you are planning to use it, unfortunately, the Forced Dark Mode flag is no longer available in the latest version of Chrome Canary. The change was first spotted by a leakster Leopeva64:
“Another “novelty” in Chrome Canary is that the “Force Dark Mode for web contents” flag has disappeared, this could be something temporary.”
However, the feature is currently in the experimental stages. It is possible that this is a temporary change and Google can decide to bring back the flag based on user feedback.
Chrome Canary Update Fixes “Tab hover cards” Bug
Leopeva64 further confirmed that the latest update has fixed a minor bug with Tab hover cards in Google Chrome. The card previously appeared with a small delay when a user moved the pointer over the tab for the first time. However, the card appeared immediately when you quickly hover the pointer over the tab again.
Thankfully the bug has been fixed now. You can observe the changed behavior in the latest Canary update.
The feature is currently in works and no ETA is available at the time of writing this article. If you are one of those who are annoyed by the same issue, you should install Chrome Canary version 80.0.3968.0 to fix it.