Geek Answers Handbook

Should a modern web application use intranet frames only or not?

I would like to ask about using frames in a modern intranet-only web application. Of course, there are several reasons to use or maybe not use frames in a modern Internet application. But what about intranet web applications (think of a financial application)?

Think about the parts of the application that in most cases are constantly visible (for example, a toolbar, menus, identification, etc.), where frames can be a simple / quick solution? Are these benefits such money when considering things like PPR?

I am curious and both are grateful for your opinion on this matter.

+5
source share
8 answers

Frames are not inherited by evil, but they create problems that other approaches do not encounter. Since you are talking about an intranet, you probably are not worried about:

  • frame search indexing values
  • usability / accessibility issues
  • Support for significantly different browsers (mobile, text, etc.).

In general, there is probably no great reason to shy away from them. However, I do not think that you have suggested good reasons to use them.

However: one problem that I could run into with a rich internet application is the potential need for your different pages / components to talk to each other. Frames can be a royal headache with scripts, and for this reason I avoid them.

+13
source

CSS, ASP.NET , .

, , , . , gif.

+3

, -. , , ( , ..). , ?

+2

, . , ajax , iframe - ().

+1

, . AJAX , ? , IE6.

0

, , . DOM, , iframes ( JS- ..).

, , . , , .

0

№. , , , .

, , CANT , <iframe>.

, , , , IE Quirks . , , .

0

, , CSS. (- > )

0

More articles:


All Articles