UserInteractionOnBackPressedCallback handler should break its loop when the event is handled true
Categories
(Firefox for Android :: Homepage, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox137 | --- | verified |
People
(Reporter: bob+bmo, Assigned: bob+bmo)
References
Details
Attachments
(1 file)
Bug 1921125 updated back handling to use new AndroidX APIs and also extracted some handling from HomeActivity into UserInteractionOnBackPressedCallback. In the process, it looks like the original early return from the loop calling fragments/handlers was dropped, resulting in all fragments being called even if an earlier one handled the event already. The doc-comment on UserInteractionHandler.onBackPressed also suggests the old early-break behaviour was correct.
I can't find any visible breakage from this change; in all my tests only a single fragment exists so there's never more than one loop iteration. Still seems like it'd be a good idea to either match old behaviour and doc-comment or at least adjust the comment to accurately describe new behaviour.
Updated•10 months ago
|
Comment 3•10 months ago
|
||
| bugherder | ||
Comment 4•9 months ago
•
|
||
@ QA: We refactored the code and need help validating that nothing changed in back handling on Android 14+ - navigating between screens / closing features like the qr scanner / find in page, etc. Thank you!
Comment 5•9 months ago
|
||
Verified on the latest Fenix nightly 137.0a1 with a Google Pixel 6 (Android 15), and a Samsung Galaxy S24 (Android 14), that nothing changed in back-handling.
Description
•