Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate viewport tag #8654

Closed
Dremora opened this issue Sep 6, 2019 · 3 comments
Closed

Duplicate viewport tag #8654

Dremora opened this issue Sep 6, 2019 · 3 comments
Milestone

Comments

@Dremora
Copy link

Dremora commented Sep 6, 2019

Bug report

Describe the bug

viewport tag gets duplicated in the browser (there's no custom viewport tag provided).

To Reproduce

This occurs on our site, but I've noticed that nextns.org has the same issue, so the instructions are for it:

  1. Go to https://nextjs.org
  2. Wait for the page to load
  3. Inspect the element tree
  4. Search for "viewport", you'll see two occurrences

Expected behavior

There should only be one.

Screenshots

image

System information

  • OS: macOS
  • Browser (if applies): Chrome
  • Version of Next.js: 9.0.5
@Janpot
Copy link
Contributor

Janpot commented Oct 8, 2019

@Dremora It seems like the provided page https://nextjs.org doesn't show the issue (anymore?).

In my case, I had a duplicate viewport tag because I defined mine in _document.js instead of _app.js. It also had a key property. Moving it to _app.js and removing the key property solved the issue for me.

Maybe the documentation isn't clear enough about this behavior? Although the behavior of the key property seems like a bug to me.

Edit:

It seems like this is intended behavior. So I guess this is a matter of missing documentation (I'm not free to send a PR).

@Timer
Copy link
Member

Timer commented Oct 18, 2019

Should be solved by #8960

@Timer Timer closed this as completed Oct 18, 2019
@Timer Timer added this to the 9.1.2 milestone Oct 18, 2019
@balazsorban44
Copy link
Member

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.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants