-
Notifications
You must be signed in to change notification settings - Fork 1.9k
OnNavigating wrong target when tapping the same tab #25599
Copy link
Copy link
Labels
area-navigationNavigationPageNavigationPagepartner/syncfusionIssues / PR's with Syncfusion collaborationIssues / PR's with Syncfusion collaborationplatform/ioss/triagedIssue has been reviewedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering TriageVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't workingSomething isn't working
Milestone
Metadata
Metadata
Assignees
Labels
area-navigationNavigationPageNavigationPagepartner/syncfusionIssues / PR's with Syncfusion collaborationIssues / PR's with Syncfusion collaborationplatform/ioss/triagedIssue has been reviewedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering TriageVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
Done
Description
Let's say we have a tab bar with MainPage and SettingsPage. We are on MainPage and pushed DetailsPage on the navigation stack. We tap the MainPage tab again and we're back to MainPage from DetailsPage.
This is ok, but the problem is we don't get any indication of that in the AppShell's OnNavigating event, so we cannot prevent this with e.Cancel (e.g. when the user has some unsaved changes on the DetailsPage or something):
The
CurrentandTargetproperties are the same inOnNavigating, but inOnNavigatedthePreviousandCurrentare different.Code: TabBarNavigation from this repo: https://github.com/lszl84/maui-scroll-bug.git
Steps to Reproduce
Link to public reproduction project repository
https://github.com/lszl84/maui-scroll-bug.git
Version with bug
8.0.82 SR8.2
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
No response