Hi, > Well, in general, the framework doesn't protect much against bad inputs.
It setting the width to 20-30 that causes the issue not 0, I'd not call that a bad input and it can happen at other width and text lengths as well it just that this manages to reproduce the issue easily enough. It turns out it's actually a spark scrollbar issue. It tries to add one then other find both don't fit, so removes one and gets caught in an endless loop. Thanks Justin
