Comment 3 for bug 433903

I don't understand why it's dependent on that at all. Regardless of how wide the table is, why should its columns ever be the same width? That would make sense if the columns were showing the same type of datum, but in this table they don't -- every single column is of a different sort. (In a couple of minutes I found <http://espn.go.com/nfl/statistics/player/_/stat/passing/sort/quarterbackRating/year/2009/seasontype/2> as another example of this: data can sensibly be compared between rows but not between columns, therefore the columns are different widths.) The only other reason I can think of for fixing column widths at all would be if multiple tables of the same type were ever vertically stacked, so they needed to be consistent with each other -- but that doesn't happen for this table either.

(On the side issue of whether the table should return to spanning both columns, I think that would be worthwhile -- I considered it a design goal of 2.0 that developers doing actual work with Launchpad should be able to use a Launchpad window alongside a terminal window on a standard-size screen, and it would be a shame to completely subvert that. But again, I don't think that's relevant to this bug.)