Success! Looks like we've fixed this one. According to our records the fix was applied for
Ext GWT Premium Member
Grid with spanning heading bug - headers get the wrong width don't align [2.3] r2490
Revision 2490 added an adjustWidths() method in the ColumnHeading.java class. Unfortunately it fails when applied to Heading Groups (headings that have two rows). Some column headers on the second row are applied widths from the wrong column. If you set custom widths on each column it becomes obvious as the column headings get out of alignment with the rest of the column.
It's easy to see the error in the code when debugging.
Here is a scenario:
Row0 has a cell A that spans two rows, then a cell B that effectively spans the two cols (C & D) in the second row.
The adjustWidths() code will correctly apply the widths of A and then B (as a total of C&D). But then on row 2 there are really only 2 cells C & D as cell A belongs the first row (as it has a row span set). The adjustWidths() does not account for this and applies the width of A to the first cell (C) and then the width of C to the second cell D.
The code needs to check if rows above have rowspans and if so pick the next column config from the ColumnModel to get the right width.
I'll get an example a.s.a.p, but all our grids with header groups broke when we upgraded to 2.3 because of this (revision 2489 was only available in 2.3).
Please don't ignore this - either remove the adjustWidths() or make sure that the row spanning cells are skipped for the rows they span. It's a glaring error when custom widths are set on columns.
What to see how bad it looks? Ouch!HeaderGroupBugInGXTRev2489.JPG
So... I've seen a bit of bad press that sometimes bugs aren't fixed in Sencha products. Well prove them wrong! Be a hero and fix this one! (and maybe the long outstanding ComboBox force selection bug for extra awesomeness...)
Last edited by The_Jackal; 11 Jun 2013 at 4:07 PM.
Reason: Updated revision to 2490
What's about prioritize and schedule to fix?
Sencha - Support Team
Thanks for the report! I have opened a bug in our bug tracker.
We also have same issue. Somehow it works fine in FireFox but not in IE9
Is there any update on it?
This appears to be fixed in SVN and the nightly builds, and will go out in 2.3.1.