Bug: Detached node memory leak when using key and focus contenteditable element #25772
Labels
Resolution: Stale
Automatically closed due to inactivity
Status: Unconfirmed
A potential issue that we haven't yet confirmed as a bug
The DOM node stays in memory as a detached node if it has a content editable element inside what is focused using ref and that component is used with key prop in parent.
React version: 18.2.0, 17.0.2
Steps To Reproduce
All steps to reproduce are written in
README
file for this repo.Also there is a source code to reproduce the bug.
The current behavior
The DOM node stays in memory as a detached node and can not be collected with garbage collector.
The expected behavior
The DOM node doesn't stay in memory as a detached node.
The text was updated successfully, but these errors were encountered: