cef/patch at 5dc69c6cdbec5a0b405e4a033655b20588bffc34 - cef

History

Marshall Greenblatt 5dc69c6cdb alloy: Remove optimization/prediction service usage (see issue #3352 ) This service is required by the "PermissionOnDeviceNotificationPredictions" feature which is enabled by default in https://crbug.com/1350956. It uses a Google backend service as described at https://go.dev/solutions/google/chrome. This change removes the usage of PredictionBasedPermissionUiSelector, which triggered this dependency, along with related startup complexity that was added to support the optimization/prediction service in the M106 update.		2022-08-25 14:09:20 -04:00
..
patches	alloy: Remove optimization/prediction service usage (see issue #3352 )	2022-08-25 14:09:20 -04:00
README.txt	Use git apply for applying patch files (issue #1825 )	2017-04-27 13:53:32 -04:00
patch.cfg	alloy: Remove optimization/prediction service usage (see issue #3352 )	2022-08-25 14:09:20 -04:00

README.txt

There may be instances where CEF requires changes to the source code for
Chromium, Blink or third-party projects that are either not desired by those
projects or that have not yet been merged into the source code versions of those
projects used by CEF. To address this situation the CEF project adds a patch
capability as part of cef_create_projects[.bat|sh] build step. This patch
capability works as follows:

1. The CEF developer creates one or more patch files containing all required
   code changes and places those patch files in the "patches" subdirectory.
2. The CEF developer adds an entry for each patch file in the "patch.cfg" file.
3. When building CEF from source code the patch files are applied by the
   patcher.py tool via the cef_create_projects[.bat|sh] build step
4. When updating Chromium the patch_updater.py tool is used to update all patch
   files. See https://bitbucket.org/chromiumembedded/cef/wiki/ChromiumUpdate.md
   for more information about the update process.