[AUTO][DOC] Generate patches doc for master branch (#2441)
[AUTO][DOC] Generate patches doc for master branch
This commit is contained in:
uazo
@@ -94,6 +94,7 @@
|
||||
|**Disable Read Aloud by default** <br><sub><nobr> Wed, 24 Jan 2024 12:19:44 +0000</nobr> <br>File: [Disable-Read-Aloud-by-default.patch](/build/patches/Disable-Read-Aloud-by-default.patch) <br><nobr>Author: uazo</nobr> <br><nobr>Context: </nobr> <br><nobr>License: </nobr> ||
|
||||
|**Disable Real Box** <br><sub><nobr> Sun, 5 Nov 2023 17:59:54 +0000</nobr> <br>File: [Disable-Real-Box.patch](/build/patches/Disable-Real-Box.patch) <br><nobr>Author: uazo</nobr> <br><nobr>Context: </nobr> <br><nobr>License: </nobr> |Real-box is search box in ntp|
|
||||
|**Disable Service and Shared workers on 3P iframe** <br><sub><nobr> Sun, 5 Nov 2023 18:05:19 +0000</nobr> <br>File: [Disable-Service-and-Shared-workers-on-3P-iframe.patch](/build/patches/Disable-Service-and-Shared-workers-on-3P-iframe.patch) <br><nobr>Author: uazo</nobr> <br><nobr>Context: </nobr> <br><nobr>License: GPL-2.0-or-later</nobr> |Disabled by default due https://bugs.chromium.org/p/chromium/issues/detail?id=1147281<br>Workers can be reenabled per top-site-url using "Allow 3P Cookies"<br>("Block 3P Cookies" in ui to off) in site settings|
|
||||
|**Disable Sticky User Activation Across Same Origin Navigation** <br><sub><nobr> Wed, 29 Oct 2025 13:01:41 +0000</nobr> <br>File: [Disable-Sticky-User-Activation-Across-Same-Origin-Navigation.patch](/build/patches/Disable-Sticky-User-Activation-Across-Same-Origin-Navigation.patch) <br><nobr>Author: uazo</nobr> <br><nobr>Context: </nobr> <br><nobr>License: GPL-2.0-or-later</nobr> |Do not retains the user activation status after navigating<br>from one page to another page of the same origin.<br>It is currently not possible to remove activation once it has been granted.|
|
||||
|**Disable TLS resumption** <br><sub><nobr> Thu, 24 Mar 2022 10:08:00 +0000</nobr> <br>File: [Disable-TLS-resumption.patch](/build/patches/Disable-TLS-resumption.patch) <br><nobr>Author: uazo</nobr> <br><nobr>Context: </nobr> <br><nobr>License: GPL-3.0-only</nobr> |Disable resumption feature for all HTTPS and QUIC connections;<br>the feature could be used to track users even without cookies.<br>Sessions are not currently saved to disk in Chromium (although<br>there is support for it) but are long enough to constitute a<br>privacy risk (2h for TLS 1.2 and 7 days for TLS 1.3) if user<br>does not frequently close the browser.<br>Since session information is not kept in the HTTP cache it is<br>not cleared when deleting navigation data (although it is possible<br>to clear it by selecting "passwords").<br>Two new user configurable flags are introduced:<br>* kDisableTLSResumption, active by default<br>* kLogTLSResumption, that would allow to find in logcat reused<br>sessions in lines matching "SSL Log:"<br>See also:<br>* https://arxiv.org/abs/1810.07304|
|
||||
|**Disable UA full version** <br><sub><nobr> Wed, 16 Feb 2022 14:28:58 +0000</nobr> <br>File: [Disable-UA-full-version.patch](/build/patches/Disable-UA-full-version.patch) <br><nobr>Author: uazo</nobr> <br><nobr>Context: </nobr> <br><nobr>License: GPL-3.0-only</nobr> |getHighEntropyValues will return only the major version|
|
||||
|**Disable Viewport Segments** <br><sub><nobr> Sat, 28 Jun 2025 08:17:07 +0000</nobr> <br>File: [Disable-Viewport-Segments.patch](/build/patches/Disable-Viewport-Segments.patch) <br><nobr>Author: uazo</nobr> <br><nobr>Context: </nobr> <br><nobr>License: GPL-2.0-or-later</nobr> |Disable Viewport Segments API, specifically for foldable devices,<br>since it exposes the geometry of the fold.|
|
||||
@@ -268,6 +269,7 @@
|
||||
|**Temp disable experimental-web-platform-features** <br><sub><nobr> Mon, 2 Sep 2024 07:05:25 +0000</nobr> <br>File: [Temp-disable-experimental-web-platform-features.patch](/build/patches/Temp-disable-experimental-web-platform-features.patch) <br><nobr>Author: uazo</nobr> <br><nobr>Context: </nobr> <br><nobr>License: </nobr> ||
|
||||
|**Temp disable predictive back gesture** <br><sub><nobr> Sat, 12 Aug 2023 14:48:57 +0000</nobr> <br>File: [Temp-disable-predictive-back-gesture.patch](/build/patches/Temp-disable-predictive-back-gesture.patch) <br><nobr>Author: uazo</nobr> <br><nobr>Context: </nobr> <br><nobr>License: GPL-2.0-or-later</nobr> ||
|
||||
|**Temp guard FileSystemAccessPersistentPermissions** <br><sub><nobr> Sun, 29 Oct 2023 15:18:24 +0000</nobr> <br>File: [Temp-guard-FileSystemAccessPersistentPermissions.patch](/build/patches/Temp-guard-FileSystemAccessPersistentPermissions.patch) <br><nobr>Author: uazo</nobr> <br><nobr>Context: </nobr> <br><nobr>License: </nobr> ||
|
||||
|**Temp use PREVIEW for IDCompositionDevice5** <br><sub><nobr> Wed, 29 Oct 2025 12:30:49 +0000</nobr> <br>File: [Temp-use-PREVIEW-for-IDCompositionDevice5.patch](/build/patches/Temp-use-PREVIEW-for-IDCompositionDevice5.patch) <br><nobr>Author: uazo</nobr> <br><nobr>Context: </nobr> <br><nobr>License: GPL-2.0-or-later</nobr> |Temporarily restore the statement from v141 while waiting to update the Windows SDK.<br>See Remove preview usage of DynamicTexture DComp APIs.<br>https://chromium-review.googlesource.com/c/chromium/src/+/6902339|
|
||||
|**Timezone customization** <br><sub><nobr> Wed, 30 Sep 2020 07:40:01 +0000</nobr> <br>File: [Timezone-customization.patch](/build/patches/Timezone-customization.patch) <br><nobr>Author: uazo</nobr> <br><nobr>Context: </nobr> <br><nobr>License: GPL-3.0-only</nobr> |Allow specifying a custom timezone, or using a random one.<br>See also: https://github.com/bromite/bromite/wiki/TimezoneOverride<br>Require: Content-settings-infrastructure.patch|
|
||||
|**Try to fix 2082** <br><sub><nobr> Thu, 15 May 2025 06:55:56 +0000</nobr> <br>File: [Try-to-fix-2082.patch](/build/patches/Try-to-fix-2082.patch) <br><nobr>Author: uazo</nobr> <br><nobr>Context: </nobr> <br><nobr>License: </nobr> ||
|
||||
|**Use 64-bit WebView processes** <br><sub><nobr> Thu, 26 Jan 2017 01:30:12 -0500</nobr> <br>File: [Use-64-bit-WebView-processes.patch](/build/patches/Use-64-bit-WebView-processes.patch) <br><nobr>Author: Daniel</nobr> <br><nobr>Context: </nobr> <br><nobr>License: GPL-3.0-only</nobr> |64-bit processes introduce 10% or so higher memory consumption.<br>The reason for preferring 64-bit processes is providing substantially better<br>exploit mitigations at the expense of slightly more memory usage.<br>In addition to the standard mitigations, it also enables usage of<br>https://github.com/AndroidHardening/hardened_malloc (where available).<br>It will provide high entropy ASLR (24-bit to 32-bit depending on whether the<br>kernel uses 3 or 4 level page tables rather than 16-bit for 32-bit processes),<br>high entropy stack canaries (56/64-bit instead of 24/32-bit depending on<br>whether a zero byte is used) and also features like pointer authentication and<br>memory tagging when those are made available in the future.<br>The reason why upstream started preferring 32-bit processes is to save memory,<br>particularly since saving memory makes it feasible to use finer-grained<br>sandboxing.|
|
||||
|
||||
Reference in New Issue
Block a user