Scrolling bounds are totally busted when using `Navigation Stack + Pager TabView + Plain List`
Open
Nobody has claimed this yet.
compose
layout
navigation
- Dominant language
- Swift
- Stars
- 330
- Forks
- 76
- Avg merge
- 3h 6m
- Merged PRs (30d)
- 1
Description
Scrolling bounds are totally busted when using Navigation Stack + Pager TabView + Plain List
https://github.com/user-attachments/assets/f38b1a15-4f46-4710-813a-13741c0e2abe
struct ContentView: View {
var body: some View {
NavigationStack {
NavigationLink("plain list inside page tab view") {
TabView {
List {
Section {
ForEach(0..<30, id: \.self) { index in
Text("Row \(index)")
}
}
}
.listStyle(.plain)
}
.tabViewStyle(.page(indexDisplayMode: .never)) // hide tab indicator
}
}
}
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the supplied ContentView example with NavigationStack, a pager TabView, and a plain List. Inspect how scrolling bounds are calculated for this combination and compare them with the expected List bounds. Done means the list scrolls within correct bounds in the reported configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100