status changed; resolution set
status changed from new to closedresolution set to fixed (In [14959]) Compute splitter thickness at layout time, if not already computed. Fixes #6932 !strict
View ArticleArticle 8
OIC, then it's not a dup of #5672, since in this ticket BorderContainer is a direct child of TabContainer. The first patch is probably OK... the second and third patch will work in the common case but...
View ArticleArticle 7
Here's the test case: Bad http://www.cb1inc.com/files/BorderContainerBad.html Fixed http://www.cb1inc.com/files/BorderContainerFixed.html This just fixes the BorderContainer?'s splitter. I'm sure...
View Articlesummary changed
summary changed from [patch] [cla] BorderContainer splitter width/height not being computed to [patch] [cla] BorderContainer: splitter width/height not being computed Can you attach a test case? If...
View Articleowner set
owner set to peller hmm. perhaps we can optimize further by only doing this check when the initial result was zero? We shouldn't have to compute them on each layout.
View Article
