iOS 11带大标题的UICollectionView点击状态栏滚动到顶部卡顿错位问题

Yep, I dealt with this exact annoying bug a while back when building an iOS 11+ app with large navigation bar titles and a UICollectionView. That over-scroll stutter and accidental refresh trigger was driving me crazy—glad you noticed the Mail app doesn't have it (you're spot-on that it uses a custom scroll setup instead of UICollectionView).

Here are the solutions that worked for me, ordered from simplest to most explicit:

1. Tweak the Content Inset Adjustment Behavior #

iOS 11 introduced contentInsetAdjustmentBehavior for UIScrollView (UICollectionView's parent class). The default behavior can miscalculate insets when paired with large titles, causing that over-scroll issue. Try setting this in your viewDidLoad():

collectionView.contentInsetAdjustmentBehavior = .scrollableAxes

If .scrollableAxes doesn't do the trick, you can try .never but you'll need to manually adjust the content insets to account for the navigation bar and safe area:

collectionView.contentInsetAdjustmentBehavior = .never
let safeAreaTop = view.safeAreaInsets.top
let navBarHeight = navigationController?.navigationBar.frame.height ?? 0
collectionView.contentInset = UIEdgeInsets(top: safeAreaTop + navBarHeight, left: 0, bottom: view.safeAreaInsets.bottom, right: 0)
collectionView.scrollIndicatorInsets = collectionView.contentInset

2. Manually Control Scroll-to-Top Action #

If the first method doesn't resolve the glitch, take over the scroll-to-top behavior by conforming to UIScrollViewDelegate and implementing this method:

func scrollViewShouldScrollToTop(_ scrollView: UIScrollView) -> Bool {
    // Calculate the exact top offset to avoid over-scrolling past the content
    let correctTopOffset = -scrollView.adjustedContentInset.top
    scrollView.setContentOffset(CGPoint(x: 0, y: correctTopOffset), animated: true)
    return false // Block the default system behavior which causes the glitch
}

This explicitly tells the collection view where to stop scrolling, preventing that overshoot that triggers the refresh control.

3. Verify Refresh Control Setup #

Double-check how you're adding your refresh control. Using the built-in refreshControl property is key—avoid adding it as a subview manually, which can mess with scroll calculations:

let refreshControl = UIRefreshControl()
refreshControl.addTarget(self, action: #selector(handleRefresh), for: .valueChanged)
collectionView.refreshControl = refreshControl

I ended up using the second method in my project because it gave me full control and eliminated the glitch completely. Give these a shot—one of them should fix your issue!

内容的提问来源于stack exchange，提问作者utahwithak