Comments

July 28, 2006 at 8:45 am

(1) Corky says:

NO! If your site is ADA compliant then you do not use frames. Most screen reader have a very rough time with these sites.

July 31, 2006 at 9:39 am

(2) Jason Champion says:

Corky is right about ADA compliance. There are those few times where frames can be useful (maybe intranet for small companies, or personal use for record keeping). But they should NEVER BE USED FOR PUBLIC!!! Not only that, but the metatags don’t work properly in some situations, different browsers react differently, and… you usually have to overload your site with javascript in order to get your pages to behave properly… which can result in slower load times. Just use ‘overflow:auto’ in CSS if you want a scrolling area, or use SSI or some other type of includes.

July 31, 2006 at 1:07 pm

(3) Robert says:

Now does this include iframes, because I love them, hahaha…

I agree though, frames were cool back when HTML first came out, but compared to what there is today, you should avoid them. I much rather make a page completely in CSS, but if only I could just write one set of code….. Stupid different browsers… P

August 1, 2006 at 8:29 am

(4) Sam says:

IFrames are alright in some cases but Frames just should not be used anymore period.

August 1, 2006 at 12:00 pm

(5) Sean McGee says:

Frames are now obsolete anyways. You can accomplish the same purpose with positional CSS.

I think the only case where frames are still functionally used by the big companies (including about.com) is when you link to an outside site. For instance, Google’s image search.

Pretty much any other reason you can think of to use frames, you can accomplish with positional CSS.

August 1, 2006 at 12:03 pm

(6) Sean McGee says:

Actually, the results of this poll are scary.

One out of four people (so far) that call themselves web designers say they use frames “for every site” they build.

No wonder we still have http://www.webpagesthatsuck.com.