When testing viewability reported, Chrome on Windows is off by a large factor when scrolling the page. It seems to be reporting a value that is the previously observed value.
From discussion report:
I am using the 1.0.2 version. I have a timer that calls $sf.ext.geom() and based on the geometry I'm
computing the amount of clipping of the iframe on the edges.
I've noticed the geom data is not the same between browsers.For example the self data. In firefox and IE the top, left represents the position in the document no scoll data is used in the values. On the other hand in chrome 32 the self top, left represents the position of the iframe with scrolling amount added, so they can have negative values when scrolled out of view.
Using the same 1.0.2 version, on the same test page structure, this time on chrome 33, the geometry values are fine, the self.top doesn't have the scroll amount added to it. The geometry values are the same like in firefox or ie. The test page I have has an absolutely position div where the safe frame is loaded.
yeah I know what this is. . . we have a fix incoming for it. . .