Is it worth it to kill frames?

killing frames to protect content

[justgowithit]

I recently noticed an upward trend in the use of javascript to kill frames amongst some of my competitors and I’ve been contemplating whether or not to do this myself.

I keep my .htm file sizes down around 10K as a matter of principal and good web design. A snippet of javascript to kill frames would have a noticeable impact on my overall files size. An impact that I am not certain is necessary.

Is there anyone that can enlighten me to other benefits of blocking frames, besides the obvious, and somewhat minimal amount of content protection it provides?

[BigDave]

I wouldn't bother unless it became an issue because someone was actually doing it.

You also don't have to put it in each file. But it in an external .js file and load that into your web pages.

[justgowithit]

Hmm....

I guess it's never caused that big of a problem.

I'm aware of the different methods of implementation, I was more concerned with the different causes to warrant its use. Doesn't look as though there are many.

Fair enough - I'll stop worrying about it.

[GaryK]

Sorry to arrive late to this discussion. There's just too much to keep track of on this site.

Apart from content protection there are some search engines that keep a small frame at the top of each page with links back to the search engine ostensibly in case you forget where you came from. I don't like the idea of some search engine essentially advertising on my website just because they provided a link to it.