This bug didn’t show up in development.
It didn’t show up on first load.
It only appeared after users navigated back from a chat screen.
Users complained they couldn’t scroll to the last messages. The bottom navigation covered part of the list, and scrolling simply stopped too early.
At first glance, everything looked correct padding was there, styles were applied, and no errors showed up. But the browser didn’t care.
The real issue came down to how scrolling works: the container wasn’t the problem the content inside it wasn’t tall enough to scroll past the fixed UI.
Once that clicked, the fix was simple, and the UX immediately felt right again.
This article breaks down what went wrong, why it only happened after navigation, and what this taught me about building mobile-friendly layouts in Next.js.
Top comments (0)