HTML Frames.....

Is HTML frame is an old technology? Will the modern web application are
developed using the HTML frames? Does all the browsers support them?
Thank you for your suggestion,
NishAll browsers support frames, not all support iframes. I have never liked
frames and have always considered them old technology. Frames will exist
for a long time, but people have many choices for segmenting their pages.
They can use master pages. Or SmartNavigation. Or scrollable divs.
Just like any technology, it is more important to learn when to use
something rather than assuming that it might be obsolete.
"Nish" <Nish1989@.hotmail.com> wrote in message
news:%23YD$RzmRGHA.4332@.TK2MSFTNGP10.phx.gbl...
> Is HTML frame is an old technology? Will the modern web application are
> developed using the HTML frames? Does all the browsers support them?
> Thank you for your suggestion,
> Nish
>
Hi,
Peter Rilling wrote:
> All browsers support frames
Actually, not all browsers support frames. Mobile devices often don't,
or support them partly only. If the OP's website might be displayed on
mobile devices (PDAs, mobile phones), then I would rather avoid using
frames.

>, not all support iframes. I have never liked
> frames and have always considered them old technology. Frames will exist
> for a long time, but people have many choices for segmenting their pages.
> They can use master pages. Or SmartNavigation. Or scrollable divs.
> Just like any technology, it is more important to learn when to use
> something rather than assuming that it might be obsolete.
Frames have however one advantage over master pages or div: only parts
of the loaded "page" (I mean here page as a whole, meaning the frameset
and all frames) can be refreshed separately. It *can* be an advantage
(stress on *can*) in some situation, for example if one of the frame
contains a very big HTML table (in which case one might consider a
paging solution better, but anyway...).
It's possible to achieve the same with DIVs too, for example with AJAX.
However, it's more complicated and requests a good understanding of web
services, DOM, etc... as well as of the compatibility problems between
browsers.
Frames have a few divantages: Client-side communication between
frames is awkward, especially because synchronization problems are
involved: It's relatively complex for one frame to know for sure what
another frame's current state is. It's possible, but it needs a good design.
Also, the displayed URL does not necessarily correspond to a unique
state (because it's the frameset's URL and not a URL corresponding to
each of the loaded frames). This sounds like a very philosophical
problem, but it has implications one should be aware of. Again, it's
possible to solve this (for example using query strings on the
frameset's URL), but it's awkward and complicated.
I try to avoid using frames if I can, but I agree that you cannot really
call them obsolete. There are situations where they make sense. It's
good to be aware of the problems and advantages mentioned here to be
able to make an informed decision.
HTH,
Laurent
> Is HTML frame is an old technology?
I wouldn't call it a technology really. Just part of HTML.

> Will the modern web application are
> developed using the HTML frames?
Probably, though I hope not, as frames are usually implemented by developers
rather poorly. There's usually a better way to accomplish something rather
than resorting to frames.
Of coruse, there times when frames are useful.

> Does all the browsers support them?
Not sure if text browsers can handle them, but the major visual browsers
should be OK.
-Darrel