As users add more sheets (which turn into nodes), performance degrades because every node remains fully rendered in the DOM regardless of whether it is visible in the current viewport. The HTML layer (#nodeHtmlLayer) is synced to the canvas via a single CSS transform: translate/scale on the container so panning does not remove or hide individual node elements. Nothing checks whether a node is inside the viewport before rendering or keeping it mounted.
The frustrum math exists but a cull pass that compares node bounds against this frustum and toggles display: none on out-of-viewport nodes is not set
As users add more sheets (which turn into nodes), performance degrades because every node remains fully rendered in the DOM regardless of whether it is visible in the current viewport. The HTML layer (
#nodeHtmlLayer) is synced to the canvas via a single CSStransform: translate/scaleon the container so panning does not remove or hide individual node elements. Nothing checks whether a node is inside the viewport before rendering or keeping it mounted.The frustrum math exists but a cull pass that compares node bounds against this frustum and toggles
display: noneon out-of-viewport nodes is not set