AND-3136 - Fix positioning of Ads when a content embed is displayed. By introducing the setTimeOut with just a 50 MS delay prevents the getMpuPosCallback function from triggering to early and the correct add position with the iFrame content and height is computed passing the correct Ad position to window.GuardianJSInterface.mpuAdsPosition function which the native app uses to position the ads over the placeholders
AND-3136 - Fixed Issue with setTimeOut of 1 second - onload function for iFrame content being completely loaded triggering a callback would be ideal solution in case of slow connections as the getMpuPosCallback would only pass the Ad coordinates once the iFrame content has loaded, however I've not got this to work at this point and this bug is now on hold whilst a decision is made over Ad positioning, so I'm commiting this setTimeOut solution, now it only applies to Articles with an iFrame
AND-3136 - Remove console log message and changed user credentials from my old git hub account creds entered by accident to git config
AND-3136 - Commented out Console log messages and increased ad load delay on Articles with iFrames to 3 seconds to account for slower connections
AND-3136 - Commented out Console log messages and increased ad load delay on Articles with iFrames to 3 seconds to account for slower connections
AND-3136 - Changed if/else to ternary operator to make less verbose and changed onloadhandler function to CemelCase onloadHandler
Merge pull request #298 from guardian/AND-3136

AND 3136