For issue #18132 update to proton icons first batch
(cherry picked from commit 21cf0b31a4)
For issue #19290 update to proton icons second batch
(cherry picked from commit 9bfb31519a)
For issue AC#10231 update proton icons third batch
(cherry picked from commit bf42a1786e)
Remove feature flag for proton icons re-design #18132
(cherry picked from commit 52587753a5)
For #19357: Remove bookmarks experiment and keep star-with-line icon.
(cherry picked from commit 93c6403882)
The main cause for this is that the `LifecycleProvider` needs to be set
to `State.RESUMED` to avoid the account manager's internal
`ObserverRegistry` from putting the UI observers into the paused state.
The rest of the changes is to rely the internal (safe) logic to
correctly sync and then update the tabs list.
* For #19005: new tab three-dot menu sync sign in (#19037)
* Show synced tabs or sync account in new tab menu
* Sync sign in item navigates to account settings
* Check account auth and get sync item title
* Look for sync sign in item on home menu for UI test
* Sync sign in menu item UI test
* For #19114: check state of sync account when navigating from sync sign in menu item (#19118)
* For #18591 - Make the navbar sticky in the new menu
* Turn on feature flag for three-dot menu redesign for beta. (#19111)
* For #18591 - Update tests
Some tests trying to "Add to top sites" may fail because of the sticky navbar
now covering that menu item -> scroll the menu up a little.
Some tests that previously were trying to scroll to the bottom of the menu to
interact with navbar options now don't have to. Them trying to interact with
navbar option with the menu opened as collapsed is a good test for the navbar
stickyness.
Co-authored-by: Mugurell <Mugurell@users.noreply.github.com>
When we allow the homescreen to handle undo for the last tab, we no
longer need to handle this ourselves with our own binding.
In the future, we should re-think this logic to be more robust and less
spread out across multiple screens.
The test failed with the rewrite of the code because it violates
one of our assumptions that only one Activity will be started. However,
since it doesn't rely on observed behavior and we made up the events,
it's value is questionable so it seems okay to remove, especially for
the gain of conciseness in the code.
* Remove signed in as string from sync menu item
* Nav to sync account settings on click
For #18806: navigate to settings account page or sign in on clicking menu item.
* Confirm account exists and retrieve item title
* Remove string
For #18857 [Telemetry] Send a Glean event when users change their default browser
For #18855 [Telemetry] Send an event when users open the toolbar menu
For #18851 [Telemetry] Send an event when users click on the "set as default browser" entry in the toolbar menu