Bump top site limit under its new name
Fix unresilved conflict
Allow Nimbus to generate code that allows the fork flavors
Drop private browsing page again
Use the new text color name
Point at paged style again
Bring back Sentry so we don't have to change the code that would call it
Note we need to build with app: now for some reason
Also prefix Github build commands
Adapt to settings moving
Parse Iceraven versions
Discover the linter's formatter
Get rid of some Detekt complaints
Handle more weird version strings
Finish README
Stop auto-release changelogs from being too huge
Fix#440 by reattaching settings
The StartupActivityStateProvider uses an imperative implementation,
driven by callbacks, to set the state of the application. This is hard
to follow as you need to understand which callbacks will be called in
which order. For example, to make sense of an implementation like this,
COLD, WARM, AND HOT would likely need to be implemented in separate
ActivityLifecycleCallbacks.
I feel the StartupStateProvider is an improvement because it leverages
the StartupActivityLog to query a linear state for a more understandable
implementation. Furthermore, it seems accessible to write COLD, WARM,
and HOT in the same class because they can all be approached the same
way.
* Issue #18862: Add new addBookmark BookmarksUseCase
* Issue #18862: Add class for state binding features
* Issue #18862: Add delete multiple tabs to tray interactor
* Issue #18862: Add new actions to navigation interactor
* Issue #18862: Enable select mode from main tray menu
* Issue #18862: Add menu when in select mode
* Close#18862: Add multi-select banner to tabs tray
* Close#18862: Add select support for handle UI
We apply various layout changes to the "handle" UI in the tabs tray when
switching modes. It isn't quite clear to my, why we do this, if it's
really needed to meet the end result, and if there is a better way.
For now, we're simplying moving over that logic that we can re-evaluate
at a later time.