fixesbrave/brave-browser#23084
Related Chromium change:
https://github.com/chromium/chromium/commit/92c74c166b472ff78318ac1fa3b86f83c0ae2090
[M103] Add missing READING_LIST toggle to Android sync settings
More details on the linked bug. This is only a temporary solution, the
long-term one should be to address crbug.com/1067282, i.e. auto-generate
the UI from the UserSelectableType enum.
Desktop and iOS follow no particular order for the toggles, so this
CL picks something close to the desktop order crbug.com/1326825#c1.
(cherry picked from commit c4ebfbf)
Fixed: 1326825
Change-Id: I185984fc154eb222bf9a09210d2b3face4884bea
Chromium change:
https://github.com/chromium/chromium/commit/ff81de2378f2e5b5842d0b21d2adf75dbaa0ca7f
Feed: add logging for more feed launch cancel cases
* NAVIGATED_AWAY_IN_APP: logged when the user follows a non-feed-content link during the feed launch. For the NTP it is logged from our TabObserver.onPageLoadStarted(); it will need to be done differently for Start Surface since the feed isn't in a tab.
* NAVIGATED_BACK: logged when "back" is pressed causing the feed surface to disappear during feed launch. A later change will log it for NTP and Start.
* NAVIGATED_TO_ANOTHER_TAB: User went to another tab during feed launch. This isn't normally what we mean by "navigate" but the name came from logging in the other Discover surfaces.
The NTP and Start changes in this CL just plumb a TabModelSelector to FeedSurfaceCoordinator. Later CLs will hook up the specific logging described above for each surface.
Bug: 1195940
Chromium change:
https://github.com/chromium/chromium/commit/1b9e3f25fadc72b743c4529e1870453f594b9d86
[TabletGTS] Fix polish toolbar for first relaunch and a11y switcher
Fix polish toolbar for first relaunch and a11y switcher.
-Pass both the fullscreen and non-fullscreen tab switcher toolbar stubs
when the polished tablet GTS is enabled.
-Choose which one to use based on our flag and if the a11y list switcher
is enabled.
(cherry picked from commit 50515c1)
Bug: 1312980, 1317611
Chromium change:
https://github.com/chromium/chromium/commit/254d31968ece2b5bb58984ed2f79ae01d001c9d1
Remove partnercustomizations AppHooks dep and modularize code
* Remove AppHooks dependency for partnercustomizations.
* Move partnercustomizations code to its own module.
* Move test rules to the partnercustomizations module and setup BUILD.
* Move tests to the partnercustomizations module.
Bug: 1291657
Chromium change:
https://github.com/chromium/chromium/commit/5b05dd6d54ca92c8e00ef8ce74f822cd722b8b3f
Cleanup autogranted DSE permissions
Since the work to revert DSE permissions has moved to 100% (cl/412714386)
there is no need to keep the logic that autogrants permissions to the
DSE.
This CL cleans all of the related logic, leaving only the bit that
reverts the autogranted permissions (if they are present) and bits
related to the DSE origin that don't have anything to do with the
permissions specifically (which are still used for the X-Geo) header.
Bug: 1270216
This reverts previous commit:
[Android] Filter warning after bytecode pacthing
With new R8 library there is a warning related to our bytecode patching:
Warning: Missing method void Lg2.d() (referenced from: void Vf2.run())
Without obfuscation it looks like this:
Warning: Missing method void org.chromium.chrome.browser.toolbar.ToolbarManager.$invoke$special$updateButtonStatus() (referenced from: void org.chromium.chrome.browser.toolbar.ToolbarManager$$ExternalSyntheticLambda3.run())
We do change invoke special to invoke virtual for this method and this is expected.
Chromium change:
chromium/chromium@e3db48a
Android: Stop disabling R8's allowaccessmodification -keep semantics
Causes a 5.5kb regression, but brings us closer to stock R8, and will
ensure visibility of test @rule fields are not changed, thus avoiding
bugs like bug 1265431.
Bug: 1265431
samartnik