Hi there,

In Table style, the width of each column is allocated depending on the maximum width of the content displayed in it. This is an excellent and effective system.

When using the 'group by field' function, however, that calculation is applied to each group individually, rather than globally. While that does mean that, technically, the columns in each group are the optimum width for the content in the group, it makes for an untidy page, and a confusing layout, as the fields are not aligned vertically throughout all the groups.

I've attached a screenshot to illustrate the situation.

is there a way to remedy this?

CommentFileSizeAuthor
Table-style-column-widths.jpg57.23 KBOsfer

Comments

merlinofchaos’s picture

merlinofchaos commented

The way to remedy this is via CSS; you'll need to apply some CSS to your table cells to ensure that they all have consistent width. Views has no idea how wide each cell should be and ordinarily just lets the browser decide, but in this situation that obviously doesn't work.

It is pretty easy to use CSS to pick out individual table cells and apply a width: property to them; using a percentage width is recommended, though do be careful that if a property has a value big enough to go over that it could expand beyond its stated width (but overflow: hide can help alleviate that).

Osfer’s picture

Osfer commented
Status: Active » Fixed

Thanks Merlin, it sounds like the only solution for consistent cell widths across field-grouped tables in a view is to hardcode the column widths. It's a shame that this precludes the intelligent width-determination based on the content in all the visible cells in a column, but I understand that it's not Views' responsibility. Thanks for clearing that up!

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.