I’m running into a recursive loop with a ResizeObserver, where something inside the observed container is changing the size of the container on re-render, which causes the ResizeObserver to re-trigger.
In this specific case, there are several items I suspect may be causing this, but haven’t been able to pinpoint what causes it. Using the DevTools debugger, I’m able to see the ResizeObserver is triggered, but the Stack trace is empty.
There’s a good chance it’s caused by Javascript, but an equally good chance it’s caused by some part of the css layout, which would not be stack trace-able.
Is there some way to see why the ResizeObserver is called?