Currently the dom manages node id via Slab, meaning id are re-used (right?), and so if the application embedding Blitz is somehow doing some caching by node id, then that cache needs to be invalidated when a node is removed from the dom, and so it would convenient if the document mutator would return a list of invalidated node ids.
Example use case: Make nodes available to JS via the Dom standard API like getElementById(elementId), where multiple calls to get the same elements should return the same JS object, so the JS available Element must be cached, but if the node is dropped from the document then that cache must be invalidated.
Currently the dom manages node id via Slab, meaning id are re-used (right?), and so if the application embedding Blitz is somehow doing some caching by node id, then that cache needs to be invalidated when a node is removed from the dom, and so it would convenient if the document mutator would return a list of invalidated node ids.
Example use case: Make nodes available to JS via the Dom standard API like getElementById(elementId), where multiple calls to get the same elements should return the same JS object, so the JS available Element must be cached, but if the node is dropped from the document then that cache must be invalidated.