>> That expression do not work well on other screen-resolutions than
>> 96dpi - the most widespread one that IE6 may be found on at the
>> moment, and there's not much I can do about that since resolution
>> can't be easily checked and used as a variable in expressions.
> Oh well, for me it suffices ... i guess if we want to consider all
> possible screen resolutions out there and users that change default
> font size etc.... we'll be in the magic business :-)
You're right: web design isn't magic - just code :-)
FWIW: my expression takes height for font resizing. That's the whole
idea behind extracting the browser's own font-size and using it to
calculate dimensional trigger-points.
And, yes, ideally we should take all those variants and options at the
user-end into account while designing. Someone may actually use them.
Pity those who create hardware and software don't always agree on how to
make all those variants and options interact, as that would have made it
much easier for us.
As more and more browsers come around to support mediaqueries, we can
start doing something useful for end-users with other set-ups and
preferences than our own. Still need some leveling on the hardware and
software front for it to work consistently though.
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/