Hi all. I've been away from these forums, and from web designing, for while now, and now that I'm back I'm seeing loads of threads taking about how awful frames are. Just wondering what's so bad about them - I've never had problems in the past. Also, if you're not going to use frames but still want the same type of functionality, what should you be using instead?<br />
<br />
Thanks for satisfying my curiosity!<br />
TBor<!--content-->Basically frames tend to split your content from your menus etc...<br />
So someone disabled using a screen reader or text browser might experience problems.<br />
On the other hand most of them do, so the real reason as far as we're concerned is Google. Google will display your site with the frameset title and no content... also when it's indexing it has to go further...<br />
<br />
Anyway, what most of us on this board use is css for layouts, and the css property overflow: auto; to create a scrolling box of content.<br />
<br />
For links you might want to check out:<br />
<br />
<!-- m --><a class="postlink" href="http://www.alistapart.com/articles/practicalcss/">http://www.alistapart.com/articles/practicalcss/</a><!-- m --><br />
<!-- m --><a class="postlink" href="http://www.bluerobot.com/web/layouts/">http://www.bluerobot.com/web/layouts/</a><!-- m --><br />
<!-- m --><a class="postlink" href="http://glish.com/css/">http://glish.com/css/</a><!-- m --><br />
<!-- m --><a class="postlink" href="http://www.inknoise.com/experimental/layoutomatic.php">http://www.inknoise.com/experimental/layoutomatic.php</a><!-- m --><br />
<!-- m --><a class="postlink" href="http://www.saila.com/usage/layouts/">http://www.saila.com/usage/layouts/</a><!-- m --><br />
<br />
<!-- m --><a class="postlink" href="http://www.w3schools.com/css/default.asp">http://www.w3schools.com/css/default.asp</a><!-- m --><br />
<!-- m --><a class="postlink" href="http://www.htmlhelp.com/reference/css/">http://www.htmlhelp.com/reference/css/</a><!-- m --><br />
<!-- m --><a class="postlink" href="http://hotwired.lycos.com/webmonkey/authoring/stylesheets/tutorials/tutorial1.html">http://hotwired.lycos.com/webmonkey/aut ... rial1.html</a><!-- m --><!--content-->
<br />
Thanks for satisfying my curiosity!<br />
TBor<!--content-->Basically frames tend to split your content from your menus etc...<br />
So someone disabled using a screen reader or text browser might experience problems.<br />
On the other hand most of them do, so the real reason as far as we're concerned is Google. Google will display your site with the frameset title and no content... also when it's indexing it has to go further...<br />
<br />
Anyway, what most of us on this board use is css for layouts, and the css property overflow: auto; to create a scrolling box of content.<br />
<br />
For links you might want to check out:<br />
<br />
<!-- m --><a class="postlink" href="http://www.alistapart.com/articles/practicalcss/">http://www.alistapart.com/articles/practicalcss/</a><!-- m --><br />
<!-- m --><a class="postlink" href="http://www.bluerobot.com/web/layouts/">http://www.bluerobot.com/web/layouts/</a><!-- m --><br />
<!-- m --><a class="postlink" href="http://glish.com/css/">http://glish.com/css/</a><!-- m --><br />
<!-- m --><a class="postlink" href="http://www.inknoise.com/experimental/layoutomatic.php">http://www.inknoise.com/experimental/layoutomatic.php</a><!-- m --><br />
<!-- m --><a class="postlink" href="http://www.saila.com/usage/layouts/">http://www.saila.com/usage/layouts/</a><!-- m --><br />
<br />
<!-- m --><a class="postlink" href="http://www.w3schools.com/css/default.asp">http://www.w3schools.com/css/default.asp</a><!-- m --><br />
<!-- m --><a class="postlink" href="http://www.htmlhelp.com/reference/css/">http://www.htmlhelp.com/reference/css/</a><!-- m --><br />
<!-- m --><a class="postlink" href="http://hotwired.lycos.com/webmonkey/authoring/stylesheets/tutorials/tutorial1.html">http://hotwired.lycos.com/webmonkey/aut ... rial1.html</a><!-- m --><!--content-->