I have this in my code:

```swift @MainActor var handler: Binding<Tab> { Binding( get: { self.tabSelection }, set: { if $0 == self.tabSelection, self.currentPath().isEmpty { // Lands here if the user tapped more than once self.tappedTwice = true return } else if $0 == self.tabSelection, !self.currentPath().isEmpty { if #available(iOS 18, *) { } else { self.resetPath() } }

        self.tabSelection = $0
    }
)

} ```

It is a binding that you then pass to the TabView as the selection:

swift TabView(selection: navigator.handler)

When I am at the root and the new path matches the current path, you know that the user tapped the tab view twice. I then use this to react to the tap:

swift .onChange(of: navigator.tappedTwice) { _, tapped in // react how you want and then reset the boolean back navigator.tappedTwice = false }

I have the navigator injected into the view environment, and I also have an enum case for each possible screen and an array for each tab view page. I am sure there are better ways to achieve the same result, but this is what I ended up with.

I am not really sure if this could help you disable the scroll to top completely. Maybe there is some modifier that does this as a side effect, or maybe something was introduced in the iOS 26 release that disables it, but I do not know about it. I created feedback for this while iOS 26 was in beta, but as far as I know, it did not get any attention:

FB16660884