Welcome to WebmasterWorld Guest from 220.127.116.11
My simple blocker did STOPPED busting AJ's frame! I turned J & JS right back on.
Apparently my blocker acts as a script even thought my code doesn't specifically call one.
I presume those disabling Java and JS are somewhat more sophisticated than usual, and presumably
able to see that a site is being framed. Exceptions always apply, I could be wrong. -Larry
How did you come to this number? I have direct experience where I accidentally excluded the "noscript" code for fastclick on a monday and earnings was about 95 for the day. when I included the noscript code, earnings for the following Monday was 135 for a day! that's definitely more than 25%. It's too bad google does not have a noscript equivalent of their adsense code.
For the sake of my frame buster only, I would like some decent estimate of the percentage of
people with this particular feature disabled, no matter what you call it.
I want to think the numbers are small, especially if most users couldn't turn off J or JS
even if they even wanted to. I could be very wrong. Opinions / numbers anyone? - Larry
Now 4% of users not being able to use your site at all, would be significant. But 4% of users not being busted out of frames in the event that they came from AskJeeves or whatever, is not worth losing sleep over IMO.
Rechecking the numbers, I see that SitePoint was reporting stats calculated by TheCounter.com. That site has a "Global Stats" link on their homepage that leads to all kinds of useful data on user preferences.
i do agree that it was an unscientific proof but i believe it to be true. if i believed the numbers (sitepoints) you quoted, i would never have bothered to include the noscript code and i would have lost out on almost $45 per day from fastclick! what i'm afraid is that other webmasters might believe in your numbers and be unaware of significant economic consequences. I trust my direct experience rather than something i just read. you should try it sometime.
if (parent.frames.length > 0) top.location.replace(document.location); // Escape from any referring site's frame, but preserve one-click "Back". --></script>