Tee G. Peng wrote:
I got an impression that setting 100.1% fontsize in body tag is a better approach and have been doing so for many sites. Also, with the 100.1% in the body, I usually declare .85em (.95 for my site as I love big fontsize :) ) for paragraph and lists. I also find that I get a more stable, closer fontsize across browsers.
I have the same experience, but I usually only set 100% - not 100.1% - as starting-point, since the old problems that '.1' was supposed to solve isn't there anymore. Besides, the only reason to set that percentage as a starting-point at all, is to avoid IE's 'em sizing bug'... <http://www.gunlaug.no/contents/wd_additions_13.html> ...which also affects font-size keywords btw.
... I aware that Opera often makes the size a bit bigger but this is a bit unusual for me. If I change the 62.5 to 100.1, nothing gets change for the Tab nav in Opera, it still shows 3/4px bigger than other browsers but the second level link text shrinks to like 4 or 5 pixel in IE, thus making it impossible to read.
I'm not aware of the latest Opera-versions having a _general_ problem causing bigger font sizes. Haven't seen any such problems since around version Op 7.20. In today's version such deviations are usually caused by inheritance through too many up and down sized wrappers, where Opera, or some other browser, may (seem to) lose steps. Sometimes that's caused by a a setting in a browser that is overlooked, and sometimes it's caused by different tip-over values in browsers. I may of course also have overlooked a genuine Opera-bug.
Client sent me this link, kind of suggesting that 62.5% is the better approach because his client isn't happy that now the heading texts are too small and the paragraph texts are too big due to the changes I made. http://www.clagnut.com/blog/348/ What do you think?
The suggested 62.5% as starting-point is too vulnerable, IMO. For the time being at least, the 'minimum font size' may create problems when extremely small font-sizes are used as starting-points... <http://www.gunlaug.no/contents/wd_1_03_04.html> Add the effect of different, and growing, screen-resolutions - and how browsers handle screen-resolutions differently - into the equation, and small font-sizes as starting-points may create even more problems. The "readable size" of different font-families shouldn't be forgotten either, since readability _is_ the most important point, IMO. Generally: if a document/design can take the stress from font-resizing options in browsers reasonably well - not break too early and allow the text to be easy to read without blowing up in the visitor's face, then it doesn't really matter what method you choose. I never argue against what browsers and screen-resolutions can do to my designs when it comes to font-size, I just try to make it work well no matter what. Usually that means my font-sizing starts at 100% and doesn't deviate too much from 100%, whereafter I leave to each visitor to decide what that 100% is. regards Georg -- http://www.gunlaug.no ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
