From b855b1f4d3f0024481d7da930ab98f23b7612095 Mon Sep 17 00:00:00 2001
From: uazo <29201891+uazo@users.noreply.github.com>
Date: Tue, 19 May 2026 10:39:44 +0000
Subject: [PATCH] [AUTO][DOC] Generate patches doc for master branch
---
docs/PATCHES.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/PATCHES.md b/docs/PATCHES.md
index 457e5520..37fa89e2 100644
--- a/docs/PATCHES.md
+++ b/docs/PATCHES.md
@@ -74,6 +74,7 @@
|**Disable Accessibility service by default**
Mon, 8 Nov 2021 09:47:23 +0000
File: [Disable-Accessibility-service-by-default.patch](/build/patches/Disable-Accessibility-service-by-default.patch)
Author: uazo
Context:
License: GPL-2.0-or-later ||
|**Disable Android AppRestrictions**
Fri, 5 Jan 2024 17:02:29 +0000
File: [Disable-Android-AppRestrictions.patch](/build/patches/Disable-Android-AppRestrictions.patch)
Author: uazo
Context:
License: GPL-2.0-or-later ||
|**Disable Android Tab Declutter**
Tue, 1 Apr 2025 11:37:52 +0000
File: [Disable-Android-Tab-Declutter.patch](/build/patches/Disable-Android-Tab-Declutter.patch)
Author: uazo
Context:
License: GPL-3.0-only ||
+|**Disable AppRating**
Mon, 18 May 2026 15:44:56 +0000
File: [Disable-AppRating.patch](/build/patches/Disable-AppRating.patch)
Author: uazo
Context:
License: GPL-2.0-or-later |Chromium Android includes an AppRating promo path that can trigger user-facing
review prompts through the Android app-rating integration. The implementation
depends on Google Play Review APIs provided by Google Play Services. Those
dependencies are already excluded by default in this fork through a separate
patch, making the AppRating feature non-functional and unnecessary.
Change:
Remove AppRatingPromoController from the optional promo selection flow and
exclude the app_rating Java and junit targets from the Android build graph.
Privacy/Security Impact:
Removes an unused user-engagement surface and avoids invoking review-related
logic tied to Google Play Services. No browser engine, network, Blink, V8,
storage, or process-isolation behavior is changed.
Notes:
AppRating depends on Google Play Review APIs from Google Play Services.
Since Google Play Services support is already excluded by default through a
separate patch, this change removes the now-unused integration and prevents
accidental reintroduction of the feature.|
|**Disable AsyncDNS by default**
Sat, 26 Mar 2022 16:41:55 +0100
File: [Disable-AsyncDNS-by-default.patch](/build/patches/Disable-AsyncDNS-by-default.patch)
Author: csagan5
Context:
License: GPL-3.0-only |This feature is detrimental to privacy, see also:
* https://bugs.chromium.org/p/chromium/issues/detail?id=805020|
|**Disable BackForwardCache**
Tue, 14 Feb 2023 16:29:12 +0000
File: [Disable-BackForwardCache.patch](/build/patches/Disable-BackForwardCache.patch)
Author: uazo
Context:
License: GPL-2.0-or-later ||
|**Disable CSS blink-feature support**
Mon, 29 Jul 2024 06:48:25 +0000
File: [Disable-CSS-blink-feature-support.patch](/build/patches/Disable-CSS-blink-feature-support.patch)
Author: uazo
Context:
License: GPL-2.0-or-later |the function is not currently exposed to websites but is only allowed for testing.
disabled as it is an potentially advanced fingerprinting mechanism.
also fixed the possibility of using internal selectors for speculation rules.
see https://chromium-review.googlesource.com/c/chromium/src/+/5540782|
@@ -148,6 +149,7 @@
|**Do not use Windows ClearType Text Tuner setting**
Tue, 16 Apr 2024 12:29:29 +0000
File: [Do-not-use-Windows-ClearType-Text-Tuner-setting.patch](/build/patches/Do-not-use-Windows-ClearType-Text-Tuner-setting.patch)
Author: uazo
Context:
License: GPL-2.0-or-later ||
|**DoH improvements**
Sat, 26 Sep 2020 14:23:19 +0100
File: [DoH-improvements.patch](/build/patches/DoH-improvements.patch)
Author: csagan5
Context:
License: GPL-3.0-only |Enable secure mode by default
Always enforce DoH even with inconsistent system DNS configuration|
|**Enable -fwrapv in Clang for non-UBSan builds**
Thu, 22 Dec 2016 07:15:34 -0500
File: [Enable-fwrapv-in-Clang-for-non-UBSan-builds.patch](/build/patches/Enable-fwrapv-in-Clang-for-non-UBSan-builds.patch)
Author: Daniel
Context:
License: GPL-3.0-only |Using -fwrapv (notably only when not using signed integer overflow checking -
since it will override it and result in not performing checks) is just common
sense since it eliminates the chance of security vulnerabilities being
introduced by optimizations based on signed overflow being undefined.
That has happened before, and those optimizations don't even add up to a 0.1%
performance increase for this kind of software. It's not worth having.
The Linux kernel passes -fwrapv and also -fno-strict-aliasing to disable those
dangerous optimizations (since there is so much incorrect code they can break).
In fact, it is easy to point to dozens of known examples of invalid code that
could potentially be broken by those optimizations.
It is not acceptable for projects to be using optimizations that are known to
be broken with a bunch of code in their tree.
They put barely any effort into even fixing the known cases.
Chromium has blacklists for UBSan for 'false positives' (none of which are
actually false positives, but rather "undefined, but not a bug beyond
potentially being broken by optimizations or even code generation without
them") and also for components too full of these bugs for them to currently
want to bother with it. That includes a bunch of signed overflow issues
(there is sadly no detection for aliasing violations, which are fairly common,
but not that common).
Ideally, -fwrapv could be always passed, but unfortunately the way it is
implemented has silly interactions with other switches.
The reason it would still make sense to pass it is because due to their UBSan
blacklists, they get far from full coverage with it, so -fwrapv would still
be better than nothing where it's not being used.
Since -fwrapv makes signed integer overflow well-defined, Clang will disable
the UBSan checks for signed integer overflow, including in the
production-oriented trapping mode used for hardening.
Excerpt from https://github.com/bromite/bromite/issues/226|
+|**Enable Android DevTools Frontend**
Mon, 18 May 2026 14:39:41 +0000
File: [Enable-Android-DevTools-Frontend.patch](/build/patches/Enable-Android-DevTools-Frontend.patch)
Author: uazo
Context:
License: GPL-2.0-or-later |Enable the Android DevTools frontend and remove Android-specific UI
restrictions that prevented access to developer features on phones.|
|**Enable Android Dynamic Performance Framework**
Wed, 23 Aug 2023 13:49:19 +0000
File: [Enable-Android-Dynamic-Performance-Framework.patch](/build/patches/Enable-Android-Dynamic-Performance-Framework.patch)
Author: uazo
Context:
License: GPL-2.0-or-later ||
|**Enable Cert Management UI**
Thu, 16 Jan 2025 09:43:07 +0000
File: [Enable-Cert-Management-UI.patch](/build/patches/Enable-Cert-Management-UI.patch)
Author: uazo
Context:
License: GPL-2.0-or-later |Activates the ui of certificate management in desktop platforms,
disabling the use of system certificates by default (which can be activated from the ui).|
|**Enable Certificate Transparency**
Fri, 10 Jun 2022 14:20:02 +0200
File: [Enable-Certificate-Transparency.patch](/build/patches/Enable-Certificate-Transparency.patch)
Author: csagan5
Context:
License: GPL-3.0-only |Reporting/auditing functionalities are disabled; a flag is exposed.
Add guard to make sure that certificate transparency stays enabled
by default.|