I have a hunch that many people here have a pet peeve about the way one or more of the major browsers render their pages.
I also have a hunch that many of us have found work-arounds that may not be widely known. I'm inviting everyone to post their discoveries and their questions in this thread. Here's a recent solution I finally stumbled over.
EXTRA PIXELS AROUND NETSCAPE FRAMES
I've been working with a client who insists on frames. Netscape adds a lot of extra "browser english" right next to the frame borders compared to the way Explorer holds the exact pixel dimensions. Somtimes important content gets chopped off in Netscape, and it seems like the only answer is to render a big blank spot in Explorer -- the majority browser.
Most people don't realize the <form> tag in Netscape causes an extra space, like a <p> tag.
For gutter spacing, and other space sensitive pages, where you start a form - even a simple dropdown menu - is suspect in Netscape.
The workaround I use is to nestle the form tag inside a table cell at the very beginning of the form,instead of designating a form line, with post method, etc. and then some HTML, and then the start of a paragraph or a new table and then the form.
Compare pages in MSIE and Netscape and watch the spacing around the form tag. It's confused many webmasters :)
Forms can cause no end of headaches. I almost always find that I need to use a browser detect script and create 2 versions of the page. Thanks for your hint, cre8pc -- I'll be paying attention to that workaround.
The design of a form page is often treated very casually. More often than not I see chaotic layout and ambiguous instructions. No matter how enticing the offer, if the form page isn't user friendly and un-imposing, the site will lose a lot of visitor response. For the want of a nail, the war is lost.
Edited by: tedster
tedster - I found your post from 9/4 about Netscape Background Problems very handy at [webmasterworld.com...]
and perhaps it belongs here as well...
Here's the workaround Dave refers to:
REPEATING BACKGROUNDS IN NESTED TABLE CELLS
When a background image is defined for a top level table, Netscape begins to render that image all over again with each new cell of any nested table, instead of just letting the single image "show through" the way Explorer does.
The fix? Set background="null" in the nested table tag, and both browsers will let a single image show through the way you would expect.
If you include a space anywhere in that list, Netscape just won't cooperate.
If your page design is tight, you can also place the opening/closing form tags between table cell walls;
... </td><form><td> ...
and it renders well in all browsers.
This is a new one to me and it sounds interesting. Do you have an example I can look at? You can sticky mail me the URL.