You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TXMBase is designed to unregister and delete components if they are found to not be contained within the DOMNode of a parent component after a refresh. TXMBase was built this way in order to prevent memory leaks after successive component refreshes and updates. However, it is possible that we want to display a registered component for the first display, hide it for another display mode and then display it again on a successive refresh into another display mode. We need to figure out a way to only unregister the components that have no possibility of being displayed again.
The text was updated successfully, but these errors were encountered:
If component XYZ is not contained in the DOM, then
A. If component XYZ is registered into a repeatable section AND the repeatable section is still present, then component XYZ gets unregistered.
B. Else if component XYZ does not belong to a repeatable section and there was another (newer) component registered using the same tag name, then component XYZ gets unregistered (because the new component replaces it).
If component XYZ is contained in the DOM, then it does not get unregistered.
TXMBase is designed to unregister and delete components if they are found to not be contained within the DOMNode of a parent component after a refresh. TXMBase was built this way in order to prevent memory leaks after successive component refreshes and updates. However, it is possible that we want to display a registered component for the first display, hide it for another display mode and then display it again on a successive refresh into another display mode. We need to figure out a way to only unregister the components that have no possibility of being displayed again.
The text was updated successfully, but these errors were encountered: