search

vercel / next.js

The React Framework
https://nextjs.org
MIT License
125.79k stars 26.85k forks source link

weird render for first time render from server #9570

Closed vitthaljkulkarni closed 4 years ago

vitthaljkulkarni commented 4 years ago

Better1

Bug report

Describe the bug

I have an issue with render from the server. On the first load of the page, the layout goes for a toss. However it is corrected on subsequent renders via navigating the pages. Surprisingly the weired layout also appears on a browser refresh. I have tested it with both Chrome and Microsoft Edge but same problem. The app was created using standard boilerplate 'create-next-app' and then I just added a few of my pages. See screenshots below

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Go to 'app url'
  2. See how weird the layout is.
  3. Navigate away to any other page and come back again and see how the layout is again.
  4. Do a browser refresh and see how weird the layout is again.

Expected behavior

The layout should be consistent and clean.

Screenshots

Error1

Better1

System information

Additional context

Add any other context about the problem here.

timneutkens commented 4 years ago 
Go to 'app url'
See how weird the layout is.
Navigate away to any other page and come back again and see how the layout is again.
Do a browser refresh and see how weird the layout is again.

Which app url? No repository is provided which means this issue is not actionable.

I'm going to close this as a clear and concise reproduction is needed to help you.

vitthaljkulkarni commented 4 years ago

See attached screenshot please. Also app at http://junkbonds.herokuapp.com/Vitthal On 28 Nov 2019 14:39, Tim Neutkens notifications@github.com wrote:Go to 'app url' See how weird the layout is. Navigate away to any other page and come back again and see how the layout is again. Do a browser refresh and see how weird the layout is again.

Which app url? No repository is provided which means this issue is not actionable. I'm going to close this as a clear and concise reproduction is needed to help you.

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

balazsorban44 commented 2 years ago

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.