[iOS] Rename directories that have swift files in them
This fixes the swift formatter not running on files that belonged to any of these directories. This also updates a few resource paths that had spaces in them. The only remaining directories with spaces in them are Xcode asset catalogs as these are based on the names of the items in the catalog and dont include source files.
This flag prevents our actor tests from navigating. The same approach is
used in upstream actor navigation tests.
Chromium change:
https://chromium.googlesource.com/chromium/src/+/6c4c09344f079
commit 6c4c09344f079e262dc5ff78d4258325c019b23e
Author: Dylan Cutler <dylancutler@google.com>
Date: Fri Jan 23 11:35:31 2026 -0800
[M145] Enable confirming actor navigations to new origins
The web client's code is set up handle the type of requests Chrome
sends when we enable the "confirm_navigation_to_new_origins" feature
parameter now.
I manually verified on Canary that web client is prepared to handle
Chrome enabling this parameter.
(cherry picked from commit bc3aec3412d432997ff1fcce2263b3af212b56fa)
Bug: 439672418
Fixed: 477987062
This value used to be retrieved through an override,
`GetInvocationSource`, which has not been used in brave. For all calls
of `CreateSession`, this change now passes `nullopt` as the invocation
source.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/240cea47d40e34d36fd6696785f292aa704810df
commit 240cea47d40e34d36fd6696785f292aa704810df
Author: Jason Hu <hujasonx@google.com>
Date: Thu Jan 15 17:25:40 2026 -0800
[context-input] Refactor how source is passed through contextual-tasks
This change makes it so that the contextual search session handle owns
the invocation source param, instead of the composebox subclass
implementation. This allows the source to be passed down the same way
that session entries are - i.e. omnibox/realbox -> contextual-tasks
transition maintains the original source now. This will allow the query
controller to continue to use the correct source param in the
postmessage source field.
Bug: b:475617204
Change-Id: I193a3b4e6fb02b5c06f55ab4e6a3dd5421b1501b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7468141
Commit-Queue: Jason Hu <hujasonx@google.com>
Reviewed-by: Sophie Chang <sophiechang@chromium.org>
Reviewed-by: Christian Xu <christianxu@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1570132}
This reverts commit c49bfe6c4c41cdf188bd9736165033106ee4cb6b.
Reverting because this causes multiple upstream permissions tests to
fail and it's more important to keep those test working than avoiding a
patch.
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/0660eaa52c271c0b9c908ff7cc56f68563a34a7b
commit 0660eaa52c271c0b9c908ff7cc56f68563a34a7b
Author: Dana Fried <dfried@chromium.org>
Date: Fri Dec 19 09:54:31 2025 -0800
[Chrome Next] Remove pre-side-by-side layout now that it's launched
Note that the logic in browser_view_layout_impl_old.cc is also moribund
and is about to be removed (once PiP gets its own layout).
Because of this, and because the old layout manager unit tests assumed a
single layout manager they could manipulate to behave like a tabbed,
app, or popup browser, none of them apply to the new setup and the old
unit tests (which tested the layout manager that isn't being used
anymore) are also removed.
Bug: 424236535
Per review feedback.
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/9d2b3244101ccd0eb8321d3027c648ec4a1b14e2
commit 9d2b3244101ccd0eb8321d3027c648ec4a1b14e2
Author: Dave Tapuska <dtapuska@chromium.org>
Date: Thu Jan 15 07:32:24 2026 -0800
Set timeout from multi source page context fetcher
- Change the result code on CopyFromSurface so we can log a uma histogram
instead of an arbitrary string
- Pass timeout to viz, set the browser side timeout to be 500ms later to
give the IPC enough time.
Bug: b:447589565
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/5eb0161669e4f2e59191d1ac37bea98f551f5108
commit 5eb0161669e4f2e59191d1ac37bea98f551f5108
Author: Hubert Chao <hchao@chromium.org>
Date: Thu Dec 18 09:02:23 2025 -0800
[LNA] Add permission prompt for LNA split permissions
Adding the permission prompt UI for the new LNA split permissions LOCAL_NETWORK and LOOPBACK_NETWORK for both Desktop and Android.
Not done in this CL:
* updated icons
* omnibox chip
* checking the right permissions in StoragePartitionImpl::OnLocalNetworkAccessPermissionRequired
CLs for adding the new permissions:
1. https://crrev.com/c/7225793/: permissions/content settings types
2. https://crrev.com/c/7233078/: content settings and page info UI
3. this CL: permission prompt UI
4. future CL: permission policies
Bug: 465491626
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/562341811ecc226ef52b230a47e404cfa5a7da52
commit 562341811ecc226ef52b230a47e404cfa5a7da52
Author: Calder Kitagawa <ckitagawa@chromium.org>
Date: Fri Jan 9 12:42:35 2026 -0800
[BrowserWindow] Compile browser_window on all android
Compile browser_window (but not extensions windowing) on all Android.
BrowserWindowInterfaces instances are only used for desktop Android
until modifications can be made to their lifecycle to support having
both a regular and incognito tab model by either creating two separate
BWI's per window OR creating one BWI that knows about regular &
incognito mode.
Binary-Size: Enable entire feature
Fixed: 474415203
Change-Id: I563f1f4982db0870b1b53c28775983a63d8c0446
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7418197
Reviewed-by: Theresa Sullivan <twellington@chromium.org>
Commit-Queue: Calder Kitagawa <ckitagawa@chromium.org>
Reviewed-by: Linyu He <linyuh@google.com>
Cr-Commit-Position: refs/heads/main@{#1567145}
As upstream continues to work on rearchitecting the delete browsing data dialog,
we encountered the following warnings when visiting the dialog in cr145:
polymer_bundled.min.js:1 Cannot redefine computed property 'isSyncPaused_'.
polymer_bundled.min.js:1 Cannot redefine computed property 'hasPassphraseError_'.
polymer_bundled.min.js:1 Cannot redefine computed property 'hasOtherSyncError_'.
polymer_bundled.min.js:1 Cannot redefine computed property 'googleSearchHistoryString_'.
This is because we override `properties()` using a spread of the base class
properties, which ends up redefining them.
Remove the spread of base class properties and initialize Brave-specific fields
in the constructor instead. This avoids redeclaring inherited computed
properties, which caused runtime Polymer errors, while keeping TypeScript type
checking happy. The change ensures new instance properties are added safely
without breaking inherited behavior.
Delay initial CrViewManager.switchViews() call until after first render so all
view elements are stamped before switching. This avoids assertion failures
introduced by stricter upstream invariants when views are conditionally stamped
or not yet attached during early lifecycle.
Chromium change:
https://source.chromium.org/chromium/chromium/src/+/e6b2721218aea18372be7c12cfe9879faf5b80a1
commit e6b2721218aea18372be7c12cfe9879faf5b80a1
Author: dpapad <dpapad@chromium.org>
Date: Tue Nov 18 15:22:36 2025 -0800
WebUI: Prevent cr-view-manager events firing when not needed.
When calling switchView() or switchViews() with an already active view,
cr-view-manager was unnecessarily firing 'view-enter-start',
'view-enter-finish', 'view-exit-start', 'view-exit-finish' events, which
in turn caused a bug in Settings where focusBackButton() was called in
SettingsViewMixin when it shouldn't (when searching in <all-sites>).
The cr-view-manager behavior when switching to already active views had
been modified at crrev.com/c/6696849, so this CL effectively restores
the old "early return no-op" behavior.
Fixed: 460732312
Change-Id: If71cd7084a267a52539464f5e3e2a45ba3dc49e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7169474
Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: John Lee <johntlee@chromium.org>
Commit-Queue: John Lee <johntlee@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1546843}
Chromium recently introduced the googlechrome config flag to restrict
remote executions for non-clang compile actions (such as mojo generators)
to only Google's official REAPI setup. This was done because "non google
builds often have issue with enabling remote executions for non-clang
compiles when they use an external REAPI."
However, Brave's RBE infrastructure is fully compatible with these remote
actions and they execute correctly in our setup. By force-enabling the
googlechrome config via -config googlechrome in .sisorc, we restore
remote execution support for mojo and other non-clang build actions in
Brave builds.
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/bc0bd277c9a2fcde9989fbfe981344db0648f0b7
commit bc0bd277c9a2fcde9989fbfe981344db0648f0b7
Author: Junji Watanabe <jwata@google.com>
Date: Thu Jan 8 18:39:35 2026 -0800
siso: Introduce googlechrome config to enable remote executions for non clang compile actions
Non google builds often have issue with enabling remote executions
for non-clang compiles when they use an external REAPI.
To make the transition to Siso smooth, this CL enables remote executions
only for `-config googlechrome` build. backend_config/google.star now
has `googlechrome` as a default flag.
Bug: 424659245, 472063697
Change-Id: I3b39d395f4130b61891ab6b1f46517bde00c8c32
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7409934
Reviewed-by: Fumitoshi Ukai <ukai@google.com>
Commit-Queue: Junji Watanabe <jwata@google.com>
Cr-Commit-Position: refs/heads/main@{#1566686}
https://chromium.googlesource.com/chromium/src/+/5c12bc8f387c732614868975dc0ee7e9b8e25f94
commit 5c12bc8f387c732614868975dc0ee7e9b8e25f94
Author: Fumitoshi Ukai <ukai@google.com>
Date: Fri Jan 9 01:41:57 2026 -0800
siso: enable googlechrome only for Google RBE
external folks may use google.star without setting reapi_address
etc in .gclient custom_vars.
Check reapi_address flag to enable googlechrome config in google.star.
Bug: 424659245, 472892242, 472063697
Change-Id: Ife9337352537c7583439fd684da3924accbd918f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7414509
Auto-Submit: Fumitoshi Ukai <ukai@google.com>
Reviewed-by: Junji Watanabe <jwata@google.com>
Commit-Queue: Fumitoshi Ukai <ukai@google.com>
Cr-Commit-Position: refs/heads/main@{#1566817}
Chromium changes:
https://chromium.googlesource.com/chromium/src/+/199c5793cf76c58e931c834ee9bc36437387bb06
commit 199c5793cf76c58e931c834ee9bc36437387bb06
Author: Wenyu Fu <wenyufu@chromium.org>
Date: Fri Dec 12 16:41:21 2025 -0800
[Icons] Remove btn_toolbar_reload.png and test_ic_refresh_black_24dp
Update `btn_toolbar_reload` as a drawable alias. Since refresh is not
automirrored, create `ic_refresh_24dp_rtl.xml` to keep it mirrored in
RTL locale. This allows us to remove all the png version of
btn_toolbar_reload.
Also remove the test only resource that doesn't seem necessary
test_ic_refresh_black_24dp.xml.
Bug: 465841381
Change-Id: I4d936216bee75a493689f4c3f840178275cadc84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7256663
Commit-Queue: Wenyu Fu <wenyufu@chromium.org>
Reviewed-by: Joel Tan-Aristy <jtanaristy@google.com>
Cr-Commit-Position: refs/heads/main@{#1558360}
Mihai PLESA