Issue: brave/brave-browser#40863
This is the effort to reduce the size of #31939
and only removes already deprecated codes that refers brave dark theme api.
* Remove wallet exstension APIs and replace with WebUI handlers
* Remove typescript definitions which are unused
* Remove the reset of the brave_wallet extension API
* Add test for webui handler changes
Add support for --disable-component-update in all brave components. Use with --allow-brave-component-update to
restore previous behavior for perf and other testing
Add admin policy for Web Discovery (#30023)
* Fix Web Discovery API to account for policy, add Web Discovery test
* Move IsWebDiscoveryEnabled/pref_names to components/web_discovery/common
* Check Web Discovery Native feature before loading extension background page
* Use PrefService ref in IsWebDiscoveryEnabled
* Mark WDP policy as pending development for Android
* Move Web Discovery enabled/disabled via policy prefs to //brave/components/constants
There was a flag from long ago that allowed you to select Crypto Wallets as your wallet. However if you did this, it no longer works. There is no one that can feasibly still be using this wallet because it hasn't worked for many versions
Addressed review comments
Remove references to 21070F3D60711361C1210B870439BE49B5D995F4
21070F3D60711361C1210B870439BE49B5D995F4 is for Ethereum Remote Client which is removed
Remove unused ReinstallAsNonComponent
Remove unused comment IsInstallationExplicitlyAllowed
Remove _permission_features.json because it's an override that only
exists because of CW extension.
Remove unused string braveWalletImportFromLegacy
Use constexpr for kMetamaskExtensionId
Remove need subscription to kDefaultEthereumWallet and OnWalletTypeChanged handler
Remove DISABLED_ImportLegacyWallet
Add Migration for people with CryptoWallets pref
Deprecate and keep CryptoWallets prefs
1
This attribute has been deleted from grit, and isn't recognised anymore.
Chromium change:
https://chromium.googlesource.com/chromium/src/+/96c98d3ae26486007669c1cd00e4da58c85659b3
commit 96c98d3ae26486007669c1cd00e4da58c85659b3
Author: dpapad <dpapad@chromium.org>
Date: Tue Feb 4 16:23:24 2025 -0800
Grit: Remove output_all_resource_defines from list of valid attributes.
All references to this attribute have been removed in previous CLs, both
from public and internal repositories.
Fixed: 389466679
Chromium change:
https://chromium.googlesource.com/chromium/src/+/ec463f3e1ee7b
commit ec463f3e1ee7b6f66b4c71d0dbd772c4c8d07ad2
Author: Devlin Cronin <rdevlin.cronin@chromium.org>
Date: Fri Aug 16 02:24:51 2024 +0000
[Extensions] Add a //chrome/common/extensions build target
Extract out files from //chrome/common/extensions into a separate
build target, //chrome/common/extensions:extensions, instead of having
them shared in //chrome/common:common_lib.
In addition to reducing the monolithic build file in //chrome/common,
this some circular dependencies between //chrome/common resources and
extensions files.
Bug: 356905053
* Content picker: a single JS to inject
* Remove a non-relevant test
* Use asset/source to inline html content
* Remove host from braveShields.addSiteCosmeticFilter
* Remove obsolete async
* Use mode: closed
* Update CSS styles
This change has no functional effects and seems to be only due to
wording choice.
Chromium change:
https://chromium.googlesource.com/chromium/src/+/316185d068318c45f64f36f77bda9f436cf71e23
commit 316185d068318c45f64f36f77bda9f436cf71e23
Author: Tim Judkins <tjudkins@chromium.org>
Date: Wed Mar 27 18:01:56 2024 +0000
[Extensions] Change "blessed" -> "privileged" in extension feature files
This CL finishes up previous work to move to a more understandable
language to describe privileged extension contexts for the extension API
feature system to use "privileged" instead of "blessed".
This changes:
'unblessed_extension' -> 'unprivileged_extension'
'blessed_extension' -> 'privileged_extension'
'blessed_web_page' -> 'privileged_web_page'
No behavior change is expected.
Bug: 40946553
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/6a8c35314cd95efb0d218f03d38af6c5fadb03c9
commit 6a8c35314cd95efb0d218f03d38af6c5fadb03c9
Author: Tim Judkins <tjudkins@chromium.org>
Date: Thu Nov 5 18:02:56 2020 +0000
[Extensions Bindings] Support returns_async in extension schemas
(Based on previous work from https://crrev.com/c/2144684 )
This CL is a starting point for supporting a returns_async parameter in
Extension schemas, which is a step in supporting promise-based APIs. It
adds a new property to the Model in json_schema_compiler, returns_async,
which contains information about what the API function is expected to
return.
returns_async is used instead of Model.callback, and can be created
either from a callback specification or a specific "returns_async"
entry in the schema.
It also modifies the doc generation code to handle this new property,
displaying it as a callback at the end of the schema. This should
result in there being no visible difference to the docs when an API is
rolled over to using returns_async, other than previously required
callbacks being displayed as optional.
In order to do end-to-end tests, this CL also moves over tabs.create,
tabs.duplicate and tabs.query to use the new schema format, thereby
enabling promise support on them.
Bug: 978538
* Extend upstream API features instead of copy-pasting.
* Move runtime.sendMessage patch to script.
* Add missing extension id in the comment.
* Move feature extensions into separate files, add sec-team as owners.
* Support full API feature replacement with "replace!" prefix.
* Validate original files existence.
Refactor ai_chat_tab_helper to platform generic, so that iOS can use the same core code for its APIs.
With this change, iOS is able to supply a web-page, URL, and all of the things Desktop does.
Fix layering violation.
Fix iOS not compiling due to unit tests that include "content".
Renamed from AIChatDriver to ConversationDriver
Upstream is set to deprecated, and delete all occurrences of
`base::StringPiece`, and replace it with `std::string_view`, and
according correspondent types.
This change removes the use of `base::StringPiece`, and of the headers
as well across the Brave codebase.
Kevin Smith