3 ms·
About the page view argument: this article shows a lack of understanding about the HTTP request. The browser does not add additional headers to a request indic
by kwamenum86 18y ago
About the page view argument: this article shows a lack of understanding about the HTTP request. The browser does not add additional headers to a request indicating that a page is loading in an iframe. Therefore loading a page in an iframe has the same effects (from a traffic standpoint) as loading the page normally.
About the ads argument:
Eh...maybe. I work on content-based websites everyday and a lot of thinking goes into ad placement. Digg/Facebook/Stumbleupon/whoever else are altering the presentation of these content sites and essentially placing ads on every site a user visits through their pages. Maybe that is the cost of having your content promoted on these sites. A 20 px toolbar won't affect most sites although it does look unprofessional and sloppy. At the end of the day, the content publishers have the right to control the presentation of their content and I would expect many to just break these toolbars using js. To my knowledge the top.location hack can't be stopped...believe me. Whether, as a content publisher, you support the toolbar doesn't matter. If you are in support of it you don't need to do anything otherwise you can insert a little js on your site and call it a day.
- jrockway 18y agoTo my knowledge the top.location hack can't be stopped...believe me. I did a quick experiment. If you set top = null, then top.location stops working.
- jrockway 18y agoIt turns out that I am wrong: http://gist.github.com/90381 http://gist.github.com/90381
- kwamenum86 18y agoWere you able to get it working in any browsers or did you discover it does not work at all later? That would be a huge loophole if it worked in any browser under any circumstances.
- jrockway 18y agoI only tried Firefox. Basically, you can set top = null in the parent page, and it behaves as you expect -- there is no magic going on. But "top" gets reset for the iframe. I didn't try anything more evil than that, though. I think if the parent script did something like "while(1){}", it could "starve" the iframe of CPU time, and it would never have the chance to change the URL. At that point, though, I think I would just implement the toolbar as browser chrome.