JavaScript FrameBuster Snippet
Oftentimes you want to make sure your site isn't being IFRAME'd. Sometimes it's for security reasons, other times it's so your site's content isn't being skimmed else, and other times it's...oh, who cares, you just want to do it. Here's a short way to escape frames:
if (top.location != self.location) {
top.location = self.location.href;
}
Uglify this and you get 63 characters of gold. Simple, effective.
![Create Namespaced Classes with MooTools]()
MooTools has always gotten a bit of grief for not inherently using and standardizing namespaced-based JavaScript classes like the Dojo Toolkit does. Many developers create their classes as globals which is generally frowned up. I mostly disagree with that stance, but each to their own. In any event...
![Introducing MooTools Templated]()
One major problem with creating UI components with the MooTools JavaScript framework is that there isn't a great way of allowing customization of template and ease of node creation. As of today, there are two ways of creating:
new Element Madness
The first way to create UI-driven...
![Using MooTools For Opacity]()
Although it's possible to achieve opacity using CSS, the hacks involved aren't pretty. If you're using the MooTools JavaScript library, opacity is as easy as using an element's "set" method. The following MooTools snippet takes every image with the "opacity" class and sets...
![Create a Simple Slideshow Using MooTools, Part II: Controls and Events]()
Last week we created a very simple MooTools slideshow script. The script was very primitive: no events and no next/previous controls -- just cross-fading between images. This tutorial will take the previous slideshow script a step further by:
Adding "Next" and "Previous" controls.
Adding...
Sorry bit of a jacascript noob here – this sounds great but how would one implement it? Where does it go?
Again apologies for what must sound a simple question.
Just toss it at the top of your javascript file :). Really anywhere in your JS this would work.
Just don’t put it inside a function unless that your intention. For example if for some reason you want to give your users a chance to make sure the page isn’t iframed by clicking a button then you put that code in a function say unIFrameMe() and then call that function when onclick the button.
In general, you’ll want this code to be outside of a function, so it is run when the js is loaded.
EMILIO!
But what about the Frame Buster Buster?
http://stackoverflow.com/questions/958997/frame-buster-buster-buster-code-needed
Thanks for the answers re the javascript.
htaccess solutions might be better as they are not so easily bypassed:
To blocks all sites (including your own) from iframing your pages:
or to block any external site from iframing your pages:
You can also only block some of your urls with the x-frame-options header. Here’s an apache solution
Header always append
X-Frame-Options SAMEORIGIN# Block any site from applying an iframe.Apparently I didn’t use `pre` tags.