Warn, don’t crash, when running Next.js inside an IFrame

[tomsoderlund]

Checks if Next.js is running inside an IFrame, in which case it doesn’t use window.history and throws a warning once.

Previously, this would generate this error:

Failed to execute 'replaceState' on 'History':
A history state object with URL 'https://NEXTJS-CHILD-SERVER/path' cannot be created in a document with origin 'https://IFRAME-SERVER.com' and URL 'https://IFRAME-SERVER.com/path'.

This is an update to #3437 (which is a solution for #3118).

[timneutkens]

We don't do this check right 🤔

[timneutkens]

So it probably should check for the method not being available

[tomsoderlund]

@timneutkens The method IS available (I think), just restricted by the browser’s security model.

[vladS111]

@timneutkens Actually we don't need history to be rewritten if we run Next inside the iframe.

[timneutkens]

Isn't this already handled in this if branch: https://github.com/zeit/next.js/blob/8aecb8d061bc8c50dba3f4601296e9785a7646db/packages/next-server/lib/router/router.js#L215-L224

[tomsoderlund]

I see now that the problem only applyies to Friendly IFrame's without src. Running Next.js inside a normal IFrame (with src) seems to work fine. So maybe our use case is more exotic than I first thought.

[tomsoderlund]

Oh, it looks like @hankmander's old PR #3437 is on the merge queue for 7.0.3:
b8f189f

[timneutkens]

It is not, it was replaced by the window.history check.

[timneutkens]

Could you fix the merge conflicts and add an integration test? I guess this is the only way to solve the specific issue with iframes.

[timneutkens]

I'll close this for now since it's conflicting with the current codebase.