Tony Crockford wrote:
I'm still looking for a best practice solution to reducing font size to the *norm* and not causing problems when I do so.

The most cross-browser reliable method is to declare 'font-size: 100%'
as base, and size *down* _only_ on the text-carrying elements.

This approach let all container-elements inherit the base directly,
which means 100% = 1em = default = 'chosen or unchosen user preferences'
everywhere but on text. This will in most cases make it a lot easier to
size all elements to line up as intended relative to all others even
when 'em', '%' and 'px' is used in the element-size mix, than if each of
the container-elements rely on intermediate deviations from base font-size.

An added advantage is that text doesn't get unintentionally and
unnecessarily blown up in some browsers, because of how they apply
'minimum font size'. Call it browser-bugs or whatever, but too many
sites break under the slightest stress simply because they adjust
font-size _up_ from base (which usually is body) rather than down.

Once your font-size issue is solved in a way that makes it technically
able to take font-resizing well, then there's not much more you can do.
The need for font-resizing and how to achieve it, is for the end user to
decide on and solve, and your responsibility ends once you have made
absolutely sure _your_ solution doesn't prevent _them_ from using
_their_ software to resize.

The only way to make sure your method is not causing any unsolvable
problems at the user-end, is to test across browsers and browser-options
until breaking-point and a bit beyond. You should ideally know more
about how your solution behaves and how much stress it can take, than
any end user.
However, there's no way you can prevent a user from breaking your
well-prepared solution by adding a particularly nasty user-stylesheet,
so you can quietly limit your testing to the more ordinary, selectable,


List Guidelines:

Reply via email to