# fix\(mobile\): a fresh pull request opens below the header on the folded iPhone Duo · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/e0152b40aed2b23f4febbb1e70a3baa9e5abc385)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: e0152b40aed2b23f4febbb1e70a3baa9e5abc385

Requested commit: e0152b40aed2b23f4febbb1e70a3baa9e5abc385

Commit: e0152b40aed2b23f4febbb1e70a3baa9e5abc385

Tree: 220b0b51c1a6f5086ee3f19305f9d23fcb10bf2b

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
fix(mobile): a fresh pull request opens below the header on the folded iPhone Duo

Each iOS stack screen gets its own safe-area provider. Until UIKit
measures that column, it reports the window's insets, and the window
on the folded iPhone Duo has no top inset because the status bar sits
on the side. Pull request detail passed -insets.top to LegendList as
initialScrollOffset. LegendList keeps its first value, so it pinned the
scroll view's contentOffset at 0. When the header's inset arrived, the
content inset grew but the offset stayed put, which hid the title
under the header as if the page were already scrolled.

The scroll views behind the pull request detail, the pull request list,
reviewers, and Home now own their resting offset. They follow the top
inset while resting below the header and hold it once scrolled. These
lists previously re-applied -insets.top on every inset change, so a
rotation or fold also jumped a scrolled reader back to the top.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

```

## Parents

- [e4779fd19c54c4368e54f87ac163673f92e3a214](https://git.cafe/pingdotgg/t3code/commit/e4779fd19c54c4368e54f87ac163673f92e3a214?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/e0152b40aed2b23f4febbb1e70a3baa9e5abc385?format=markdown)