Closed CatchABus closed 2 months ago
The problem seems to be caused by ScrollBox
being instantiated without options parameter:
e.g.
const sb = new ScrollBox();
sb.addChild(new Graphics());
Perhaps, constructor options
parameter should not be marked as optional or throw exception if developer doesn't call init.
Closing as it's not a bug.
Expected Behavior
ScrollBox should be destroyed upon calling
destroy
without problems.Current Behavior
ScrollBox throws upon destroy if
background
is not set and background should be optionalSteps to Reproduce
Call ScrollBox
destroy()
.Environment