I prefer rem sizing. Ems is fine and all, but you can end up with some really quirky font sizes if you aren’t careful.
Just something I prefer. We were fine before REM was introduced. We could live without it. I just find it’s easier for me.
It also allows for me to basically make my own version of “vh”. Where I can simply media query different font sizes (16px, 15px, etc) for different sizes and it works like VH should (or rather, how we all want.)
Where this can be really annoying is when on Page 1 you have Parent–>Child–>Grandchild, and on Page 2 you have Parent–>Child and you are trying to get Grandchild = Child across pages.
The resolution would make no difference. You can add media queries to change the font size for the HTML element, as pointed out earlier. Then all REM measurements will update accordingly.
Did you have any problem selecting a font size in the old non-responsive days using pixel sizes?
If not, go with rem, as @RyanReese suggests. The rem unit does not scale like ems or percents as layers become nested. It remains proportional to the user’s font size, the <html> element, not the font size of the parent box.
I have always used EM because it is relative to a user’s preferred settings and scales.
I know nothing about this media stuff - it sounds like it relates to mobile and that topic has to wait for now.
But if I set the parent font to 16px and someone is visually empaired and they want the base to be 32px, then I have done them a disservice that wouldn’t have happened with EM, right?
The em unit is relative to the font-size of a parent container.
The rem unit is relative to the font-size of the <html> element; therefore, easier to code (no math to speak of).
In both cases, the user controls the displayed size of the font.
The sizing of the font within nested elements is much easier using rem units than em units because the rem is relative to the size of just one thing, the <html> element, which could be empty or could be percent. In all cases, the displayed font size is ultimately controlled by the user’s browser (just like your experience with em).