sirkrisp

@wellyshen Thanks for your reply, understood. I think it would be great if there was variable that indicates when we can trust the dimensions as returned by `useDimensions`. Because, by...

@wellyshen In my scenario, I had to create a Placeholder component that relies on useDimensions (It's a placeholder for an absolute positioned element). The placeholder is animated, so the initial...

@wellyshen Because the placeholder is animated, and this would result in an unwanted animation from zero to the actual width/height. Basically I cannot differentiate whether the target element has actually...

@wellyshen That would be extremely useful!

@wellyshen Will create a PR later today or tomorrow. Actually, I am not sure about the initialWidth/Height option - because those I could also pass into the component. What I...

@wellyshen I'm so sorry, I was very busy and completely forgot about it but I still want to implement it. In the meantime, if you do not want this issue...

@wellyshen I implemented the changes here: https://github.com/sirkrisp/react-cool-dimensions/tree/zero-width Can you have a look? Thanks!

@wellyshen I basically just initialised width and height with null and only after the elements bounds those variables are populated with the correct dimensions. I think initialising width and height...

In the screenshot below you also see that the nodes count keeps increasing even though with page virtualization it should stay somewhat constant.

Hi Sebastian, thanks for your reply. I have a few doubts, though. As the docs state: > It is often more economical to do a keys-only query **first**, and then...