To: Eric L who wrote (43296 ) 10/6/2004 2:14:58 PM From: Don Earl Read Replies (1) | Respond to of 110652 "As a matter of netiquette I generally consider it rude to move discussions all over a forum, although that has its place (as your move of our discussion here certainly did) but with your permission - and only with your permission - I would like to post my response to you here to the new Firefox board linking back to your original post here." Feel free to do so. There are a lot of different forums on SI. While some topics are narrow enough to limit to one discussion group, this doesn't strike me as one of them. "The root problem is Netscape 3 (or 4) is well past its (their) prime. No web designer gives any thought to them, With less than ½ of 1% of usage on websites and declining rapidly, they shouldn't have to." I don't want to get too carried away discussing Netscape 3. I certainly realize I'm in the minority in still using it. On the other hand, since most folks have moved away from it, I do think many people would be surprised at how functional it still is. With today's high bandwidth connections, the speed difference isn't as noticable, but it is there. Netscape 3 is VERY fast compared to anything else on the market. I suppose it had to be considering at the time it was released, anyone with a 28.8 connection acted down right smug. Personally, I still think it's a shame Microsoft was allowed to get away with the business tactics they did, which eliminated the possibility of Netscape (and many others) surviving as a stand alone company. A lot of good technology, much of which had the potential to be great technology, was burried as a result. I'm not any kind of technical guru. I can write some basic HTML (with a book in hand) and don't get too bogged down on most basic stuff. As a result there are probably places that make sense to me which would cause the less technically challenged to shake their heads in pure wonder. One of those places is since everything is backwards compatible, I always use my oldest browser to debug my HTML. If the display is okay in Netscape 3, I don't have to check anything else. I know the code will display properly on every browser made. I suppose my approach makes it hard for me to understand why anyone would want to start debugging code in one browser, then work backward and sideways to see if it works in others. Obviously picking Netscape 3 as the least common denominator would be too limiting for many applications, but I'd tend to think that general approach would be valid. If the objective is functionality, for the largest possible audience, and there aren't any major technical advances involved in achieving the desired results, it seems to me it would be a lot easier to start with the oldest first and call it good when it works