On 6 Aug, 03:46, Kevin Raleigh <krale...@sbcglobal.netwrote:
Is this sufficient for testing web pages?
In practice, this approach leads to _worse_ sites.
Test for validity and good practice first. Use one of the well-behaved
browsers as your initial working platform. If you test correctly
against the objective standards (this includes CSS validity) and you
follow good practices such as Strict DTDs, appropriate doctype
declarations, standards-mode rendering and avoiding features that are
known to be poorly supported, then you'll see good cross-browser
results even before you begin testing.
_Only_then_ start worrying about other browsers.
If your approach to "cross browser" begins with "my browser", then
"another browser", then particularly if one of these is IE, then
you'll make your work _worse_. This is especially true in teams, where
one coder might understand the real issues, but the average team
member doesn't.
Obviously I'm not saying "Don't test on IE". But don't test on IE
until you _already_ have standards-based testing in place, and use
good practices rather than focussing on the "throw it at IE until it
looks right" way.
