Brian Vaughn

Making refs "reactive" as you say would essentially make them the same as the `useState` hook. If you want a value that ensures a re-render on change, use the state...

The example above already works without anything in the dependencies array: ```js const ref = useRef(null); useEffect(() => { const observer = new ResizeObserver(); observer.observe(ref.current); return () => { observer.disconnect();...

Just to spell it out a little more explicitly, one way to approach this using a callback ref would be: ```js const cleanupRef = useRef(null); const refSetterFunction = useCallback((element) =>...

The frame limitation is mentioned in the docs, FWIW: https://github.com/facebook/react/tree/master/packages/react-devtools It's not a bug, just a known limitation. We currently suggest using the standalone version (as linked above) or (if...

Great! Keep me posted on your progress :smile: Here's instructions to get you started: https://github.com/facebook/react/tree/master/packages/react-devtools-extensions#build-steps

@marvinhagemeister Do you remember doing anything additional (beyond just adding `all_frames: true` option in `manifest.json`) to get it to work? I haven't taken the time to dig into this yet...

Gotcha! Thanks for elaborating :smile: > Maybe it's the same timing issue we've been talking about a while back that's more of a regression in Chrome? I think the fix...

Fair enough. Maybe someone else will pick it up :)

@anrao91 Unfortunately, no. Not beyond what's been discussed on this thread and on the linked PR (#18952).

@sarathps93 You're welcome to work on this. Please check out the work and discussion on #19345 before starting though!