You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hope everyone is doing well. We've gotten a little further with Safe Iframes and working with MOAT, our viewability vendor, to see if we can implement on Mobile Mail for viewability - and then move forward with expandables and more usage.
However, MOAT, is still finding a problem with the $sf.ext.geom().par variable not getting updated in IE 11 when scrolling.
I've updated my code to the latest version as you suggested and you can find this at:
This isn't a show-stopper as MOAT says they can work around this but wanted to raise this up as not sure what future problems this may cause.
(Sean)
Ah it's at the bottom and the doc height is coming in late, which is what I think
is happening on that test page, and perhaps why the standard impl is not always
getting updated right, I vaguely remember having some issue with that in the past.
The text was updated successfully, but these errors were encountered:
(Ed)
Hi all,
I hope everyone is doing well. We've gotten a little further with Safe Iframes and working with MOAT, our viewability vendor, to see if we can implement on Mobile Mail for viewability - and then move forward with expandables and more usage.
However, MOAT, is still finding a problem with the $sf.ext.geom().par variable not getting updated in IE 11 when scrolling.
I've updated my code to the latest version as you suggested and you can find this at:
http://browsertest.web.aol.com/ads/safe071415/safeTest110.html
This isn't a show-stopper as MOAT says they can work around this but wanted to raise this up as not sure what future problems this may cause.
(Sean)
Ah it's at the bottom and the doc height is coming in late, which is what I think
is happening on that test page, and perhaps why the standard impl is not always
getting updated right, I vaguely remember having some issue with that in the past.
The text was updated successfully, but these errors were encountered: