JMartinCollins

According to [this post](https://github.com/reactwg/react-18/discussions/18#discussioncomment-801681): > Whether a component gets hidden or unmounted, refs that are attached to host components (like HTML elements) will be cleaned up and re-initialized the same...

[sandbox link](https://codesandbox.io/s/throbbing-cookies-fv9vgo?file=/src/App.js) Also something to consider is that the current effect cleanup order is different between simulated(bubble) and standard(capture) unmounts.

@HenrikBechmann I think what you're getting it is at the core of the issue with this (possible) bug. I think an effective way to check whether a component is mounted...

@tsarapke unrelated. The issue relates specifically to refs set to DOM elements. Looks like maybe yours can be solved by: ```ts // ... const prevParams = useRef(null); // ... if(!aborted){...

@tsarapke in a way it kind of *is* related. I think the approach that you *should* be taking with this hook is to pass it a DOM element ref. Then,...