A few classes are being affected by these changes but they are mostly
incosequential overall.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/e0f759f728337f7df2f808ebc2c1eefffab5c5e3
commit e0f759f728337f7df2f808ebc2c1eefffab5c5e3
Author: Athul Iddya <athul@iddya.com>
Date: Thu Apr 16 17:08:08 2026 -0700
Add a native frame view for non-browser widgets on Linux
Introduces NativeFrameViewLinux, a FrameViewLinux subclass that provides
native client-side decorations for non-browser widgets on Linux. This
class is preferred over FrameViewLinux for the GTK UI theme. Its
implementation mirrors BrowserFrameViewLinuxNative, using
WindowFrameProvider for frame decoration and NavButtonProvider for
window control buttons.
NativeFrameViewLayoutLinux similarly extends FrameViewLayoutLinux to
override frame and button layout decisions using WindowFrameProvider and
NavButtonProvider. Shared utilities between NativeFrameViewLinux and
BrowserFrameViewLinuxNative are extracted into frame_view_utils_linux.
WindowFrameProvider and NativeTheme gain options for non-browser frame
rendering: top area height, padding and border APIs, and bottom border
drawing in the top area, to match the appearance of native GTK dialogs.
Bug: 396190939
Cq-Include-Trybots: luci.chromium.try:linux-wayland-mutter-rel,linux-wayland-weston-rel
Change-Id: Iee94d493a1751176c38d793e7efcfe47271bc909
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7615475
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Auto-Submit: Athul Iddya <athul@iddya.com>
Reviewed-by: David Yeung <dayeung@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1616203}
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/a7ea861d95f70515cbddad5ea07b29ba144f5659
commit a7ea861d95f70515cbddad5ea07b29ba144f5659
Author: Foromo Daniel Soromou <koretadaniel@chromium.org>
Date: Thu Apr 30 08:15:42 2026 -0700
Extract browser navigator into a separate build target
NOTE: This change is trivial and do not change any behavior.
Extract the browser navigator code and its associated parameters from
the monolithic `chrome/browser/ui` build target into a dedicated
`chrome/browser/ui/navigator` directory and build configuration.
This refactoring establishes a new standalone build file containing
dedicated source sets for the navigator component. Consequently, the
`browser_navigator_params_headers` source set and related source files
are removed from `chrome/browser/ui/BUILD.gn`.
Numerous build files across the `chrome/browser` directory are updated
to replace the old dependency with the new
`//chrome/browser/ui/navigator` target. This modularization decouples UI
components, streamlines dependency management, and improves overall
build structure.
A follow up CL will move the files under c/b/ui/navigator and rename the
include places.
Bug: none
Change-Id: I65c10afadfb1dc3857a3714cdbce6d06201633ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7803848
Reviewed-by: Dana Fried <dfried@chromium.org>
Reviewed-by: Kaan Alsan <alsan@chromium.org>
Commit-Queue: Foromo Daniel Soromou <koretadaniel@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1623210}
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/46173485057d34f790cbd27eb563ca231f46e121
commit 46173485057d34f790cbd27eb563ca231f46e121
Author: Keigo Oka <oka@google.com>
Date: Wed Apr 29 23:54:16 2026 -0700
Site Search: Implement Starter Packs UX for Android Desktop.
This CL implements the Starter Packs (@bookmarks, @history, etc.) UX for
Android Desktop, focusing on the suggestion list experience while
maintaining existing Android chip behavior.
Key changes:
1. Enabled FeaturedSearchProvider on Android in AutocompleteClassifier.
2. Updated BasicSuggestionProcessor to format starter pack suggestions with
appropriate icons (e.g., star for bookmarks, spark for @gemini) and
combined text (e.g., '@gemini - Ask Gemini').
3. Included GROUP_STARTER_PACK in AndroidNonZPSSection to prevent these
matches from being culled on Android.
4. Passed StarterPackId from C++ to Java in AutocompleteMatch to allow
semantic icon selection in BasicSuggestionProcessor without parsing URLs.
5. Enabled kOmniboxSiteSearch and kStarterPackExpansion by default for Android.
Fixed: 500863504
Change-Id: I507e7666c1b68201d178351f5aea166b8db0be46
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7784849
Reviewed-by: Tomasz Wiszkowski <ender@google.com>
Auto-Submit: Keigo Oka <oka@chromium.org>
Commit-Queue: Keigo Oka <oka@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1622980}
Chromium change:
https://chromium.googlesource.com/chromium/src.git/+/009e12b95d04c
commit 009e12b95d04c14133718b7519809c59370fc1d2
Author: Mike Wittman <wittman@chromium.org>
Date: Thu Apr 23 10:54:06 2026 -0700
[embeddings] Simplify test embedding vector specification
Many of the tests that make use of Embedding specify vectors
of size 768, even though the code under test does not depend on
that size. This change reduces the sizes to 3 and uses literal
initializers where feasible to avoid unnecessary size assumptions
and reduce complexity in the tests.
Bug: 499323089
This change drops the use of `contents_height_side_panel_` in favour of
`toolbar_height_side_panel_`. It all changes our interface for
`SidePanel` to match the changes in upstream for how `SidePanelType` is
passed around.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/32daa3e6986fa59dc7adeca3104b17b0a0b63f63
commit 32daa3e6986fa59dc7adeca3104b17b0a0b63f63
Author: Caroline Rising <corising@chromium.org>
Date: Wed Apr 29 11:37:34 2026 -0700
[Side panel] Make all side panels use the toolbar height side panel view.
This removes usage of the content height side panel view and makes the
toolbar height side panel layout according to the current feature's
SidePanelType. This also removes all no unnecessary uses of
SidePanelType as a param for various side panel accessors.
In a followup we will rename the toolbar height side panel.
Bug: 505775465, 505776523
Change-Id: I5fd80c00064621250619cf4b3c9df326f4bc2ea7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7789262
Commit-Queue: Caroline Rising <corising@chromium.org>
Reviewed-by: Dana Fried <dfried@chromium.org>
Reviewed-by: Eshwar Stalin <estalin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1622601}
The new type is THEMES_ANDROID.
https://chromium.googlesource.com/chromium/src.git/+/0c6882b3
commit 0c6882b3eb6e3c2573c9276999817d8a3e8c6f56
Author: Xinyi Ji <xinyiji@google.com>
Date: Fri Apr 24 06:26:48 2026 -0700
[NTP Customization Sync] Add scaffold for THEMES_ANDROID data type
This CL adds the initial scaffolding for the THEMES_ANDROID data type.
- DataType enumeration entry.
- TODOs for mapping to selectable types.
- Histogram entries.
Bug: 488439751
Chromium change:
https://chromium.googlesource.com/chromium/src.git/+/f370ff5e
commit f370ff5ea61fef0acf8afe8f6e62efd35be2350e
Author: Erik Chen <erikchen@chromium.org>
Date: Tue Apr 28 14:18:20 2026 -0700
Modularize //chrome/browser/profiles
Refactors the `//chrome/browser/profiles` BUILD.gn to introduce a new
`:misc` source_set target and moves profile implementation files (e.g.,
`profile_impl`, `off_the_record_profile_impl`,
`bookmark_model_loaded_observer`, policy handlers, avatar/Gaia/shortcut
helpers) out of the top-level `//chrome/browser` static library into it.
Updates dependents across the tree (UI, tests, prefs, policy, signin,
taskbar, etc.) to depend on `:misc` where needed, and adds
`allow_circular_includes_from` plus `nogncheck` annotations to handle
headers that can't yet be split out. This is a pure build-system
reorganization with no behavioral changes.
misc should eventually be refactored as it contains sources that likely
should not live in the //chrome/browser/profiles directory.
AGENT_GENERATED_CL
Bug: 353332589
This change reduces the use of shadow files for this customisation. In
particular, the replacements required an extra function to be overriden
to correct the replacements in the body of the source.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/d959d50e90e94ec50892c3244c70cbac15e93c55
commit d959d50e90e94ec50892c3244c70cbac15e93c55
Author: Anton Bershanskyi <bershanskyi@gmail.com>
Date: Tue Apr 28 12:47:00 2026 -0700
[Extensions] Move manifest_url_handlers.{h,cc}
Rename extensions/common/manifest_url_handlers.{h,cc} to
extensions/common/manifest_handlers/manifest_url_handlers.{h,cc}.
This commit was generated automatically by the script tool
tools/git/move_source_file.py.
Bug: 324534603
Bypass-Check-License: Files moved, not created.
Change-Id: Ia8c401b4075b0737a38ccd6074177e404c2043f7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7747370
Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Anton Bershanskyi <bershanskyi@gmail.com>
Cr-Commit-Position: refs/heads/main@{#1621973}
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/7d3c16b9bb778a09b643288fe47bae4c1d8e53b7
commit 7d3c16b9bb778a09b643288fe47bae4c1d8e53b7
Author: Jingping Sun <jings@microsoft.com>
Date: Mon Apr 27 10:58:12 2026 -0700
[Unchecked] Enable -Xlint:unchecked for Chromium-owned code
Conditionally append -Xlint:unchecked to the base javac flags only when
options.chromium_code is true. This makes javac fail the build on any
new unchecked-conversion / heap-pollution / raw-type warnings in
Chromium-owned Java code, while leaving synced third-party Java sources
(chromium_code=false; auto-defaulted for third_party/ paths without
org.chromium namespace) compiled silently as before.
Why conditional, not global: Synced third-party Java code under
third_party/{junit,google-truth}/ src/ contains unchecked-warning sites
we cannot fix in chromium code base.
Bug: 358366667
Change-Id: I904b09cd4484098cee3b59e6d4aae94eba8d33ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7790536
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Peter Wen <wnwen@chromium.org>
Commit-Queue: Jingping Sun <jings@microsoft.com>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1621171}
build step: cxx "./obj/components/permissions/permissions/speaker_selection_permission_context.obj"
siso_rule: clang-cl/cxx
stderr:
In file included from ../../components/permissions/contexts/speaker_selection_permission_context.cc:5:
In file included from ../../components/permissions/contexts/speaker_selection_permission_context.h:8:
In file included from ../../components/permissions/content_setting_permission_context_base.h:8:
In file included from ../../brave/chromium_src/components/permissions/permission_context_base.h:9:
../../components/permissions/permission_context_base.h(293,31): error: no class named 'PermissionContextBase' in namespace 'permissions'
293 | friend class ::permissions::PermissionContextBase;
| ~~~~~~~~~~~~~~~^
1 error generated.
Follow up to:
commit 72f140e852
Author: Claudio DeSouza <cdesouza@brave.com>
Date: Wed Oct 11 17:42:49 2023 +0100
`FindBrowserWithWebContents` renamed upstream
This is a simple function rename with no other effects.
Chromium change:
https://chromium.googlesource.com/chromium/src/+/82d9bb0f98d7c88a1b2af2e267cf36125fba17c6
commit 82d9bb0f98d7c88a1b2af2e267cf36125fba17c6
Author: Avi Drissman <avi@chromium.org>
Date: Mon Oct 9 21:05:45 2023 +0000
Rename FindBrowserWithWebContents to FindBrowserWithTab
"WebContents" hasn't been synonymous with "tab" since the content
split. It's confusing to have a function that says it finds a browser
by "web contents" yet only looks at the tabs.
Rename the function so that its name accurately reflects its function.
Bug: none
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/d78abe4e930bc802ef45f8a9a1c5ca2919e6b4bd
commit d78abe4e930bc802ef45f8a9a1c5ca2919e6b4bd
Author: Victor Hugo Vianna Silva <victorvianna@google.com>
Date: Mon Apr 20 05:59:44 2026 -0700
[sync/android] Remove isInitialSyncFeatureSetupComplete()
Along with the corresponding setter and UserActionableError::
{kNeedsSettingsConfirmation,kUnrecoverableError}, which are unreachable
in production code.
OBSOLETE_HISTOGRAMS=Sync setup incomplete and unrecoverable error states were removed on Android, along with their histograms.
NO_IFTTT=UserActionableError values are not obsoleted on all platforms.
Bug: 40066949
Change-Id: I903ee43392dfe960e359404338d7d3f07873f784
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7772435
Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Victor Vianna <victorvianna@google.com>
Cr-Commit-Position: refs/heads/main@{#1617442}
This change reruns the plasters, and adds an update to the call for the
constructor of `DeviceInfo` to pass the newly added argument.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/390ff11a3d7dee78459be3ad5a0f7ca614700bd7
commit 390ff11a3d7dee78459be3ad5a0f7ca614700bd7
Author: Theodore Olsauskas-Warren <sauski@google.com>
Date: Fri Apr 24 12:04:14 2026 -0700
[GLIC] Include experimental_triggering opt-in state in DeviceInfo
A new function which represents the combination of GLIC FRE +
Actuation + Experimental actuation is added to GlicEnabling, and
the value is included in the DeviceInfo FeatureSpecificFields.
Many test call sites which construct a DeviceInfo object are updated,
and given we are updating these sites anyway, the singular default
value for MobilePromoOnDesktopPromoTypeSet in the DeviceInfo
constructor is removed and call sites updated.
Bug: b:505510293
Change-Id: I3943e1eddf83ae6d431cc62b8446876c1bd35105
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7783606
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Theodore Olsauskas-Warren <sauski@google.com>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1620378}
All the code relating to this is gone in upstream, so it is also removed
in Brave.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/4e272219dcf3ae5ed3d110e01741ec2ae07b13f4
commit 4e272219dcf3ae5ed3d110e01741ec2ae07b13f4
Author: Mitsuru Oshima <oshima@chromium.org>
Date: Fri Apr 24 13:19:00 2026 -0700
Remove UseWebUITabStrip(), kUseWebUITabStrip flag
This removes the UseWebUITabStrip function, kUseWebUITabStrip feature
flags and simplifies the surrounding logic since it's no longer used.
There are still other code/files specific to WebUITabStri, and they'll
be removed in separate CLs.
Bug: 421465978
Change-Id: I2278ec267fcd3cc7e5b2006bcafba9ee67525686
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7787148
Reviewed-by: Eshwar Stalin <estalin@chromium.org>
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Reviewed-by: Georg Neis <neis@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1620421}
This PR fixes the plaster for `PageActionPerActionMetricsRecorder`,
which has to use the new `PageActionMetricsRecorder`. This PR also
improves the plaster to disable any `Record` functions in this class, so
we can notified when new ones are added.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/42d106dd97f5729ff8ccf50171f3dc87798d76d8
commit 42d106dd97f5729ff8ccf50171f3dc87798d76d8
Author: Kaan Alsan <alsan@chromium.org>
Date: Fri Apr 24 14:29:50 2026 -0700
Consolidate PageAction Metrics Recording using ScopedMultiSourceObservation
This CL transitions the PageAction metrics recording system from
multiple ScopedObservation-based recorders to a single
PageActionMetricsRecorder using ScopedMultiSourceObservation.
Previously, we had count(page actions) * count(tabs) metrics recorder
objects, which duplicated GURLs and created many individual scoped
observations. This CL improves efficiency by sharing navigation state
across all actions in a tab and reducing the total number of
observations. With local profiling (with debug parameters on), this
saves ~100KB per tab, with 31 page actions enabled.
Key changes:
- Merged per-action and page-level metrics logic into a unified
PageActionMetricsRecorder.
- Updated PageActionModelInterface to include GetActionId() for
identification in the consolidated recorder.
- Refactored PageActionControllerImpl to manage the unified recorder.
- Deleted the redundant PageActionPageMetricsRecorder.
- Updated unit tests and test support classes to align with the new
architecture.
Bug: 384074251
Change-Id: I1aeb2205b4d36de3af68d70404ce459babf1dbef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7790756
Commit-Queue: Kaan Alsan <alsan@chromium.org>
Reviewed-by: Foromo Daniel Soromou <koretadaniel@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1620471}
Otherwise there is an error:
../../brave/chromium_src/components/password_manager/core/browser/password_store_factory_util.cc:18:5: error: unknown type name 'PrefService'
18 | PrefService* prefs) {
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/37a52a3a3a7babdf79058424bae296faa5b4a61e
commit 37a52a3a3a7babdf79058424bae296faa5b4a61e
Author: Victor Hugo Vianna Silva <victorvianna@google.com>
Date: Wed Sep 3 11:17:38 2025 -0700
Unify Create{Profile,Account}PasswordStoreBackend() into 1 function
After recent changes, they are almost the same and can share code.
Also:
- IWYU.
- Emit a TRACE_EVENT for the creation of the account store backend,
not just the profile one.
- Remove IsAccountStore parameter from PasswordStoreAndroidBackend,
it was always IsAccountStore(true)
- Changes in the store factories:
* Reduce vertical space, some of these functions look a lot bigger
than they need to be.
* "ProfilePasswordStore", not "PasswordStore".
* Consistently add DependsOn() for the affiliation service factory.
I think in practice this isn't needed today because the
AffiliatedMatchHelper is destroyed on Shutdown() [1], ahead of the
destructor. But that could easily change. The new code is also
more consistent (before the change, some factories listed the
dependency and others didn't).
[1] https://source.chromium.org/chromium/chromium/src/+/main:components/password_manager/core/browser/password_store/password_store.cc;l=430;drc=391e98eeaee80326c3a9d9e9dd731570dba0981a
Bug: None
Change-Id: Iabccc1284135d8de0e80898da80f0e145cd3a1c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6909469
Commit-Queue: Victor Vianna <victorvianna@google.com>
Reviewed-by: Ioana Pandele <ioanap@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1510417}
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/c66e45550985e3570e1cf181df0ec749ab3d80f6
commit c66e45550985e3570e1cf181df0ec749ab3d80f6
Author: Yanting Yu <yyanting@google.com>
Date: Tue Apr 21 12:43:23 2026 -0700
[LogoRefactor] Branch to LegacyLogoView and introduce feature flag.
This CL branches the current LogoView implementation into LegacyLogoView
to ensure the existing functionality remains intact while we restructure
the new LogoView in the follow up CL.
Changes include:
- Branched LogoView, LogoViewBinder, layout XMLs, and corresponding unit tests into LegacyLogoView equivalents.
- Added the ChromeFeatureList.LOGO_VIEW_REFACTOR feature flag in LogoCoordinator to dynamically switch between inflating the LogoView and the LegacyLogoView.
- Extracted the ClickHandler interface from LogoView into LogoProperties to serve as a shared, domain-specific contract. This cleanly decouples the two views, allowing them to be fully independent while still being driven by the same PropertyModel and LogoMediator.
- Updated new_tab_page_layout.xml to replace the `logo_holder` FrameLayout with ViewStub.
Bug: 492453183
Change-Id: Id0ef80f8acab9c2d15928020eb3688bd9f2afc33
Bypass-Check-License: branched files
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7760153
Commit-Queue: Yanting Yu <yyanting@google.com>
Reviewed-by: Xi Han <hanxi@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1618376}
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/1917c17d0ad2fdc3e994a9aefd254b8db7bbe457
commit 1917c17d0ad2fdc3e994a9aefd254b8db7bbe457
Author: Takashi Toyoshima <toyoshim@chromium.org>
Date: Wed Apr 22 19:42:38 2026 -0700
OOR-CORS: Enforce extra forbidden Sec- header checks
This CL adds a new function ContainsForbiddenSecurityHeader in
header_util to check for unauthorized Sec- headers from renderer.
This function is used in both CorsURLLoaderFactory::IsValidRequest and
CorsURLLoader::FollowRedirect to prevent renderer from injecting or
modifying these headers, while permitting Client Hints and Sec-Purpose.
Change-Id: Ia2923ccbddddba2657d72916a03e657c1785cd85
Bug: 494800494
A new member `engine_count()` serves the same purpose.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/0bd93729174039f678c71990a698215207d985b5
commit 0bd93729174039f678c71990a698215207d985b5
Author: Amelie Schneider <amelies@google.com>
Date: Thu Apr 23 08:29:23 2026 -0700
[Search] Remove unused TemplateURLTableModel functions
The experiment `SearchSettingsUpdate` included a refactoring to stop
using the table model for accessing the template URL service but
accessing it directly through the keyword controller instead. Some
functions are already unused and can be removed, the
TemplateURLTableModel as a whole should be removed once the flag is
launched.
This also excludes KeywordEditorController for Android, since it is not
used there.
Bug: 498543733, 490316630
Change-Id: Ie7ab74e7eece7485c85a678b89a48f1cb15a9a94
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7768616
Reviewed-by: Nicolas Dossou-Gbété <dgn@chromium.org>
Commit-Queue: Amelie Schneider <amelies@google.com>
Cr-Commit-Position: refs/heads/main@{#1619543}
This changes the constructor calls, and this change corrects that. For
the only use of `PermissionDescriptor` in the constructor, a default
constructor is being used because there is no blink value for the
permission name for `RequestType::kBraveOpenAIChat`, so we set that
separately.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/35ad82c9803604df82915104d4d062cd851214f7
commit 35ad82c9803604df82915104d4d062cd851214f7
Author: Antonio Sartori <antoniosartori@chromium.org>
Date: Thu Apr 23 10:37:35 2026 -0700
[permissions] Refactor PermissionRequestData
This CL refactors PermissionRequestData so that it becomes again a
data-only struct (which can be e.g. cloned) by removing the
PermissionResolver member. This allows simplifying
GeolocationPermissionContextAndroid, where we don't need to recreate
fake PermissionRequestData for the callbacks anymore.
The refactoring unfortunately implies adapting all callsites, which
however become more natural as they don't need to instantiate a
PermissionResolver anymore.
R=hempjudith@google.com
Change-Id: Ib7883e9f7cac32ef4039ce3098275ad9018f47d3
Bug: 443898320
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7780845
Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
Reviewed-by: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Judith Hemp <hempjudith@google.com>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1619624}
Claudio DeSouza
