I'm having an issue with font sizing when a site I'm developing is viewed in the wide/landscape mode on an iPhone. It's built using a sub-theme of the Omega HTML5 starterkit.
Paragraph text (with <p> tags) are being enlarged, while other text such as headers are not. Some <a> tagged text is also being enlarged. I haven't done a thorough survey to try to figure out why some <a> tags aren't effected.
I did a quick online search and found that there is an issue with iOS enlarging text in the landscape mode. Several solutions were put out, all based on -webkit-text-size-adjust: none; .
But from the little I found, using -webkit-text-size-adjust: none; alone isn't the correct solution as it can effect an Webkit browser display.
Can anyone provide the appropriate coding solution for this? I'm in over my head right now on this.
I should note: I have the "Allow customizing viewport meta properties on iOS and Android devices " configuration box checked. I do not have the "Scalable by user" box checked under the "Viewport Settings."
Comments
Hi Arne, As far as I can find
Hi Arne,
As far as I can find out, the following can help.
<meta name="viewport" content="width=device-width, initial-scale=1" />and
body {-webkit-text-size-adjust:100%;}I believe it's a known bug from when switching from portrait to landscape and I will test my site on my wifes iPhone later to see what happens. I can't confirm the above code but give it a shot.
Sam.
I've seen this solution
I've seen this solution. But my understanding is that it isn't the best, as it limits text adjustment resizing on desktop as well. I'm not sure as I haven't tried it, but this is what I read online.
I'm thinking the solution needs to be a little more specific to the media type, using a media query as part of the code, but not sure how to do this.
http://stackoverflow.com/ques
http://stackoverflow.com/questions/5303263/fix-font-size-issue-on-mobile...
Something like this?
Sam.
Yes, I saw that
Yes, I saw that. I'm not clear how to modify this code for my site.
And I'm thinking that this issue must have come up previously in the development of Omega. So I'm hoping we can get some feedback from someone involved in Omega development. It seems like a solution to this issue might be part of Omega?