View Full Version : Why are FRAMES so Uncommon??
12-06-2006, 01:51 AM
I have been trying to come up with a "design" for my site ... looking at other designs they all seem to follow the TABLE with internals getting a portion.
Why do people not do this in FRAMES?? It would be faster ... or does this help control menus??
12-06-2006, 02:04 AM
Frames are a source of several problems. One that is quite common is that it "breaks the browser's Back button". Some users expect the Back button to take them to the previous site they were at. Instead, it takes the most recently used frame back. For example, if a user goes to your site via a search engine and looks through a couple of pages, that user might think the Back button would take them back to their search results (it makes sense, doesn't it?). Instead, it takes the most recently used frame back one page in the browser history. Accessibility and usability are the issues here, and some countries actually have accessibility requirements to meet. Tables are a pain and they take a long time to load, but they do get the job done better from a usability point of view. Tables are actually considered a bad way to go these days. Frames = worst. Tables = worse. Iframes = bad. Cascading Style Sheets + semantic markup + accessible design + usable design + etc. = good, better and best. :)
12-06-2006, 02:57 AM
maybe I are not so bright ... as with OOD i just never quite got it ... anyway I am trying to make a flexable site .. with a header ... and menu bar on the left and some jpgs with links on the right and the middle is the "active area"
I want to split the menu bar into search entire db, subject specific links and some scroll bars. Again I can visualize this ... just cannot see how to do it outside FRAMES or TABLES ... and FRAMES give me more flexability as far as I can see.
BTW the output of a shopping cart goes into the active area ..
now ... how to do this cleanly ... i have implimented CCS for text and background ... where can I go to read up on this?? ... ww3??
12-06-2006, 04:31 AM
w3schools (http://w3schools.com/) will teach you just about everything you need to know.
12-06-2006, 06:28 AM
people these days design layout in DIV alot. including me hehe . frames is just simple i think
12-06-2006, 12:12 PM
Doing a little Googling, I found this page (http://webdesign.about.com/od/framesprosandcons/a/aaframesyuck.htm), which makes a case for using frames, and this page (http://webdesign.about.com/od/framesprosandcons/a/aaframesyuck_2.htm), which makes a case for not using them. Interesting reading. Personally, I don't see that frames offer anything that I can't do with some well placed div's.
12-06-2006, 02:43 PM
My biggest reasons against using frames for an internet site:
They break bookmarking/favorites.
Search engine result pages often bring your user to one frame and don't load the whole frameset.
12-06-2006, 02:53 PM
None of the points made in favour of frames are very compelling, though ("Frames create an advertisment that is always present" would be another point not to use them!), and the points made against them omit search-unfriendliness and "breaking the frameset" by linking directly to inner documents.
NikkiH, you beat me to the punch! I gotta learn to type faster...
The only areas where frames really offer some benefit (reusing common areas like headers and navigation, and persistent navigation menus) can be mimicked by either server side or client side scripting.
Another useful source for some introductory tutorials would be HTML Dog (http://www.htmldog.com/).
12-06-2006, 03:37 PM
Frames can be blocked by some security settings. Adaware and phishing attacks can use inline frames. Frames are for porting websites inside other websites. thats all!!
12-06-2006, 04:48 PM
I agree. Frames are great for putting one website on another. I've used them when I have a webpage app that I want to put on another page. So far it has worked great.
At this point I can't imagine using them for web design though. CSS (for all the pain in cross-browser design) is much more flexible.
12-06-2006, 10:52 PM
I made a mock up of a frames page to work with my design. It ended up being 14 frames ... it's does exactly what i want is a little slow to load initially with the Flash header, quickly otherwise ... but it does exactly what i want ... I don't know which direction would be best here ... maybe just for simplicity get the site out in frames ... then build the <no frames> side with "proper" use of <DIV>'s and such.
thanks for all the input.
12-07-2006, 01:47 AM
If you do try out using CSS for layouts, remember to use semantic HTML/XHTML and not go div crazy.
Another huge benefit of CSS based layout is that you can re-design the site just by changing the stylesheet (assuming you did a good job of writing the XHTML). See http://www.csszengarden.com/
12-07-2006, 02:10 AM
Frames are great for putting one website on another.
12-07-2006, 07:15 AM
I can understand why you might not want your webpage embedded in someone elses. In my case it is my own that I want in another page. It isn't a layout issue. It's a functionality issue. The webpage was intended to be embedded.
Imagine having a calendar webpage. You could then embed that calendar in other webpages by using iframes without having to worry about how the page it is embedded in works. The framed page can have it's own css file and layout and look.
I'm not aware of how to do that without frames at this point.
12-08-2006, 05:22 AM
I would hardly call myself an expert in this area. However, I've never found anything you could put in an iframe that was better or easier than using CSS to style it. Anyway, you can have more than one stylesheet on a web page, so your calendar could have its own style and layout from a different stylesheet, too.
12-08-2006, 05:30 AM
Lots of better ways of embedding content without using frames:
Server Side Includes
to name just a few of the more common ones (and someone is sure to pick me up on several other common ways I have forgotten to list).
12-08-2006, 07:17 AM
That's assuming all the content is yours. If there was a website you wanted people to have access to without leaving your site. And the person whose website you wanted to access didn't mind or even encouraged it. Then iframes are an easy solution in my mind. Can a div render an html page? If so then I agree and don't see any reason for iframes. And maybe it can. I'm far from a CSS expert (I'm not even sure I can call myself a CSS anything other than novice).