Re: Resolutions and combinations

John,

it can certainly make one crazy (er) trying to keep track, no doubt about that.

Because I have proven over time to be a rather simple minded fellow, I try
to keep things simple:

1) Design for the lowest common denominator as supported by documentation
(that would be your demographic research).
2) Use ratified code, avoiding fixed widths in tables whenever possible.
3) Keep in mind that HTML is a markup language - not - a page layout language.


Playing by these three "rules", I have found life much simpler! I use ONE
browser (which ever one will get me to the validator), and one resolution
(because I know my content will dynamically resize to fit whatever client
combination is used).

That has worked 99.999999% of the time over the last several years. The
only real exception being when I had to please a client that didn't pay
attention when I explained that there were "millions" of
browser/resolution/platform variations out there.

FWIW,
Fuzzy.

At 02:49 AM 3/12/02 , John Aitchison wrote:
>
>There are so many possible combinations of client machine 
>configurations that it is mind boggling. I just wrote down some of the 
>factors that could go to make up the combinations.. 
______________________________________________________________
Captain F.M. O'Lary
ctfuzzy(at)canopy.net
I live in my own little world, but it's ok, they know me here.
------------------------------------------------------------------

HTML: hwg-basics mailing list archives, maintained by Webmasters @ IWA