6 Commits (978871c8590373dd2633f0f94e52b9f334f1c949)

Author	SHA1	Message	Date
Gabriel Luong	978871c859	Bug 1848527 - Part 1: Enable OutdatedDocumentation detekt rule in Fenix	8 months ago
rahulsainani	3561733a01	Bug 1837961 - Part 2:Replace usages of ifChanged to distinctUntilChanged	12 months ago
mcarare	3e2738bad6	[fenix] For https://github.com/mozilla-mobile/fenix/issues/25980: Suppress LongParameterList warning. ... Remove issues from baseline.	2 years ago
mcarare	932823c871	[fenix] For https://github.com/mozilla-mobile/fenix/issues/26844: Fix ktlint issues and remove them from baseline.	2 years ago
Mugurell	dc56238b4c	[fenix] For https://github.com/mozilla-mobile/fenix/issues/22722 - Rename CrashReporterFragment to CrashContentView ... Rename in a separate patch for git to not merge this to previous changes and in such think that the the old file was deleted and a new one was created.	2 years ago
Mugurell	bb85952d10	[fenix] For https://github.com/mozilla-mobile/fenix/issues/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