Welcome to WebmasterWorld Guest from

Forum Moderators: open

Message Too Old, No Replies


Testing for compatability



2:43 pm on Jul 14, 2001 (gmt 0)

10+ Year Member

I am getting ready to start delivering different .js files depending on the browser version ie those > 4.9 and < 4.9.
Once I have done that I can test for objects and react with in each script.
The only problems I have found so far.. If I am using a function for the new browsers that the old don't understand I have to put a blank function in the older version .js file. I have also found that when testing for objects Opera will return True when it really dosen't exist as a working object. (I am assuming the next version will turn these objects on)
Does any one see any additional problems with going in this direction?


1:30 pm on Jul 16, 2001 (gmt 0)

WebmasterWorld Administrator brett_tabke is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

Have you tested some of the Mac Versions? Or browsers for Linux like Konqueror, Netscape or Opera? Or Icab for the Mac? They all react a little bit differently.

The only way I can see to make it work is to program for the least common denominator. Use one of the js validators - make sure it works in IE/NN, and then hope it works. I just don't think the web is workable under all these specific js routines.


8:36 pm on Jul 18, 2001 (gmt 0)

10+ Year Member

I still need to test for the Mac but I think they should be ok. The linux I have not thought about and at this point with retail sites (non tech) I am not sure if I need to. They would just fall into the older browser group. Opera and IE/NN are O.K.

The thing that got me thinking was studing the new stuff that can be done with the newer browsers. The ability to dynamicaly update page content using server side scripting, data base content and js is amazing to me. I still get alot of traffic from older browsers but when they finally upgrade they will go from the old to the newest.

I have not put any of this into effect. Still testing but old versus new makes sence If I can do it with out creating errors any where.

I should say that the js would only be there to enhace the site. The site would still work in non js browsers.

<<I just don't think the web is workable under all these specific js routines.>>

You might be correct but as fast as things are moving it won't be long and the need for as many specific routines should go down.


Featured Threads

Hot Threads This Week

Hot Threads This Month