Recently I hit a strange bug involving an expandable ListGrid.
I have attached a small TestCase that will reproduce the problem.
I was able to reproduce the problem using the latest nightly build for SmartGwt 5.0 (SmartClient Version: v10.0p_2015-04-17/LGPL Development Only (built 2015-04-17))
Steps to reproduce:
1) Expand the ListGrid.
2) Resize (widen) a column in order to get a horizontal scroll-bar on the grid.
3) Scroll to the end of the grid. (So far everything is fine...).
4) Widen more a column in order to get a bigger scroll-bar.
5) Now try scrolling to the of the grid -> BUG -> It appears that the nested layout becomes unaware of its actual boundaries.
P.S.
There are two notes I wish add:
1) When overriding getExpansionComponent(..) and the returned layout's width is set to setWidth100(), it doesn't auto-scale when a horizontal scroll-bar appears. It stays locked in the grid's viewport. This may or may not be related to the bug I've described, but still it's unexpected behavior.
2) I wasn't able to find a way to refresh (invalidate) a nested component, except collapsing and re-expanding it...
I have attached a small TestCase that will reproduce the problem.
I was able to reproduce the problem using the latest nightly build for SmartGwt 5.0 (SmartClient Version: v10.0p_2015-04-17/LGPL Development Only (built 2015-04-17))
Steps to reproduce:
1) Expand the ListGrid.
2) Resize (widen) a column in order to get a horizontal scroll-bar on the grid.
3) Scroll to the end of the grid. (So far everything is fine...).
4) Widen more a column in order to get a bigger scroll-bar.
5) Now try scrolling to the of the grid -> BUG -> It appears that the nested layout becomes unaware of its actual boundaries.
P.S.
There are two notes I wish add:
1) When overriding getExpansionComponent(..) and the returned layout's width is set to setWidth100(), it doesn't auto-scale when a horizontal scroll-bar appears. It stays locked in the grid's viewport. This may or may not be related to the bug I've described, but still it's unexpected behavior.
2) I wasn't able to find a way to refresh (invalidate) a nested component, except collapsing and re-expanding it...
Comment