Welcome to WebmasterWorld Guest from 54.145.246.183

Forum Moderators: incrediBILL

Browser Work-arounds

   
8:57 pm on Oct 11, 2000 (gmt 0)

WebmasterWorld Senior Member tedster is a WebmasterWorld Top Contributor of All Time 10+ Year Member



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.

We found a fix -- on the frameset page run a JavaScript browser detection. Then use document.write to code the frameset's row or column dimensions, one way for Netscape and the other for Explorer. No more chopped off text in Netscape (as long as js is enabled.)

4:17 pm on Oct 18, 2000 (gmt 0)

10+ Year Member



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 :)

Kim

8:06 pm on Oct 18, 2000 (gmt 0)

WebmasterWorld Senior Member tedster is a WebmasterWorld Top Contributor of All Time 10+ Year Member



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

10:07 pm on Oct 18, 2000 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



tedster - I found your post from 9/4 about Netscape Background Problems very handy at [webmasterworld.com...]
and perhaps it belongs here as well...
7:39 am on Oct 19, 2000 (gmt 0)

WebmasterWorld Senior Member tedster is a WebmasterWorld Top Contributor of All Time 10+ Year Member



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.

6:10 pm on Nov 17, 2000 (gmt 0)

WebmasterWorld Senior Member tedster is a WebmasterWorld Top Contributor of All Time 10+ Year Member



JAVASCRIPT FOR NEW WINDOWS

Even though extra spaces are "supposed to be" ignored in JavaScript, there are places where Netscape will choke if you include a space.

A good example of this is when you use JavaScript to open a new window, and then list all the attributes you want the window to have, like status bar, location bar, scrolling, and so on.

If you include a space anywhere in that list, Netscape just won't cooperate.

It seems funny that Netscape, the creator of JavaScript, has this bug -- but Explorer, who really runs something proprietary that they call jscript, ends up supporting the JavaScript standard more exactly ... at least in this case.

9:56 pm on Nov 18, 2000 (gmt 0)

10+ Year Member



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.

10:29 am on Nov 19, 2000 (gmt 0)

WebmasterWorld Senior Member tedster is a WebmasterWorld Top Contributor of All Time 10+ Year Member



Hi Yanton,

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.

Thanks

 

Featured Threads

My Threads

Hot Threads This Week

Hot Threads This Month