things NN won't do

when NN fails to respond intuitively

page 8 of 8

page 1
• margins and headers
• margins and headers with width
page 2
• setting div margins in a table cell
• setting div width in a table cell
• adding a border
page 3
• setting color of text in tables
• name anchor references
page 4
• closing table tag
• span tag
• negative margins
page 5
• broken images and alt text
• the title attribute
page 6
• the height attribute
page 7
• the pseudo classes
page 8
• iframes

iframes

Many people seem to think that iframes are a Microsoft proprietary tag. The iframe definition is actually part of HTML4.01. This tag is not support at all by NN4.7. Those of you who only browse with Netscape are probably missed a lot of information on pages using the iframe element.

The element is composed of open and closed tags. Browsers that don't support the tag will display any text between the open and closed tags. One can leave the tags empty.

The iframe takes is more like a textbox than a frame. In fact, to get the effect of a scrollable, fixed-size box on a page that will render across both browsers, a textbox is the perfect tool. Sometime sites will have copyright or licenses information in such a device.

The real power of an iframe is its ability to call a separate web page like a frameset page would.

It's really too bad that the iframe isn't supported by NN4.7, because it is definitely a neat little tag.

Below is the code for a page with some text above and below the iframe.

<iframe src="index.html" width=100 height=500
	scrolling=auto frameborders=1>
</iframe>

Below are screen shots of the NN4.7 and IE5.0 versions of the page. The page called in the iframe is a small text file.

we see in NN4.7:	we see in IE50:

NN4.7 does not respond to the iframe at all. If we put in some descriptive text between the open and closed iframe tags, that text would have appeared in NN4.7.