Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

meta viewport tag being overridden by the browser default

  • 2 uphendule
  • 1 inale nkinga
  • 4 views
  • Igcine ukuphendulwa ngu cranfan

more options

I have android 4.4 on a nexus10 and I believe my browser version is up to date. In order to test my website on mobile devices I have created a page within my site with a fixed width meta viewport tag as follows:

<meta name="viewport" content="width=799" />

On first loading the page, the width of 799px is correctly applied and the layout of the page is as expected. If I navigate away from the page and then return by the back button, my viewport width is lost and the page is displayed at 980px, I believe this is the browsers default viewport. To restore the correct viewport width of 799px it is necessary to refresh the page.

I have been testing for some months now and I don't recall this behaviour in the past? None of the other mainstream mobile browsers exhibit this behaviour, they all work fine.

I would appreciate any suggestions as to the cause and/or solution.

Thanks in advance.

Martin

I have android 4.4 on a nexus10 and I believe my browser version is up to date. In order to test my website on mobile devices I have created a page within my site with a fixed width meta viewport tag as follows: <meta name="viewport" content="width=799" /> On first loading the page, the width of 799px is correctly applied and the layout of the page is as expected. If I navigate away from the page and then return by the back button, my viewport width is lost and the page is displayed at 980px, I believe this is the browsers default viewport. To restore the correct viewport width of 799px it is necessary to refresh the page. I have been testing for some months now and I don't recall this behaviour in the past? None of the other mainstream mobile browsers exhibit this behaviour, they all work fine. I would appreciate any suggestions as to the cause and/or solution. Thanks in advance. Martin

All Replies (2)

more options
more options

Okay, thanks.

I might wait for the next version, and if it's still happening after that, I will file it.