Opera is also a decent choice,
and Mac users can probably get away with using Safari for initial tests.
Once the basic structure is up and running, I test in a range of alternate web browsers, typically
in the following order:
1. The other compliant browsers: Typically, I use Firefox as a starting point, although
sometimes I use Safari. Whichever one you choose to start in, it??™s a good idea to
test in the other compliant browsers first. Sometimes, one will pick up a coding
error the others don??™t, and it??™s a good sanity check to ensure everything??™s working
well. If you??™re lucky, everything will work fine right away in all of these browsers, on
both Mac and Windows.
2. A browser in text mode: What I mean by this is testing the site without CSS, which
is a way of somewhat figuring out if it??™s usable on alternate devices. Old hands
might use Lynx for this, but I instead use the Accessibility layout option of Opera??™s
User mode (see the following screenshot). The Firefox Web Developer toolbar
(www.chrispederick.com) offers similar options.
3. Internet Explorer 7 for Windows: Although this release of Internet Explorer is a vast
improvement over previous efforts, it??™s not as standards-compliant as the other
mainstream browsers. Therefore, tests need to be done to ensure everything??™s
working properly, not least because Internet Explorer 7 is the most popular
browser in terms of market share. If things aren??™t working right, conditional comments
need to be used (see the ???Dealing with Internet Explorer bugs??? section later
in the chapter).
Pages:
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451