-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
"Auto Dark Mode for Web Contents" not working properly #871
Comments
this bug occurs on the chrome extension store too. |
... FWIW, this bug on is even reproducible in Supermium-v121-r2 (with As a workaround, I myself leave the flag |
@Vangelis66 on heavier sites dark mode extensions like dark reader slows down the loading time and use much more Cpu power. Nothing beats the Chromium integrated dark mode. Using Thorium 126 at the moment. |
…o poor algorithm for determining good candidates for colour changes.
in addition to Sp0kzz - DarkReader has no access to secured and internal pages and elements, so light spots in dark theme will be like high beam @win32ss am i correct that you completely remove filtering from all possible dark modes? right now colors looks more vibrant and very light images not inverted when expected. So i rather suggest add three new dark modes for space-based modes with non-images suffix. I use |
Yes, the image filtering was disabled in 126 R3 (and is the only change that affects non-XP systems in this release) due to the issues with the "smart" filtering. However I will work on improving the dark modes in the future. |
…ow be applied to the renderer process via the dark-mode-settings switch, which also needs the corresponding WebContentsForceDark feature to be enabled. This required the introduction of a hack in feature_list to enable the feature when the switch is present, avoiding the need for the user to use two separate flags to enable and use the feature. Furthermore, several options were duplicates with different labels. Now each option is unique, with the ability to have CIELAB/HSL/RGB-based forced darkening, both with and without selective image modification, as opposed to having duplicates of the CIELAB options.
@win32ss I just updated Supermium and now it's missing the "Enabled with selective inversion of non-image elements". And that's the option that I frequently use. So why it's getting removed unexpectedly? If not then what's the alternative option that I can use? |
@Nvdtn19 long/hardsee about_flags.cc in 837ff97 see the red lines: see the green lines and search for one, similar to one you need. they are in more simple form - list of translation - mode_config pairs, but less readable due to numeric values in your case you wish one, similar to {
{"inversion_method", "cielab_based"},
{"image_behavior", "none"},
{"foreground_lightness_threshold", "150"},
{"background_lightness_threshold", "205"}
} note - mode with key anyway general mode is CIELAB, but simple or selective - relying on former duplicated mode_key, it should be simple so try |
Yes, "Enabled with selected inversion of non-image elements" was a duplicate of "with simple CIELAB-based inversion". Now there are options for CIELAB, HSL and RGB inversion of non-image elements, but also CIELAB, HSL and RGB inversion of non-image elements plus selected images. Before only CIELAB inversion of image elements was available. |
Describe the bug
unlike in previous versions the "Auto Dark Mode for Web Contents" flag is not working properly, instead of only inverting the web elements it's messing up images too.
It doesn't matter if i use "enabled with simple X based inversion" or just "enabled" the images are still being inverted.
OS: WIndows 10
Supermium 126.0.6478.249 (Release)
here's an example from https://clw.kooora.com/
how it should look like (Auto Dark Mode for Web Contents: enabled with simple CIELAB-based inversion) on other chromium browsers:
how it looks on Supermium: (Auto Dark Mode for Web Contents: enabled with simple CIELAB-based inversion)
same thing on other websites like https://www.hltv.org/
The text was updated successfully, but these errors were encountered: