David R wrote:
Wong Chin Shin wrote:
... and how in tarnation do some of you guys manage to maintain so many of them.


Simple answer:

I don't :)

I use http://www.browsercam.com, its got practically every UA and platform under the sun, the Remote Access feature is particularly useful

Browsercam is useful just to get an idea of how it looks, but only displays a limited part of larger pages, and provides no real interaction. Too much can slip away there, so I don't use it very often.

My (slightly more complex) answer is that I use a couple of fast PCs
running win2K-pro with Matrox 3-screen setups - and a few old PCs - on a
simple 8-way LAN. From 3 to 12 different browsers/-versions up at one
time during debugging, alongside a couple of editors based on HTML Tidy,
and Notebook for CSS. 6 to 8 screens, to avoid confusion.

Don't care too much about old browsers, unless I've got time for them
and want some fun. Clients may also have a say in this...

The browser-list is like this:

- The latest Opera is "standard", and a few older versions in the 7+
range for testing (the irregular ones).

- New Gecko-browsers are in - Moz - NN7.2 - FF, but FF 1.0 is usually
enough for testing (at the moment). A few older versions spread in the
system.

- Lynx (2.8.5) is useful, but I usually emulates that one in Opera. One
click and I know what I need to know.

- IE5 and IE6 comes last on the CSS testing-list - on separate PCs. Got
some stand-alones too, but they are of little use on my system - too
unstable.

- NN4.8 and IE4 are here just to see that they can receive plain HTML.

An iMac on its way in - tomorrow, so I'll get Safari - Omniweb - IE/Mac
(maybe) under control in the future (I hope).

Linux OS won't be included just yet. Next year - maybe.

All the other variables are handled by helpful individuals who makes me
aware of any "too bad" page-handlings in other browsers/OS. It's a 2-way
relationship that beats most other solutions. There's simply too many
things that can go wrong, to rely entirely on ones own setup.

Note that I "design" web pages only as a hobby. My professional
activities are focused on "how to make browsers work properly". I can't
do that through browsercam or similar services. I need "hands on"
contact with the browser's inner core.

        Georg

******************************************************
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************



Reply via email to