Mike Shaver wrote:
On Mon, Nov 30, 2009 at 7:33 PM, John J Barton
<[email protected]> wrote:
The last bit that confuses me is the getClientRect() vs calls to
getClientRect() on an element an all of its children. getClientRect()
already returns a list. I guess the list part of getClientRect() is really
zero, one or two items, just to deal with tables in a special way?
If you have a page with a span that, well, spans multiple lines due to
wrapping, I would expect that you would get multiple rects:
............ AAAA
AAAAAAAAAA
AAA ..............
A would likely have 3 client rects, no? In the presence of floated
images I could imagine that it gets even more complex:
............ AAAA
AAAAAAAAAA
AAAAAAAFFF
AAAAAAAFFF
AAAAAAAFFF
AAAAAAAAAA
AAA ..............
Where F is a floated-right image -- could get 7 (?) rects, maybe? I'm
not sure how the implementation would split those out, tbh.
Ah, so that is the purpose of the list part of getClientRect()? The
documentation is opaque.
So then my question is: for the event target do we want the union of the
element's getClientRect() or that plus all of its children?
jjb
_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout
