Mobile site text size

[libertyha]

Hi,

I believe there is a possible design issue on the mobile site. On the page doc.rust-lang.org/nightly/intro.html (the page that appears after clicking "show me more!" on the home screen) the text is very small for a mobile site. Zooming in and scrolling sideways and then scrolling down is possible but cumbersome. I was using an IPhone 4.

-Liberty H.A.

[Anttonii]

The website is fine when viewed on my iPhone 5s.

[nodakai]

On my iPhone 5s:

[steveklabnik]

Here's a screenshot from the simulator on 4: https://twitter.com/pbowden/status/537287102699147264

Wonder what's different?

[acdha]

It's definitely a bit small on an iPhone 4S. That really looks like it's not picking up a viewport declaration:

[steveklabnik]

https://twitter.com/mr_The/status/537287509064310787

[acdha]

Oh, there actually isn't a viewport declaration – adding something like this should fix that:

<meta name="viewport" content="width=device-width, initial-scale=1.0">

That's probably nicer than the usual app-style habit of preventing zooming altogether:

<meta name="viewport" content="user-scalable=no, width=device-width, initial-scale=1.0, maximum-scale=1.0">

[steveklabnik]

@acdha ahhh that would make sense. it looks like we need to use a meta tag for legacy stuff: http://html5hacks.com/blog/2012/11/28/elegantly-resize-your-page-with-the-at-viewport-css-declaration/

[steveklabnik]

I'm going to stop posting screenshots, as they all show that this is true 😄

[kerrizor]

Able to reproduce this on an iPhone 4 in both Safari and Chrome mobile browsers.

(Late to the party)

[iKevinY]

I can confirm that adding the viewport meta tag as @acdha suggested makes the documentation significantly more readable on mobile (iPhone 6 screenshots to round out the iOS device mentions):

Text is kind of big in landscape, but I think it would only take a bit of CSS to fix this:

Pretty much all "mobile-optimized" sites opt for the app-like viewport settings (where zooming is disabled altogether), so my two cents would be to go with the latter of @acdha's two examples.

[iKevinY]

I believe this issue has been addressed in #21133.