This seems to STILL be broken? I just switched a bunch of tables to auto column width (because of my frustration over not being able to distribute 100% over the columns according to their importance and data types). This triggers some badness such has a heading "strength" being turned into "stren..." and "rank" becoming "r...". These appear unfixable but worse is this problem.
I have a table that displays "search results". The user types in a search string and boom, the table's data source changes and the results look ridiculous.
Do .refresh() on the data source and the data is redisplayed, but the table still looks ridiculous.
Click over to a different tab, then come back and the columns reallocate and the resulting layout is acceptable.
At first I thought this was happening only once after the entire app was launched. But no.... it happens at random intervals. If I type in another search query and the table loads with a different results set it MAY continue to look OK. However, I select a row and a related table display looks wonky. I then select a different row... still wonky. Click to another tab, click back, and both tables look fine, and stay that way as I click other rows and display related data.
It's entirely possible I am doing something during tab switch processing that "fixes" the bug. If I knew what that was...that might be an acceptable workaround.
But this issue is ANCIENT...and still open? It would be great to hear a definitive explanation of a workaround.
