Should I cache calls to .getBoundingClientRect() (in mousemove for ex) or the browsers do that?

[Cyril Auburtin]

knowing that getBoudingRect use things like quadtrees I'm not sure it's good to call it very frequently

I've seen chrome has a cache for .closest for example, does it cache also .getBoudingRect?

[Cyril Auburtin]

code: https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/core/dom/Element.cpp&q=getBoundingClientRect&sq=package:chromium&l=1020

[PhistucK]

Looks like it triggers layout and then computes it. No cache.

closest is different since it does not care about layout, only the DOM hierarchy, which is a must simpler concept than layout. Also note that it looke like closest only caches the selector itself, the closest elements themselves are recomputed every time.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

[cyril.a...@gmail.com]

ok thanks, is there an estimation of the cost of this function? does it depend on the element depth in the DOM?

[PhistucK]

Less on the element depth (but also) and more on the CSS rules.

☆PhistucK

[cyril.a...@gmail.com]

ok thanks, reminds I just did a * {box-sizing: border-box;}, it seems working better with .getBoundingClientRect (for positioning overloays, or carets)