11 Commits (9654b4dfb122b54b04369fe80a2f9c95811478e8)

Author	SHA1	Message	Date
Gabriel Luong	9654b4dfb1	For #27667 - Remove import-ordering from the list of disabled ktlint rules	2 years ago
mcarare	ffcef5ff2e	For #26844: Fix ktlint issues and remove them from baseline.	2 years ago
MatthewTighe	767d604315	Fixes #26029: Add wallpaper state to AppStore	2 years ago
MatthewTighe	d6952cb2aa	Fixes #25545: wait to draw Pocket until after first frame	2 years ago
Mugurell	1c7e788bae	For #25025 - Use the `PocketStory` supertype ... This prepares extending support from just `PocketRecommendedStory` to `PocketSponsoredStory` also.	2 years ago
mike a	a066dddce9	Closes #24513: add undo snackbar to history group screen	2 years ago
MatthewTighe	dbfd5ffca0	for #24177: sync tabs when home is shown	2 years ago
Jonathan Almeida	f953c5ec94	For #24220 and #24223: Connect GleanPlumb messages with the new tab ui card. ... Co-authored-by: Jonathan Almeida <jalmeida@mozilla.com>	2 years ago
Gabriel Luong	c2e3d251cb	For #24114 - Refactor HomeFragmentState into AppState	2 years ago
Mugurell	bc59ede073	For #22722 - Reacting to the crashed flag ... Whenever the ".crashed" property of the currently displayed TabSessionState -> EngineState is true we will show an in-app crash reporter with the usual close tab / restore tab options and also the option to report all current non-fatal crashes to Mozilla if the setting for sending the crash reports is enabled in app settings. This closely mimics the previous crash reporter UI but there might be some subtle differences stemming from migrating to using a ComposeView. Whenever the ".crashed" property of the currently displayed TabSessionState -> EngineState is false we will set the in-app crash reporter to have a View.GONE visibility effectively removing it from the layout. The functionality for receiving the non-fatal crashes from the AC CrashReporter through an Intent is still kept and these crashes will be persisted in memory until the user closes / restores a tab and so also makes a decision about sending or not these crashes. Currently more tabs can crash following just one since more share the same process and as such there is no way to differentiate between them or link a certain Crash to a certain tab. They will all be acted upon at once from any tab the user chooses to close or restore.	2 years ago
Jonathan Almeida	9cef9357b1	Close #20704: Add AppStore to Components	3 years ago