Topic: frames (Page 1 of 1)

OK kids. The company I work for wants to build both an intranet and internet using standard company guidelines (color, jscript nav, blah, blah) which includes the use of frames. What are the most recent statistics regarding browser compatability. Should I begin recommending them with my freelance projects?

Thanks.
CRO8

You've got me - why does the company's standard guidelines include the use of frames? I'm anti-frames unless you've got a good reason for using them - it might be time to propose a new set of guidelines (form a committee!!).

Emps

yeah- I am not sure why they require frames. I dunno. . . thats why I was curious which browsers accept/decline frames- making it possible for me to incorporate them on my side projects. I don't have too much experience with using frames.

All modern browsers (3.0+) support frames. Sometimes they can be useful, but people are using them less these days...

Thats good that all modern browsers use fames. Why are people using them less these days?

Because they can be very annoying when they aren't used properly...

IMHO don't use frames!

Sometimes you get problems with Google & Co., because they link to just one frame without any navigation bar (Cos this is on another frame =()

Understand?

Frames also makes external linking a pain.

I would be much smarter to use templates (header/footer). If you do it this way you get the same kind of effect as frames would give you, the write once, effect everywhere.

Frames are really unnessessary, because anything you do with frames that is different than what could be done with tables or css2 is bad use of frames, and causes a poorer user experience.

Frames have good uses, too. Imagine that you have a very complex navigation menu (a lot of images, animations, etc.) In that case it would be best to put menu on a separate frame, so that it doesn't have to be reloaded each time your visitor goes to new page...

But the images, animations etc. are already in the browser cache...

Web browser still has to compare them with those from server in order to see if they should be downloaded again and not to mention that they have to be renderend again and optional DHTML/JavaScript code (for the menu) has to be parsed again. All those things slow down page rendering...

plus they are an quick, easy, efficient way too implement a data drill down.

hmmm. Thanks everyone!