The description of the usage of the scroll option is that it controls whether or not the scroll offsets of the parent elements should be included in the calculation of an element's offset. With reference to the http://dev.jquery.com/~brandon/plugins/dimensions/test/offset.html visual test page, this works fine for Absolute3, Static3, and Inline1, all of which are within the scrollable Relative3 area. My problem is with Relative3 itself, in that if you scroll it, the offset is calculated (with scroll:true) using its own scroll offsets, so that sending the grey box to a scrolled Relative3 puts the box outside the visible area of Relative3. This seems to contradict the stated use of scroll in that Relative3 does not have parents that have been scrolled but has itself been scrolled.
The reason for my query is that it is causing problems with Ext, purely on this one point. I have raised it on extjs.com, with a possible work-around, but Jack Slocum's (perfectly reasonable) response is to wonder why other plugins (YUI, prototype) don't have a similar problem when they too supposedly "take scroll into account". Well I don't know about prototype, but this one sticking point is the big difference between YUI and the jquery dimensions plugin. I don't have an opinion on right or wrong (basically because I can't decide which approach is more logical!), so I'm posing the question, and, I suppose, requesting a change in either the behaviour or the description (of the offset method) in order to make one consistent with the other. And ultimately to get jQuery working consistently with Ext! PS. I have put up a modified version of the Brandon's visual test that uses the YUI position calculator, just so that interested parties (if there are any) can see the difference between YUI and jQuery. http://www.wizzud.com/getxy/index.html http://www.wizzud.com/getxy/index.html -- View this message in context: http://www.nabble.com/Question-about-scroll-in-dimensions-plugin-tf3777343s15494.html#a10681054 Sent from the JQuery mailing list archive at Nabble.com.
