Let me start by saying that I was once a die-hard Netscape user. I resisted even trying Internet Explorer for a long time, but finally one of my Microsoft friends made me take it for a spin. Since that day, I've used IE for all my browsing, although at first I thought the differences between the browsers were mainly cosmetic, look-and-feel variations.
Then came some work-related Netscape frustrations (which I don't think I'm allowed to discuss, suffice it to say Netscape crashed a lot) and I began to form a negative opinion of Netscape. Still, I didn't cast any aspersions on Netscape users... I respect their anti-Microsoft stand even though I don't believe in it myself.
But I can't do that anymore because I'm too tired of all the things that are wrong with Netscape. Here is a list of my specific complaints:
Netscape is too picky about tables. I have two beefs here. First, if you leave the "border=0" attribute out of your table tag, the grid of your table will be visible as if you had been using cellspacing. My website looked hideous (in Netscape) for over a week as I tried frantically to find out what was causing this. Here is a sample of such a table, without and with the "border=0" attribute (view with Netscape to see the difference):
My second table-related complaint is that if a table cell contains no text, it will not be displayed with the background you specify. I often use tables to position things, which uses empty cells a lot. And I have found no other way to keep those cells from being displayed wrong than to put a character in that cell that has a font color that is the same as the desired background. What a pain! Again, here is an example:
General pickiness. IE is much more forgiving than Netscape of HTML mistakes. Forget to close a table cell, leave off the lower right cell of a table, things like that, and IE figures out what you meant to do. Netscape does not and goes strictly by the code.
Caching irritation. Netscape has a very powerful cache. By this, I mean that even after hitting "reload" (or even shift-reload), changes to a page are often still not displayed. (The cached version is displayed instead.) This makes for much added effort when one is trying to perfect a web page. I have to go in and manually empty the cache every time I want to see my changes. The only workaround to this is to set the cache to zero - but then, of course, everything loads much slower and it defeats the purpose of having a cache at all.