-
Notifications
You must be signed in to change notification settings - Fork 883
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 118 to Chromium 119 (1.60.x) #20654
Conversation
A Storybook has been deployed to preview UI for the latest push |
A Storybook has been deployed to preview UI for the latest push |
61f6ae8
to
9c51985
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 |
* Reverted PR#16705 (Sync all history) * Reverted PR#16478 (Display history sync diagnostic info) * Reverted PR#20071 (Disable history sync datatype to fallback to typed urls datatype) * Added overrides for HistoryModelTypeController and HistoryDeleteDirectivesModelTypeController to work when encrypt everything option is on * Add patch to sync history delete directives and history entities together * Added unit test for LowPriorityUserTypes * Enable encryption of history sync entities * Added test for precondition state of history datatype controllers * Modified: clean out HistoryDeleteDirectiveSpecifics::UrlDirective::url field, as it is unencrypted * Added test to ensure we don't send url at HistoryDeleteDirectiveSpecifics::UrlDirective * Modified ModelTypeTest.EncryptableUserTypes test to check History type * Removed 'path_excludes' for the files removed in the current PR --------- Co-authored-by: Darnell Andries <dandries@brave.com>
…ation code (#20598) - Cleanup Brave-Core IOS Chromium_SRC overrides. - Add new cleaner Chromium_SRC overrides and simplify app launch logic.
(Instead, we make sure the static_assert passes here by locally restoring kCoarseResolutionMicroseconds back to its original Chromium value.)
Upstream is changing `MigrateObsoleteProfilePrefs` to take a `PrefService` pointer, rather than `Profile`, as this is more expressive of the data actually being accessed. This change aligns all places where we have procedures similar to `MigrateObsoleteProfilePrefs`, to receive a `PrefService*` instance as well. Chromium change: https://chromium.googlesource.com/chromium/src/+/d848587fe1f19123940de4e4c0cec328bc23001f commit d848587fe1f19123940de4e4c0cec328bc23001f Author: Mikel Astiz <mastiz@chromium.org> Date: Mon Oct 2 09:28:03 2023 +0000 [sync] Remove legacy SyncRequested pref It has been practically unused for some time, and most of it is dead code ever since the feature toggle was cleaned up in https://crrev.com/c/4886256. On Ash, it needs to be migrated to a newly-introduced preference tailored to the actual underlying need, which is being able to remember that the server returned DISABLE_SYNC_ON_CLIENT (i.e. the user reset sync via dashboard). Change-Id: I0239447173b32d7d007ebf733dde23a5de1859e1 Bug: 1443446, 1219990
This changes adds a patch to add brave's own third party crates path to the list of rust paths to be ignored during formatting.
…kmarks Disable kPowerBookmarksSidePanel feature flag
6f9fe95
to
d8e21e4
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 |
Chromium change: https://source.chromium.org/chromium/chromium/src/+/37d04b2089c15cb152a8a559887a7d10c66572be [APS] Update tooltip visibility and remove hover highlight for StatusView - Remove tooltip when StatusIconView is not visible. - remove hover highlight when StatusIconView is not visible(e.g. default engine is not Google). - remove hover highlight when VerboseStatusText is visible(e.g. offline). demo(default engine not Google): https://drive.google.com/file/d/1DPIhHtWN4RnjPvkysyCSfV_gd73ZMjPb/view?usp=sharing demo(offline) https://drive.google.com/file/d/1-1Y_t59i8AcxFv6sLpBE-kG2tsSGoi4s/view?usp=sharing TODO: relocate the logic in StatusView to StatusViewBinder or StatusProperties. Bug: 1476816, 1476802
Upgrade from Chromium 118 to Chromium 119
A Storybook has been deployed to preview UI for the latest push |
1 similar comment
A Storybook has been deployed to preview UI for the latest push |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uplift into 1.60.x
approved 👍
Resolves brave/brave-browser#33274
Uplift from #20314
Uplift from #20396
Resolves brave/brave-browser#33358
Uplift from #20440
Resolves brave/brave-browser#33746
Uplift from #20598
Resolves brave/brave-browser#32876
Uplift from #20329
Resolves brave/brave-browser#33411
Uplift from #20390
Resolves brave/brave-browser#33839
Uplift from #20642
Resolves brave/brave-browser#33886
Uplift from #20664
Resolves brave/brave-browser#33882
Uplift from #20665
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: