goldkillo.blogg.se

1. #UNRESPONSIVE SCRIPT FIREFOX GOOGLEADS.G.DOUBLECLICK.NET HOW TO#
2. #UNRESPONSIVE SCRIPT FIREFOX GOOGLEADS.G.DOUBLECLICK.NET SOFTWARE#
3. #UNRESPONSIVE SCRIPT FIREFOX GOOGLEADS.G.DOUBLECLICK.NET CODE#

First, we put this where we really want the ads: This is pretty intrusive, and it turns out that it pushes the browser’s tolerance to the limit.īut first, let’s look at the code. Let the browser reach the ad segment at the end of the document, and then manipulate the document tree, moving the element to its right position. If hijacking means to recursively run scripts loaded by scripts, there’s a good chance to really mess things up. So show_ads.js writes a script that loads other scripts? Doing what? Call other? And then I saw what the script in show_ads.js produces: I don’t like it very much, because it’s well, hacky. One widely proposed solution is to hack document.write(), which Google uses to implant the extra HTML. Unless all surrounding elements are nailed in place with absolute positioning, bad things can happen…Īnyhow, this method didn’t fit my case. And getting a block of ads in the wrong place is too bad to risk.Īnd I haven’t even mentioned what happens when the page is resized. There are scripts out there which claim to do that, but they don’t rely on any standard. Neither to get it into a known position within a containing block other than the one you’re currenly inside.

There is no safe way, that I know of, to get the absolute position of an element by its ID. This can be done only if one knows the exact pixel position in terms of the entire document. Proposed trick: Create a container at the end of the document, and push it to its place with absolute positioning. So now the trick is to get the ad in the right place.

#UNRESPONSIVE SCRIPT FIREFOX GOOGLEADS.G.DOUBLECLICK.NET CODE#

If the Google ad code appears just before the closing, the browser must be pretty boneheaded to wait for it. I mean, even Microsoft will fix this bug some day. This way or another, the problem remains. Firefox waited to prevent unpredictable execution of following Javascript code, IE just went on. Since the Google ad code consists of Javascript itself, the browser must wait until that code is loaded before running any other Javascript code (which may, as far as the browser is concerned, depend on it). The thing is, that I have a lot of Javascript embedded in my page. Even though IE played it nice this time, it’s actually a bug in IE. What really happened: IE6 went right on with the rest of the page, Firefox still waited for the ads to load. The inner DIV is absolutely positioned, so no matter what comes in there, everything else will remain in place. The outer DIV allocates the necessary space on the page.

Or stupid enough to overlook the inconsistency in scripting. Since an absolutely positioned section is out of the flow, and won’t change any other part’s placement, I hoped that the browser would be smart enough not to wait for the ads. The idea was that if the browser doesn’t need to know what’s inside the ad box, it will go on rendering the page. I don’t know if it’s because I’m using a lot of Javascript in my page or not. If you want to know who the killer is, and don’t care about the drama, just skip to the end. I say: A slow site is like no site.Īnd as with any story, the solution comes in the end.

One could also argue that the ads coming in late will draw more attention. One may argue that you want your money machine up (ha!) before giving away the goods.

#UNRESPONSIVE SCRIPT FIREFOX GOOGLEADS.G.DOUBLECLICK.NET HOW TO#

So here’s the story about how to have the page displayed first, ads later. Someone once told me that I didn’t want that to happen in my site.

#UNRESPONSIVE SCRIPT FIREFOX GOOGLEADS.G.DOUBLECLICK.NET SOFTWARE#

Posted Under: Internet, JavaScript, Software This post was written by eli on May 29, 2009