Neil Deakin wrote: > Just improve the underlying code, or change interfaces? An improved and > well designed set of properties/methods for reading and modifying > position, size and other layout related specifics is much needed.
Not sure what you mean by "modifying"... We're probably going to implement getBoundingClientRect and getClientRects for all elements. These are IE-ish APIs that we will implement in a cleaned up way. Basically a "client rect" for an element is a rectangle in CSS pixels, representing the border-box of the element, relative to the top-left of the viewport, assuming everything is scrolled to its default position. getClientRects handles the case where an element is displayed in multiple frames. Rob _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
