[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the clarification. I'm not seeing --force-dark-mode work on
the google-chrome deb either. So it doesn't seem to be a snap-specific
problem. Has this ever worked on linux? When searching for "--force-
dark-mode" I'm seeing lots of references to the feature on windows/mac,
not linux.
--
Just to clarify, the --force-dark-mode flag works different from the
#enable-force-dark flag.
--force-dark-mode should instruct the browser to use a dark UI layout,
i.e. menus, omnibar etc.
#enable-force-dark instructs chrome to force a dark mode for websites
using different color inversion
apport information
** Tags added: apport-collected eoan snap wayland-session
** Description changed:
When creating a init file at ~/.chromium-browser.init chromium is
supposed to read flags from there. However these do not work correctly.
What I expected to happen:
Starting
I tested in a bionic VM with the chromium snap, the chromium-browser
deb, and the chrome deb, and none of them showed dark web content when
passing the --force-dark-mode command-line parameter, so it looks like a
consistent behaviour at least.
chrome://flags/#enable-force-dark can be used to
