Nancy Johnson wrote:
> Doesn't it also somewhat depend on your user base? If you have a
> general user base than this is fine.
Technical testing across the board of major browsers/OSes is always
safest, since one can pretty much cover all bases this way.
Specializing in user bases or whatever, has to be an "add-on" if one
should avoid "fall-behind".
> Web developers may use Firefox more.
Some do (for whatever reason), but if a site breaks in other good
browser because of lack of minimal testing, then I'm not sure the site
creator qualify as a web developer. Same goes for everyone with a
"preferred tool".
> Graphic designers often prefer Macs over windows.
Indeed, although I've never figured out why :-)
Pretty much the same major browsers run on MacOS as on other OSes though
- except IE/win of course.
Minor variants tend to follow their major parents quite well, but it is
smart to test in them if one have them and got the time.
> There is the scientific community that in some instances may lean
> toward Linux.
Again, pretty much the same major browsers run on Linux OSes as on other
OSes - except IE/win of course.
It is of course always smart to test in exclusive Linux browsers if one
can, and I guess that comes naturally if the developer works on Linux -
is on the same base as the users.
> We have an intranet site which only is optimized for IE6.
Which clearly limits the need for testing - usually by dictate.
I still have to work with sites that are optimized for IE4, so although
these sites works equally well in the latest IE and non-IE browsers on
almost every point, they won't allow anyone to test in, fix for and use
newer browsers than IE6, because the dictator can't be bothered.
> Knowing your user base is important.
"Knowing your base" usually ends up as a limitation - unless the base is
created and pre-limited by dictate. Of course, even dictated bases have
to change now and then, for technological reasons if nothing else.
Users, even within a given user-base, may use their software/browsers in
different ways and with different set-ups, because they can or because
they need to. Users also change their preferences and needs over time.
If ones testing-strategy becomes locked to a base - any base, then it is
the web developer who ends up being limited. The base, with users and
all, will move on.
So, testing across a broad base and focus on technical issues instead of
users, will serve a web developer best. Users can only do what's
technically possible, and the developer should, ideally, know and test
to those technical limits.
Limiting the testing because of lack of technical resources and time, is
of course necessary in nearly all cases - which is why major browsers on
major OSes should be tested first. Limiting testing for any other reason
is, IMO, not good practice.
regards
Georg
--
http://www.gunlaug.no
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
