In bug 531818 we came to realize that Firebug's 'inspect' function is
only one half of what one may want from it.
Currently Firebug outlines the getBoundingClientRect() values. This is a
CSS function that gives the CSS box, I believe it corresponds to "layout
area"?
But sometimes you are interested in a different box. For example, if you
wrap an <a> tag around a large image, you may want to know what part of
the screen responds to the link. I guess this is called the "event
targeting" area.?
For a given element, is the event targeting area according to ROC:
collect up all the getClientRects of the element
and all its descendants, include text node descendants.
Text nodes don't support getClientRects,
but you can create a Range covering the text node
and call getClientRects on that.
Boris said "union of all client rects", so I guess that is what "collect
up" means?
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?
(The event targeting area can be even more interesting now that we have
access to the event listener bindings).
jjb
_______________________________________________
dev-tech-layout mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-layout
