Brett Patterson wrote:
[...] Now I realize where most of my problems have stemmed from.
Note that nearly all such "designer bugs" will be caught if you follow WCAG2 recommendations and resize text in a browser to at least 200% of browser default. (Default is 16px on 96dpi screen resolution in nearly all browsers, so 200% will be 32px on that resolution. Numbers grow with higher screen resolutions, but browser do not yet agree on how to deal with / adjust for rising screen resolution.) - If you can't resize text in the browser, then it's probably IE and the font-size unit is the wrong choice. Time to re-think design. - If design/layout breaks in unacceptable ways when subjected to font resizing stress, then the design/layout is at fault. Time to re-think design. Nothing you can do to prevent end-users from stress-testing your creations - because they want to or because they have to, so it is always best to test beyond breaking-point across browser-land before release. In the end you as designer/developer, consciously or unconsciously, decide how much your creation(s) should be able to take before it becomes "unacceptable". FWIW: I didn't stress you layout on first load in any browser, but it showed serious shortcomings anyway. Later when I did put it under stress by applying regular browser-options to it... <http://www.gunlaug.no/contents/wd_additions_37.html> ...it revealed its weaknesses. regards Georg -- http://www.gunlaug.no ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************