Tim said:
The only way I have found to get consistent/exact height and/or with
using frames in all Netscape and IE versions that support frames is to
make my rows and columns using percentages in multipples of 10 and
only 10. I tried odd numbers, even number and multiples of 5, it seems
that you are only guarrenteed exact frames sizes in everything when
using multiples of 10. After you know you windows sizes you can use
postioning technoques to get the look you want.
The only way to get a consistent, interoperable, fast-loading,
extensible and professional web page in W3C web standards compliant
Netscape versions (like NS 7.x) is to make a webpage entirely scalable,
using valid markup and valid CSS code and to avoid recourse to frames
and [nested] table design.
"Frames tend to cause problems with search engines, bookmarks, emailing
links and so on, because frames don't fit the conceptual model of the
web (every page corresponds to a single URL)."
Google.com on why your page might not be indexed by google:
http://www.google.com/webmasters/2.html
"Frames introduced several usability problem that caused several
commentators to advise Web site builders to avoid them at all costs.
Examples of such usability problems are:
* The [back] button works unintuitively in many cases.
* You cannot bookmark a collection of documents in a frameset.
* If you do a [reload], the result may be different to what you had.
* [page up] and [page down] are often hard to do.
* You can get trapped in a frameset.
* Searching finds HTML pages, not Framed pages, so search results
usually give you pages without the navigation context that they were
intended to be in.
* Since you can't content negotiatiate, noframes markup is
necessary for user agents that don't support frames. However, almost no
one produces noframes content, and so it ruins Web searches, since
search engines are examples of user agents that do not support frames.
* There are security problems caused by the fact that it is not
visible to the user when different frames come from different sources."
http://www.w3.org/TR/2002/WD-xframes-20020806/#s_intro
Not to mention printing individual frame, copyright infringement,
necessary script dependency, etc..
DU