Inline frames give you the best of both worlds. They provide many of the benefits of frames without the disadvantage of having navigation in more than one frame. Inline frames do not look like frames at all. No border separates an inline frame from the rest of the page. Inline frames also do not have the capability of independent scrolling.

An inline frame is like a server-side include. You refer to the HTML file you want to appear in the inline frame, and when the page is rendered, it appears as if the inline frame were part of the main HTML document.

The principal disadvantage of using inline frames is they are not well supported by the browsers in use. Inline frames are a recent addition to the HTML elements. Currently, only Internet Explorer 4 and newer browsers support inline frames. Inline frames and <IFRAME> are identical.

Browsers that don’t support IFRAME, or have IFRAME support turned off, will display everything contained between the <IFRAME> tag and the ending </IFRAME> tag in the current window.

Those browsers with IFRAME support will link to the SRC attribute for the URL of the page to display in the inline frame, and ignore text contained in the IFRAME tags.

Inline <INLINE>
Start Tag: Required
Content: Empty
End Tag: Required

Attributes:

id, class, title, style, longdesc
name: name of this element; useful for scripting
src: required; the URL of the page you want inserted
into the inline frame
frameborder: defaults to “1”; set to “0” if you don’t want a border
marginwidth: width of margin in pixels for both sides
marginheight: height of margin in pixels for top and bottom
scrolling: yes, no, or auto; you only need to worry about this if you set the height and width to be smaller than the known contents of the URL
height: height of the inline frame in pixels
width: width of the inline frame in pixels
align: deprecated; used to specify alignment on the page