Return to Answer

Here's a simple CSS fix:

.nav { clear: both }

P.S. You can currently reproduce this bug on Stack Overflow by switching to the mobile view, thanks to the "ten million questions" announcement. Here's a pair of screenshots showing the SO front page with and without this fix (taken using the Firefox dev tools, in responsive design mode):

Here's a simple CSS fix:

.nav { clear: both }

P.S. You can currently reproduce this bug on Stack Overflow by switching to the mobile view, thanks to the "ten million questions" announcement. Here's a pair of screenshots showing the SO front page with and without this fix (taken using the Firefox dev tools, in responsive design mode):

Here's a simple CSS fix:

.nav { clear: both }

P.S. You can currently reproduce this bug on Stack Overflow by switching to the mobile view, thanks to the "ten million questions" announcement.

Here's a simple CSS fix:

.nav { clear: both }

P.S. You can currently reproduce this bug on Stack Overflow by switching to the mobile view, thanks to the "ten million questions" announcement. Here's a pair of screenshots showing the SO front page with and without this fix (taken using the Firefox dev tools, in responsive design mode):

Here's a simple CSS fix:

.nav { clear: both }

Ps. You can currently reproduce this bug on Stack Overflow by switching to the mobile view, thanks to the "one million questions" announcement.

Here's a simple CSS fix:

.nav { clear: both }

P.S. You can currently reproduce this bug on Stack Overflow by switching to the mobile view, thanks to the "ten million questions" announcement.