```
android_lint_cache/aars/room-runtime-2.6.1.aar/AndroidManifest.xml:23: Warning: The attribute android:allowBackup is deprecated from Android 12 and higher and may be removed in future versions. Consider adding the attribute android:dataExtractionRules specifying an @xml resource which configures cloud backups and device transfers on Android 12 and higher. [DataExtractionRules]
<application>
^
gen/chrome/android/chrome_public_apk__lint/RESZIPS/obj/brave/build/android/android_brave_strings_grd.resources.zip/values-am/android_brave_strings.xml:837: Warning: The resource R.string.brave_quick_action_search appears to be unused [UnusedResources]
<string name="brave_quick_action_search">"Brave ፈጣን እርምጃ ፍለጋ"</string>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../brave/android/java/brave-res/values/brave_styles.xml:290: Warning: The resource R.style.BottomSheetAnimation appears to be unused [UnusedResources]
<style name="BottomSheetAnimation">
~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../brave/android/java/brave-res/values/brave_styles.xml:295: Warning: The resource R.style.BraveAccountTheme appears to be unused [UnusedResources]
<style name="BraveAccountTheme" parent="Theme.Chromium.Activity.Fullscreen">
~~~~~~~~~~~~~~~~~~~~~~~~
../../brave/android/java/brave-res/values/brave_styles.xml:299: Warning: The resource R.style.BottomSheetActivityTheme appears to be unused [UnusedResources]
<style name="BottomSheetActivityTheme" parent="Theme.Chromium.Activity.FakeTranslucent">
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../../brave/android/java/brave-res/drawable-night-nodpi/ic_quick_action_search_and_bookmark_widget_preview.png: Warning: The resource R.drawable.ic_quick_action_search_and_bookmark_widget_preview appears to be unused [UnusedResources]
../../brave/android/java/brave-res/xml/quick_action_search_and_bookmark_widget_info.xml:7: Warning: The resource R.xml.quick_action_search_and_bookmark_widget_info appears to be unused [UnusedResources]
<appwidget-provider xmlns:android="http://schemas.android.com/apk/res/android"
^
../../chrome/android/java/res_chromium_base/drawable-night/themed_app_icon.xml:6: Warning: The resource R.drawable.themed_app_icon appears to be unused [UnusedResources]
<vector xmlns:android="http://schemas.android.com/apk/res/android"
^
../../brave/android/java/brave-res/drawable-night-nodpi/widget_preview.png: Warning: The resource R.drawable.widget_preview appears to be unused [UnusedResources]
```
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/81de9ffa1dc0a08f75324ada5fe6189a6178bce6
commit 81de9ffa1dc0a08f75324ada5fe6189a6178bce6
Author: Steven Holte <holte@google.com>
Date: Fri Nov 21 13:31:26 2025 -0800
Split on-device vs remote feature keys.
This has the following changes outside of opt-guide:
* Renames optimization_guide::mojom::ModelBasedCapabilityKey
-> mojom::OnDeviceFeature.
* Replaces all use of optimization_guide::ModelBasedCapabilityKey in
conjunction with OnDeviceCapability with mojom::OnDeviceFeature.
And these changes internally to opt-guide code:
* Removes the keys that do not support on-device execution.
* Extracts on-device enum logic to on_device_features.h/cc
* Removes conditional support of kTest and kCompose (neither are
used in any production code, so this gate is unnecessary).
* Return type for GetOptimizationTarget becomes non-optional.
* Use an EnumSet for iterating over all keys.
* Makes the proto->key conversion inferred and return optional type.
Bug: 445999234
Change-Id: I27a4191525a1f7c06b93a75307ca2cdd6a6a6964
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7139721
Auto-Submit: Steven Holte <holte@chromium.org>
Owners-Override: Nico Weber <thakis@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Mike Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1548707}
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/d7fb9d0cd0b6e1589ee974c1ca33de984df513e7
commit d7fb9d0cd0b6e1589ee974c1ca33de984df513e7
Author: Lei Zhang <thestig@chromium.org>
Date: Thu Nov 20 19:40:04 2025 -0800
Reland "Move logging::LoggingSettings to base/logging/logging_settings.h"
This is a reland of commit 6b79baf89a1d87407d4bafdc5d871061a81f80fc
The reland is the same CL. The difference is the problematic code in a
separate repo that did not do IWYU has been fixed.
Original change's description:
> Move logging::LoggingSettings to base/logging/logging_settings.h
>
> Move struct LoggingSettings, which is only used in a relatively small
> number of files, out of base/logging.h and into its own header. Update
> direct users and then do IWYU to fix the build. This effectively moves
> base/files/file_path.h out of base/logging.h.
>
> Change-Id: I04209f1063051b7399e335d7e30cb7abb9442c94
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7160150
> Reviewed-by: Francois Pierre Doray <fdoray@chromium.org>
> Commit-Queue: Lei Zhang <thestig@chromium.org>
> Owners-Override: Francois Pierre Doray <fdoray@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1546655}
Change-Id: Ie877c3c85cc3e1983fb8b2b065b0d09607442ce4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7173024
Owners-Override: Francois Pierre Doray <fdoray@chromium.org>
Reviewed-by: Francois Pierre Doray <fdoray@chromium.org>
Commit-Queue: Francois Pierre Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1548242}
With the deletion of this method, there's now the introduction of
`AlertIndicatorButton::Delegate`, which is supposed to handle
browser-related actions.
This change adjust our customistation for
`kTabMuteIndicatorNotClickable` to now be provided through the delegate.
This has only been implemented for the delegate implementation of
`Tabs`. Another derived delegate class is `VerticalTabView`, but this
one seems to be rather in the early stages of implementation.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/562914734cd0c3858c0deb23b00941c0011ec5b4
commit 562914734cd0c3858c0deb23b00941c0011ec5b4
Author: Charles Meng <charlesmeng@chromium.org>
Date: Mon Nov 24 15:27:45 2025 -0800
[Vertical Tabs] Alert indicator button
In order to share the alert indicator button between horizontal and
vertical tabs, create a common interface ParentTab. Due to inheritance
issues it's hard to know that it is also a views::View, so the DCHECK
that the parent tab is the parent in the view hierarchy is removed, and
the color provider will just be taken from the alert indicator button
because it should be the same one as its parent's.
https://screencast.googleplex.com/cast/NjU0MTEzNzU4OTMwNTM0NHwzMzNlOTQ5Ni1mMg
Fixed: 457525173
Change-Id: I2ef413e4f61d00bff2c4400a6e262e89b0c70125
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7182020
Reviewed-by: Eshwar Stalin <estalin@chromium.org>
Reviewed-by: David Pennington <dpenning@chromium.org>
Commit-Queue: Charles Meng <charlesmeng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1549443}
This squash seems to have been innefective from the beginning, as
`endswith` is not reliable for this check. The new check verifies the
the sentece, and it also adds an expectation for a full-stop at the end,
to avoid a too broader pattern.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/18b3276cdcdfb2b914fbb962a5081bb3d74d261a
commit 18b3276cdcdfb2b914fbb962a5081bb3d74d261a
Author: Konstantin Andrikopoulos <andrikopoulos@google.com>
Date: Thu Nov 20 09:17:59 2025 -0800
[dbsc] Add unexportable keys proxy service
Chrome's DBSC implementation lives in the network process. The lowered
privileges that it has constrain the use of Unexportable Key Service on
certain platforms, like macOS for example.
To support DBSC in macOS we thus need to change how the DBSC has access
to the UKS. Instead of directly using the UKS implementation in the
network process, we will move it to the browser process. And from the
browser service, we will expose a new proxy mojo service which the
network process can use.
This proxy service will implement all the asynchronous methods of the
UKS: key generation, key loading, and signing. However, the UKS also
has some synchronous methods which can't be forwarded to an async mojo
method. To solve this issue, the methods in the mojo service will also
return additional information that can be cached in the network process
and used to implement the synchronous part of the UKS interface.
So for example when creating or generating keys the mojo proxy won't
simply return the new key, but also metadata about what algorithm it is
using.
This CL starts by adding the GenerateKey method, with the rest to follow
in future CLs.
NO_IFTTT=file is added now and IFTTT is misfiring
Bug: 452303497, 443932320, 452300505
Change-Id: I5feb9cd1b71f8ec52c36846a035bc7775ec066c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7075194
Commit-Queue: Konstantin Andrikopoulos <andrikopoulos@google.com>
Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Alex Ilin <alexilin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1547877}
These values were generated using heuristics provided by `gnrt` itself.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/d4c06848b36902e02c7001032b4c72ecc8ab2944
commit d4c06848b36902e02c7001032b4c72ecc8ab2944
Author: Lukasz Anforowicz <lukasza@chromium.org>
Date: Fri Nov 21 14:01:48 2025 -0800
[gnrt] Make `gnrt vendor` infer `allow_unsafe` into `gnrt_config.toml`.
This CL modifies the behavior of `gnrt vendor`, so that it also edits
`//third_party/rust/chromium_crates_io/gnrt_config.toml` to ensure that
each crate explicitly sets `allow_unsafe`. This new, heuristics-based
behavior is meant to streamline the experience of importing Rust crates.
Bug: 460814809
Change-Id: I4192f211cbd11f5c435776f146b1dd96ba5daa18
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7180203
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1548722}
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/9afc53ae9f2e324d23f4417840980f48a66c7a21
Animate compact mode expand/contract
This is accomplished with the transition framework. LBC is notified
right before layout changes corresponding to compact mode state changes
are made, allowing it to capture values at the right time. The location
bar itself and the "+" button are animated.
In order to animate contraction correctly, the Toolbar needs to remain
larger until the animation ends to avoid clipping the LocationBar.
LocationBarEmbedder allows for the toolbar's height to temporarily fixed
without exposing the view directly.
In order to provide consistent notifications re: compact mode state, we
need to create a single source of truth for compactness, extracting the
view binder's control of this property out to the mediator.
Bug: TBD
Change-Id: I40943b27b0e295c6bc83fb9b541d6d2f57396a69
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7171390
Per @fallaciousreasoning, this needs to be disabled for now due to interactions
with Leo. It's not currently easy to fix, as all of Leo is bundled together into
one file which disallows importing individual types as the fix for this would
require. Entered https://github.com/brave/brave-browser/issues/51461 to track
this work.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/0b3a9f2a74923ee00eeb14e67c7646f4957d1750
commit 0b3a9f2a74923ee00eeb14e67c7646f4957d1750
Author: dpapad <dpapad@chromium.org>
Date: Wed Nov 19 11:39:03 2025 -0800
WebUI: Enable @webui-eslint/web-component-missing-deps by default.
Specifically
- Enable the new ESLint check by default for non-Ash build_webui()
targets.
- Disable it explicitly for c/b/r/settings/ and c/b/r/new_tab_page/
temporarily until the check is updated to correctly detect missing deps
in WebUIs that use lazy loading (actively worked and expected to
land in a quick follow-up CL).
All violations have already been fixed in prior CLs, except a few that
slipped and are fixed here.
Bug: 457866803
Change-Id: I8691ce7e9358500fe800d24b4ae5b005fc9685b6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7171069
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Teresa Mao <temao@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1547375}
`BraveSidePanel` has to provide support to an instance of
`SidePanelAnimationCoordinator`, which expected to be accessed by
Chromium.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/a7e0dd051812f4522ffd6c1dcf6aab755f7f4a56https://chromium.googlesource.com/chromium/src/+/0a79d10497ab6b7e9fe859356648a5323159a186
commit a7e0dd051812f4522ffd6c1dcf6aab755f7f4a56
Author: dljames <dljames@chromium.org>
Date: Wed Nov 19 16:53:25 2025 -0800
[TBHSP] Add ShadowOverlay opacity animation for side panel
Defines the shadow overlay opacity animation sequence in
SidePanelAnimationCoordinator. ShadowOverlayView observes this animation
id to correctly update the opacity value of its shadow. This is done to
achieve a specific visual affect requested by UX.
Change-Id: Ieab0907f66d1a4e8eb2b97d5af5215325ef88336
Bug: 445452247
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7163705
Reviewed-by: Eshwar Stalin <estalin@chromium.org>
Commit-Queue: Darryl James <dljames@chromium.org>
Reviewed-by: Caroline Rising <corising@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1547545}
commit 0a79d10497ab6b7e9fe859356648a5323159a186
Author: dljames <dljames@chromium.org>
Date: Mon Nov 17 12:50:48 2025 -0800
[TBHSP] Add animation coordinator for side panel
Add an animation coordinator in the side panel to help coordinate all of
the other animation sequences that should happen when the side panel is
open or closed.
Tests will be added in a subsequent patch due to the size of the
implementation.
Change-Id: I9bb5b6118f1abaf723401d6a7e4e14ee6a2b1ed2
Bug: 445452247
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7139797
Reviewed-by: Eshwar Stalin <estalin@chromium.org>
Commit-Queue: Darryl James <dljames@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1546098}
It is necessary that the `COMMIT_MSG` script does not interfere with
amend commits as keeping their commit message intact is necessary for
squashes to work as expected.
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/42c529f984e74c8bba3b8ced4b9e1d531252ff08
Ensure AIM/NB suggestions are fulfilled with appropriate tools.
Up till now only user-typed text was triggering appropriate
fulfillment. This change ensures that suggest picks do the same:
when the user is in AIM or Image creation mode and interacts with any
of the suggested items, they will be redirected to appropriate tool.
For the lack of a better alternative and insufficient time this change
follows the Desktop implementation: construct the AIM URL from its
Search URL analog.
Screen: http://screen/4azQvKA3MTThdrL.png
Change-Id: I04a85ad65de0aae5edf4979c591748771974b0ce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7164817
This change follows the same approach used by previous supplementable
migrations, and relies on forward declarations as a way to retrieve
references to our types.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/e18ae887f31db52f8a420983be9d3cd23a4366a4
commit e18ae887f31db52f8a420983be9d3cd23a4366a4
Author: Steinar H. Gunderson <sesse@chromium.org>
Date: Tue Nov 18 07:35:26 2025 -0800
Make ExecutionContext not Supplementable.
Part of Supplementable cleanup. Done with a script followed by
human cleanup/review and git cl format.
There is a significant (~10 kB APK) size win, which seems to stem from
the fact that Supplement is no longer taking up all the small offsets
in ExecutionContext (smaller offsets can typically be computed in
fewer bytes of code, depending on the CPU architecture); all the
members have been effectively moved to the end of the object instead
of the very beginning.
Bug: 460165754
Change-Id: I2e22b1861c3419a1694cf9f369766cf9a0015ff9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7157113
Auto-Submit: Steinar H Gunderson <sesse@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Steinar H Gunderson <sesse@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1546535}
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/cb3309d8abc8aceb10bd606ffe66be4edc298645
commit cb3309d8abc8aceb10bd606ffe66be4edc298645
Author: Tiffany Song <tiffanysong@google.com>
Date: Mon Nov 17 08:22:29 2025 -0800
[VL] Add response_code_category to NotifyURLVisited to pass to observers
There are several overrides of HistoryServiceObserver that do not
include 404 navigations, as 404 visits are not currently inserted into
History. 404 visits will soon be inserted when
history::kVisitedLinksOn404 is enabled, and not all of these overrides
will want to include 404 navigations. In order to know if a visit has a
404 result, we want to pass response_code_category through OnURLVisited
and OnURLVisitedWithNavigationId.
This CL also adds a param struct, `VisitedURLInfo`, to store the
parameters for `NotifyURLVisited` and `OnURLVisited` in order to avoid
large CLs like this one if more parameters need to be added.
This CL is part of a larger project to make links `:visited` after a 404
visit, while minimizing disruption to History consumers. Project links:
- Google-internal project doc: go/stop-filtering-history-by-status-code
- Issue tree / work status: https://crbug.com/427225439/dependencies
Fixed: 458096507
Change-Id: I85e201ec046939d987dad7af6683351283e7d67a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7122997
Reviewed-by: Nico Weber <thakis@chromium.org>
Owners-Override: Nico Weber <thakis@chromium.org>
Commit-Queue: Tiffany Song <tiffanysong@google.com>
Reviewed-by: Jérôme Lebel <jlebel@chromium.org>
Reviewed-by: manuk hovanesian <manukh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1545935}
We no longer need this patch disabling `enable_type_aware_eslint_checks` on
Windows as it was only added to avoid hitting the maximum path limit, but that
restriction was removed with https://github.com/brave/brave-core/pull/31800.
This change corrects the forward declaration for `SidePanel` used by
`SidePanelAnimationCoordinator`.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/0a79d10497ab6b7e9fe859356648a5323159a186
commit 0a79d10497ab6b7e9fe859356648a5323159a186
Author: dljames <dljames@chromium.org>
Date: Mon Nov 17 12:50:48 2025 -0800
[TBHSP] Add animation coordinator for side panel
Add an animation coordinator in the side panel to help coordinate all of
the other animation sequences that should happen when the side panel is
open or closed.
Tests will be added in a subsequent patch due to the size of the
implementation.
Change-Id: I9bb5b6118f1abaf723401d6a7e4e14ee6a2b1ed2
Bug: 445452247
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7139797
Reviewed-by: Eshwar Stalin <estalin@chromium.org>
Commit-Queue: Darryl James <dljames@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1546098}
This function now receives a single argument of type `VisitedURLInfo`.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/cb3309d8abc8aceb10bd606ffe66be4edc298645
commit cb3309d8abc8aceb10bd606ffe66be4edc298645
Author: Tiffany Song <tiffanysong@google.com>
Date: Mon Nov 17 08:22:29 2025 -0800
[VL] Add response_code_category to NotifyURLVisited to pass to observers
There are several overrides of HistoryServiceObserver that do not
include 404 navigations, as 404 visits are not currently inserted into
History. 404 visits will soon be inserted when
history::kVisitedLinksOn404 is enabled, and not all of these overrides
will want to include 404 navigations. In order to know if a visit has a
404 result, we want to pass response_code_category through OnURLVisited
and OnURLVisitedWithNavigationId.
This CL also adds a param struct, `VisitedURLInfo`, to store the
parameters for `NotifyURLVisited` and `OnURLVisited` in order to avoid
large CLs like this one if more parameters need to be added.
This CL is part of a larger project to make links `:visited` after a 404
visit, while minimizing disruption to History consumers. Project links:
- Google-internal project doc: go/stop-filtering-history-by-status-code
- Issue tree / work status: https://crbug.com/427225439/dependencies
Fixed: 458096507
Change-Id: I85e201ec046939d987dad7af6683351283e7d67a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7122997
Reviewed-by: Nico Weber <thakis@chromium.org>
Owners-Override: Nico Weber <thakis@chromium.org>
Commit-Queue: Tiffany Song <tiffanysong@google.com>
Reviewed-by: Jérôme Lebel <jlebel@chromium.org>
Reviewed-by: manuk hovanesian <manukh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1545935}
This fix adds the .js files expected by the linter.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/231eecfbd9f7f7723b6ffa7e38e515d456249a96
commit 231eecfbd9f7f7723b6ffa7e38e515d456249a96
Author: dpapad <dpapad@chromium.org>
Date: Fri Nov 14 10:34:35 2025 -0800
WebUI: Implement @webui-eslint/web-component-missing-deps check.
This check finds all child custom elements used in an .html.ts template
file and compares them with the imports appearing in the corresponding
class definition file to find missing dependencies.
Once enabled it will programmatically address a very frequent source of
developer confusion where direct dependencies are not always explicitly
imported, often leading to hard to debug failures in tests.
It will be enabled gradually in follow-up CLs by passing
enable_web_component_missing_deps in build_webui() as violations are
fixed. After that it will be enabled by default.
Bug: 457866803
Change-Id: Ib5cef7d62e910aaccf6ac0814ff5bf3ca35577e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7123208
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: John Lee <johntlee@chromium.org>
Reviewed-by: John Lee <johntlee@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1545093}
These are fixes occasioned by ESLint reports. The patch one in particular now
requires the code to be actually deleted, as commenting out the element still
triggers the linter. However, we don't need this patch at all, so we can safely
remove it here.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/12ba9f2f1e55594485b6f42c298448357e531c51
commit 12ba9f2f1e55594485b6f42c298448357e531c51
Author: dpapad <dpapad@chromium.org>
Date: Thu Nov 13 21:14:25 2025 -0800
WebUI: Turn on more eslint-plugin-lit checks in build_webui().
Specifically turning on the following checks:
- binding-positions
- no-duplicate-template-bindings
- no-invalid-escape-sequences
- no-private-properties
All violations have been fixed in a precursor CL.
Since the checks look for valid HTML code, they need to be applied only
after <if expr> statements have been processed and therefore they are
better suited as a build time ESLint check.
Bug: 457650895
Change-Id: Icc9689c37b2ee13e36983dbc966ddf6fe762536d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7123310
Commit-Queue: Teresa Mao <temao@chromium.org>
Reviewed-by: Teresa Mao <temao@chromium.org>
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1544736}
AlexeyBarabash
