However, unmount uses actualBatchOwner to optimise the removal of actual UI elements.
This leads to a conflict because some actual UI instances deeper in the tree are not actually removed from their parents, so adding them back again will result in an error.
Slot history stores fragments in unmounted state.
However, unmount uses
actualBatchOwner
to optimise the removal of actual UI elements.This leads to a conflict because some actual UI instances deeper in the tree are not actually removed from their parents, so adding them back again will result in an error.