Controversial Web "Framing" Makes a Comeback

theodp writes "The WSJ reports that the controversial practice of framing seems to be making a comeback on the Web. Big sites like Digg, Facebook, Ask.com and StumbleUpon have all begun framing links recently, joining the likes of Google, which employs the technique for Image Search. Long ago, Jakob Nielsen argued that 'frames break the fundamental user model of the web page,' but, today's practitioners contend, 'it's a feature, not a bug,' and say it provides publishers with massive distribution they wouldn't otherwise have."

Comments

How to stop it

[Anonymous Coward]

stick this in the head of your page

<script type="text/javascript"><!--
var _tl=top.location,_sl=self.location;if(_tl!=_sl)window.top.location=_sl;
//-->
</script>

Re:Can I close the frame?

[RiotingPacifist]

Not that this affects you point, but for sites that don't offer that (I haven't come across any),
In firefox: right click -> this frame -> show only this frame, will sort you out, other browsers probably perform similarly.

What is the alternative?

[FlyingGuy]

Frames made it very simple to have you web content broken up into nice blocks. You could do all your navigation in one frame, that meant, one file contained your menus. You had one file to edit and you could produce a well defined, well behaved navigation system.

With the jihad against frames we were left with two options:

• The menu code had to be reproduced in every file you pulled in. Make a change to the menu system and if you served 1000 different pages, you had to change 1000 files.
• Serve it from a database, using php, ruby, perl, python or whatever. Massive complication since you had to build a CMS just to avoid getting smacked down or you had file includes all over the place in those same files, but to have a #include you had to use a scripting language, no more pure HTML for you.

ALL of this could have been solved by having the HTML spec provide a #include tag that would tell the browser to fetch that file eg: but no one seems to like that idea anymore then they likes framsets or iframes

As to Jakob Nielsen saying it breaks the user interface, that guy needs to get over himself in a big way. The web is evolving and changing all the time. As so many have said, the browser is not simply a page reproducer any more, those days are long gone, it has become an application container that allows applications, served from without to run in a defined and "secure" ( we hope ) application space on the local machine.

I for one advocate forking the whole notion. It is time to create and application shell that is specifically designed do just run applications of some specification. I propose that this can be done by making a tag to go along side as the top level tag and call . This would allow the "browser" to take one of two immediate actions:

• Start an Application Shell, load and run the app.
• Start the HTML rendering engine and display the page.

Further I propose that the navigation portion of be ported out to the browser and you simply load the elements of the menus and it is fed by a separate channel much like XMLhttprequest.