Note that there are some explanatory texts on larger screens.

plurals
  1. POGet iPhone font-size to be the same as other browsers
    primarykey
    data
    text
    <p>A long time back, I read <a href="http://www.alistapart.com/articles/howtosizetextincss/" rel="noreferrer">a great article</a> that describes a cross-browser friendly way to size text using CSS. The strategy described is as such:</p> <pre><code>body { font-size:100%; line-height:1.125em; /* 16×1.125=18 */ } .bodytext p { font-size:0.875em; /* 16x.875=14 */ } .sidenote { font-size:0.75em; /* 16x0.75=12 */ } </code></pre> <p>This strategy works great on every browser except Safari on the iPhone, which always seems to enlarge certain bits of text. Is there any strategy to prevent this from happening?</p> <p>Normally my solution would be to add <code>-webkit-text-size-adjust: none;</code> to prevent the iPhone from enlarging the size of the text, but I recently came across <a href="http://www.456bereastreet.com/archive/201011/beware_of_-webkit-text-size-adjustnone/" rel="noreferrer">this article</a>, which describes that it doesn't allow users to zoom in on the text on ANY Safari browser - clearly a problem. I know that there is a CSS-only solution out there, but I can't find it. I just want to know how I should go about setting font-sizes so that they display the same on all browsers, including the iPhone.</p> <p>Update: To show an example, if you look at <a href="http://wexcode.com/C-Roc%20Gaming/" rel="noreferrer">this</a> on an iPhone, you'll notice that the text in the paragraph is significantly larger than the rest of the text around the site. Why is this text singled out, and is there any way that I can tell just by looking at the code that that will happen?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload