Closed wouterlucas closed 1 month ago
Why is that even an option?
Why is that even an option?
It was causing too much havoc - I don't think all clients are ready for super strict boundary rendering yet. We can always flip the default down the line.
Alternatively we can do a check to see if the node has children that are outside of their parent boundaries and implement behavior on that, but this comes at extra costs.
For now, we can set it to true by default where we need it to be and toggle this from an app dev perspective.
Enabling strictBounds will not render / process nodes that are outside of the visible area, otherwise the default behavior will render all nodes regardless of their boundary status.