Fix broken hash scroll logic

[oliviertassinari]

<Container> does not receive any property. There is no way the scrollToHash logic can work right now. I believe it's a regression. It was working fine at some point. I'm sorry, I'm too lazy to add a test.

This fix was tested on Material-UI 👌.

This bug reproduction is the following:
As soon as you want to transition to a new page with a hash. The scroll doesn't change.

• start on pageA
• you scrollTop to 100
• you move to pageB#hash
• you stay at scrollTop 100, but #hash is at scrollTop 400.

[timneutkens]

Thanks for the PR! Can you add a test here: https://github.com/zeit/next.js/blob/1a3f9507773a43e44748cbe5c0017223b99c3980/test/integration/basic/test/client-navigation.js#L246-L270

So that we can never regress on this again.

[oliviertassinari]

I have added a test. For some reason, it's green even without my fix 😱. I don't have a definitive explanation. It could be linked to rendering large pages vs the test pages that are almost empty.

You can reproduce the bug live on https://material-ui.com/ clicking on:

[oliviertassinari]

@timneutkens What do you think of updating the logic just for the sake of going back to what we had before the regression? This issue would require more investigation from me, but it's not something I have the budget for.

[timneutkens]

I'll try to reproduce, otherwise, the logic can be removed. As I was expecting it could be removed before already.

[timneutkens]

Just going to merge it in right now to be back at the previous behavior. Also, the test seems fine 👍

[oliviertassinari]

@timneutkens Thank you 🙏