ChromeMsgStart is now gone upstream and we really don't care much about
which starter is used as long as we don't have to patch Chromium.
Chromium change:
https://chromium.googlesource.com/chromium/src.git/+/5645a61daa85f327d6301935a40142ceea60c23b
commit 5645a61daa85f327d6301935a40142ceea60c23b
Author: Julie Jeongeun Kim <jkim@igalia.com>
Date: Wed Jan 27 11:16:13 2021 +0000
[printing] Clean up files related to legacy IPCs
This CL cleans up print_messages.{cc,h} and following files
since printing IPC messages have been fully converted to mojo
interfaces.
- components/printing/common/print_messages.cc
- components/printing/common/print_messages.h
- components/printing/common/printing_param_traits.cc
- components/printing/common/printing_param_traits.h
- components/printing/common/printing_param_traits_macros.h
- components/printing/common/printing_param_traits_unittest.cc
Bug: 1008939
This is no longer supported after a period of supporting the old
"whitelist" key along with the new "allowlist" one, but now we
need to migrate for real.
Chromium changes:
https://chromium.googlesource.com/chromium/src.git/+/dc12ff7d11e5de868005e17df701d8b0c3730a1c
commit dc12ff7d11e5de868005e17df701d8b0c3730a1c
Author: Karandeep Bhatia <karandeepb@chromium.org>
Date: Thu Jan 14 14:19:40 2021 +0000
Use auto-generated manifest parsing for import, export manifest keys.
Also
- Remove support for legacy export.whitelist manifest key.
- This also revealed that json_schema_compiler doesn't correctly handle
C++ reserved keywords (like export) correctly in the auto-generated code
since using them directly causes compilation errors. Fix this.
BUG=1113513, 842354
https://chromium.googlesource.com/chromium/src.git/+/9486b056f09a97fb2ba5ebb1b4c00f2dae6630c4
commit 9486b056f09a97fb2ba5ebb1b4c00f2dae6630c4
Author: Devlin Cronin <rdevlin.cronin@chromium.org>
Date: Fri May 18 05:42:04 2018 +0000
[Extensions] Use `allowlist` in SharedModule code
Rename the shared module property to 'allowlist'. The legacy 'whitelist'
key will continue to work until we update any uses of it.
Bug: 842354
It will assumed from now on that all of Brave's own code plus patches
to upstream Chromium will always be built and run as part of a Brave
build, so we can drop these guards and reduce the patching surface.
Note that github.com/brave/brave-browser/wiki/Patching-Chromium should
also be updated to reflect the change implemented in this patch.
Fix https://github.com/brave/brave-browser/issues/12740
Browser will launch window modal dialog at 2nd, 3rd, 4th, 8th and 20th
launching if browser is not a default.
If browser is changed from default to non-default, browser will launch
dialog again with same frequency.
fix https://github.com/brave/brave-browser/issues/12203
sergey