public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Than Ngo <than@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/chromium] epel9-next: Refresh utodarkmode workaround patch
Date: Fri, 07 Aug 2026 16:08:59 GMT	[thread overview]
Message-ID: <178611893948.1.1982196199918858528.rpms-chromium-5866a1f34cc9@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/chromium
Branch : epel9-next
Commit : 5866a1f34cc9a2e059121e0e53524b6be3b916c4
Author : Than Ngo <than@redhat.com>
Date   : 2026-05-06T16:26:05+02:00
Stats  : +15/-27 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/chromium/c/5866a1f34cc9a2e059121e0e53524b6be3b916c4?branch=epel9-next

Log:
Refresh utodarkmode workaround patch

---
diff --git a/chromium-143-autodarkmode-workaround.patch b/chromium-143-autodarkmode-workaround.patch
deleted file mode 100644
index 5bd4f87..0000000
--- a/chromium-143-autodarkmode-workaround.patch
+++ /dev/null
@@ -1,26 +0,0 @@
-Workaround auto darkmode issue, image are not inverted correctly in darkmode
-
-diff -up chromium-143.0.7499.40/third_party/blink/renderer/platform/graphics/dark_mode_image_classifier.cc.than chromium-143.0.7499.40/third_party/blink/renderer/platform/graphics/dark_mode_image_classifier.cc
---- chromium-143.0.7499.40/third_party/blink/renderer/platform/graphics/dark_mode_image_classifier.cc.than	2025-12-09 12:28:52.592092242 +0100
-+++ chromium-143.0.7499.40/third_party/blink/renderer/platform/graphics/dark_mode_image_classifier.cc	2025-12-09 12:42:57.776716951 +0100
-@@ -276,16 +276,20 @@ DarkModeResult DarkModeImageClassifier::
-   float high_color_count_threshold =
-       kHighColorCountThreshold[features.is_colorful];
- 
-+#if 0
-   // Very few colors means it's not a photo, apply the filter.
-   if (features.color_buckets_ratio < low_color_count_threshold)
-     return DarkModeResult::kApplyFilter;
-+#endif
- 
-   // Too many colors means it's probably photorealistic, do not apply it.
-   if (features.color_buckets_ratio > high_color_count_threshold)
-     return DarkModeResult::kDoNotApplyFilter;
- 
-+#if 0
-   // In-between, decision tree cannot give a precise result.
-   return DarkModeResult::kNotClassified;
-+#endif
- }
- 
- }  // namespace blink

diff --git a/chromium-148-autodarkmode-workaround.patch b/chromium-148-autodarkmode-workaround.patch
new file mode 100644
index 0000000..58a2d13
--- /dev/null
+++ b/chromium-148-autodarkmode-workaround.patch
@@ -0,0 +1,14 @@
+Workaround auto darkmode issue, image are not inverted correctly in darkmode
+
+diff -up chromium-148.0.7778.96/third_party/blink/renderer/platform/graphics/dark_mode_image_classifier.cc.me chromium-148.0.7778.96/third_party/blink/renderer/platform/graphics/dark_mode_image_classifier.cc
+--- chromium-148.0.7778.96/third_party/blink/renderer/platform/graphics/dark_mode_image_classifier.cc.me	2026-05-06 16:22:25.906024153 +0200
++++ chromium-148.0.7778.96/third_party/blink/renderer/platform/graphics/dark_mode_image_classifier.cc	2026-05-06 16:22:52.465423557 +0200
+@@ -265,7 +265,7 @@ DarkModeResult DarkModeImageClassifier::
+ 
+   // Very few colors means it's not a photo, apply the filter.
+   if (features.color_buckets_ratio < low_color_count_threshold)
+-    return DarkModeResult::kApplyFilter;
++    return DarkModeResult::kDoNotApplyFilter;
+ 
+   // Too many colors means it's probably photorealistic, do not apply it.
+   if (features.color_buckets_ratio > high_color_count_threshold)

diff --git a/chromium.spec b/chromium.spec
index 5fd46dd..9b66486 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -292,7 +292,7 @@ Patch22: chromium-131-fix-qt-ui.pach
 Patch23: chromium-143-revert-libpng_for_testonly.patch
 
 # Get around the problem of auto darkmode webcontent inverting and making them unreadable
-Patch30: chromium-143-autodarkmode-workaround.patch
+Patch30: chromium-148-autodarkmode-workaround.patch
 
 # disable enterprise_companion_integration_tests due to Unresolved dependencies
 Patch31: chromium-145-disable-enterprise_companion_integration_tests.patch

                 reply	other threads:[~2026-08-07 16:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178611893948.1.1982196199918858528.rpms-chromium-5866a1f34cc9@fedoraproject.org \
    --to=than@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox