fix(android): back navigation#21002
Open
alexjba wants to merge 1 commit into
Open
Conversation
This commit implements back navigation on 3 levels: - popups will close on back (already handled by qt) OR - sections will swipe back from right panels to left panels (handled generally in the portrait layout) OR - the app will move to the previous panel in history (handled in appMain) OR - app will be minimised (handled in appMain) window.onClose will not prevent app close anymore.
Member
Jenkins BuildsClick to see older builds (1)
|
caybro
reviewed
May 22, 2026
Member
caybro
left a comment
There was a problem hiding this comment.
Code LGTM
But what does all this do when we are in landscape layout on a (mobile) device?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does the PR do
This PR should be merged to master after the release cycle. It targets release to avoid unnecessary conflicts
This commit implements back navigation on 3 levels:
OR
OR
OR
window.onClose will not prevent app close anymore.
closes #20940 #20997
Affected areas
app navigation
IOS, Android app close
Quality checklist
My PR is consistent with this document: QML Architecture Guidelines
Screencapture of the functionality
Screen_Recording_20260522_133045_One.UI.Home.mp4
Impact on end user
implements nav
How to test
navigate using back on android
Risk
low