-
Notifications
You must be signed in to change notification settings - Fork 904
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade from Chromium 119 to Chromium 120. #20434
Conversation
A Storybook has been deployed to preview UI for the latest push |
693be1b
to
fed8d34
Compare
A Storybook has been deployed to preview UI for the latest push |
946645e
to
adc3c71
Compare
A Storybook has been deployed to preview UI for the latest push |
A Storybook has been deployed to preview UI for the latest push |
A Storybook has been deployed to preview UI for the latest push |
6d4036b
to
47b69f2
Compare
A Storybook has been deployed to preview UI for the latest push |
5b36dda
to
18b875a
Compare
A Storybook has been deployed to preview UI for the latest push |
18b875a
to
082ebfd
Compare
A Storybook has been deployed to preview UI for the latest push |
A Storybook has been deployed to preview UI for the latest push |
d2e0dfa
to
107d9d0
Compare
A Storybook has been deployed to preview UI for the latest push |
107d9d0
to
a6a797a
Compare
Another astract function has been added on the delegate class, which needs to be mocked in brave's test. Chromium change: https://chromium.googlesource.com/chromium/src/+/4facaa830da1fbe990de7792a0028ed181d00795 commit 4facaa830da1fbe990de7792a0028ed181d00795 Author: Nan Lin <linnan@chromium.org> Date: Wed Nov 8 21:24:28 2023 +0000 Delay sending cookie deprecation label until onboarding Delay sending the label until onboarding when third-party cookies are actually disabled. Bug: 1500681
A new abstract function has been added to the base class of this mock, and this change adds the mocking for that. Chromium change: https://chromium.googlesource.com/chromium/src/+/6c741e69558bbe9a3adfa1a6e19c029e22078acb commit 6c741e69558bbe9a3adfa1a6e19c029e22078acb Author: Nan Lin <linnan@chromium.org> Date: Fri Nov 10 22:03:15 2023 +0000 Allow attribution reporting debug reports in cookie deprecation experiment Bypass the ar_debug cookie check when the cookie access is disallowed due to third-party cookies blocked by the cookie deprecation experiment. If the user explicitly blocks third-party cookies, it can't be bypassed. Bug: 1501067
Per security/privacy team. Tried nullptr'ing TrackingProtectionOnboardingFactory first, but there's code on Android that doesn't check for nullptr. Instead we override TrackingProtectionOnboarding::MaybeMarkEligible, so it's never set it eligible.
This reverts commit 37f77699e87b23df8e9d46d38a31d298078ca666.
This enum was being extended with a patch, however this a non-controversial case in favour of using an override.
This reverts commit 4e94fe6.
This enum cannot be extended with an override, as it is annotated with `// GENERATED_JAVA_ENUM_PACKAGE`. The extended keys will not be available in the java side without the keys being textually present. This reverts commit 19438f0.
This reverts commit 239fde1.
Patching of crashpad haas had no effect for a long period already, as the specific file being patched is not being built on linux anymore, for little over a year. This change is deleting the patch altogher. Chromium change: https://chromium.googlesource.com/chromium/src/+/b999986ff24699b81ecd3f45254a4bdf0332698a commit b999986ff24699b81ecd3f45254a4bdf0332698a Author: Peter Kasting <pkasting@chromium.org> Date: Wed Oct 25 03:54:27 2023 +0000 Shorten code by using existing helper APIs, eliminating temps. No functional change. Bug: none https://chromium.googlesource.com/chromium/src/+/7c44905e4a83c8c4811867c5bb27d10d8a086b34 commit 7c44905e4a83c8c4811867c5bb27d10d8a086b34 Author: Joshua Peraza <jperaza@chromium.org> Date: Wed Oct 5 22:15:41 2022 +0000 linux: Remove breakpad integration Builds targeting Chrome OS remain runtime switchable between breakpad and crashpad, while Cast OS has only breakpad client integration. Bug: 1176772
This file has been triggering the formatter in M120, possibly due to updates to the toolchain.
kEnableSnippetsByDse preference is only registered when Feed is enabled, however in Chromium they try to set it even when Feed is disabled. Since we don't use Feed in Brave we need to disable this code. Chromium change: https://source.chromium.org/chromium/chromium/src/+/1f4c1c5e28a37e3104c015eb30593d92cb3c516e [DSE] Identify EEA countries In this CL, we expose an API to identify EEA country to Java in TemplateUrlService. Add a parameter and update chrome://flags. Bug: 1475011
Renamed to monochrome_32_64_public_apk for 64-bit platforms. Chromium change: https://source.chromium.org/chromium/chromium/src/+/450c8413b6e16857ebe35eed1f06cdfdd9106596 commit 450c8413b6e16857ebe35eed1f06cdfdd9106596 Author: Sam Maier <smaier@chromium.org> Date: Thu Oct 5 18:32:32 2023 +0000 Relandx2 "Renaming monochrome_public_bundle to m_32_64_p_b for 64-bit builds" This is a reland of commit c58c4142cb5f18148d4e42f98270204bbe5c19f0 Fixed: hardcoded names of more expectations files, and copying the wrapper scripts. Original change's description: > Renaming monochrome_public_bundle to m_32_64_p_b for 64-bit builds > > The goal is to switch the name "monochrome_public_bundle" to build a > 64-bit primary Chrome. This is the first step, where we make > "monochrome_public_bundle" an alias to what it used to be. The next > step will be to change what the alias points to. > > This is also true for all other monochrome and trichrome targets that > default to a 32_64 configuration. > > Bug: 1479998 > Change-Id: I0cfa0a84f79dc9013af72c7d653be4187c65ccda > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4858642 > Reviewed-by: Richard (Torne) Coles <torne@chromium.org> > Commit-Queue: Sam Maier <smaier@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1202715} Bug: 1479998
A Storybook has been deployed to preview UI for the latest push |
Upgrade from Chromium 119 to Chromium 120.
Upgrade from Chromium 119 to Chromium 120.
* Merge pull request #20434 from brave/cr120 Upgrade from Chromium 119 to Chromium 120. * Updated chrome-VERSION.patch from Chromium 119.0.6045.163 to Chromium 120.0.6099.35. * Additional assert_ts.js -> assert.js for 1.61.x. Chromium change: https://chromium.googlesource.com/chromium/src/+/f7a2ea671005530e7a891bba411a34bfd1b3b4cd commit f7a2ea671005530e7a891bba411a34bfd1b3b4cd Author: dpapad <dpapad@chromium.org> Date: Mon Oct 16 21:13:04 2023 +0000 WebUI: Rename assert_ts.ts to assert.ts, part 7 (last) In this part updating one remaining reference in ui/file_manager/ and removing assert_ts.ts. assert_ts.ts used the "_ts" suffix to differentiate from the previously existing assert.js file. The latter no longer exists and the "_ts" suffix can be dropped. Fixed: 1291526 * Remove `SidePanelCoordinator` `final` keyword substitution (#20765) `SidePanelCoordinator` is tagged upstream as `final`, and as a workaround to be able to derive from it, an override had been introduced at some point to replace the keyword `final` with naught. This type of redefinition is unreliable, as it is UB, and it also becomes highly viral. This change replaces the substitution with a patch. The substitution was removing the `final` keyword from the signature of other functions in different headers, and leaving it with no token to indicate the function is an override, causing a build failure. * `Label::CalculatePreferredSize()` marked as `final` (#20767) This function is now marked as `final`, however there is another entry in the overload set that can be used in its place for the override in `BraveVPNStatusLabel`. Chromium change: https://chromium.googlesource.com/chromium/src/+/bf2f84a8c4f27e399e05bf4730a29152f6a8b0b6 commit bf2f84a8c4f27e399e05bf4730a29152f6a8b0b6 Author: weidongliu <liuwd8@gmail.com> Date: Mon Oct 30 15:59:03 2023 +0000 views: Mark CalculatePreferredSize() of views::Label as final Views::Label now has two functions to calculate the preferred size. This can cause some unexpected errors. CalculatePreferredSize() is now expected to be deprecated. Therefore, mark it as final to prevent overrided by subclasses. Bug: 1346889 * Revert "Disable kPowerBookmarksSidePanel feature flag" This reverts commit 237341e. * Java files formatting. * Fix `BraveBrowsingDataRemoverDelegate` substitution (#21034) This override has been missing a matching header since it was introduced, and this has been causing linking to fail in every upstream occurrence of `ChromeBrowsingDataRemoverDelegateFactory::GetForProfile` as the return type in the header was not being replaced accordingly. This changes adds the changes to the header as well, and provides an inclusion `BraveBrowsingDataRemoverDelegate` in the shadow file, to allow the compiler to understand that `BraveBrowsingDataRemoverDelegate*` is pefectly convertible to `ChromeBrowsingDataRemoverDelegate`. * [Android] Move JNI classes to jni_zero namespace * Disabled failing upstream browser tests. * Merge pull request #21152 from brave/maxk-fix-page-info-cookies-separator [cr120 follow-up] Removes an extra separator in cookies page info view. * Merge pull request #21153 from brave/maxk-redirect-on-device-data-to-cookies [cr120 follow-up] Redirect On-device data link to cookies page. * Merge pull request #21166 from brave/maxk-hide-hover-card-image-toggle [cr120 follow-up] Hide Settings->Appearance hover card toggle. * Fixed crash accessing 'send to devices' in share menu via Sync (#21168) Fixes brave/brave-browser#34636 Related Chromium commit: https://source.chromium.org/chromium/chromium/src/+/84ed1f62ecd64bbfc3d2c4775a6e80a6b0e9defb Clean up SendTabToSelfSigninPromo flag Enabled by default in M119 (https://crrev.com/c/4905024), can be cleaned up in M120. Fixed: 1479693, 1295204 Change-Id: Ic778e9c886a5d9391fb5da7510d166952481fe21 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4905343 Reviewed-by: Boris Sazonov <bsazonov@chromium.org> Reviewed-by: Wenyu Fu <wenyufu@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Commit-Queue: Victor Vianna <victorvianna@google.com> Cr-Commit-Position: refs/heads/main@{#1204655} * Merge pull request #21169 from brave/120.0.6099.56_master Upgrade from Chromium 120.0.6099.35 to Chromium 120.0.6099.56. * Updated chrome-VERSION.patch from Chromium 120.0.6099.35 to Chromium 120.0.6099.56. --------- Co-authored-by: cdesouza-chromium <cdesouza@brave.com> Co-authored-by: Emerick Rogul <erogul@brave.com> Co-authored-by: Artem Samoilenko <artem@brave.com> Co-authored-by: AlexeyBarabash <AlexeyBarabash@users.noreply.github.com>
Resolves brave/brave-browser#33471
Submitter Checklist:
QA/Yes
orQA/No
;release-notes/include
orrelease-notes/exclude
;OS/...
) to the associated issuenpm run test -- brave_browser_tests
,npm run test -- brave_unit_tests
wikinpm run lint
,npm run presubmit
wiki,npm run gn_check
,npm run tslint
git rebase master
(if needed)Reviewer Checklist:
gn
After-merge Checklist:
changes has landed on
Test Plan: