On 2019-W36-5 12:08 +0200, Martin Husemann wrote:
On Thu, Sep 05, 2019 at 04:26:05PM -0700, Constantine A. Murenin wrote: > Is the objection against any borders for any tables in the first place, or > specifically against the border around each td element (e.g., against two > 1px lines separated by a bit of whitespace around each cell)? No particular objection to anything, just the concrete example looks ugly and wastes space now.
Which space is being wasted? If you apply the code from the prior message w/ border-collapse: collapse, then there's actually going to be less space between the cells even with the border than was before the original change. (This was why I've tried to add a near-white 3px border to th table header elements, to compensate.)
> I think tables without borders just look wrong, although in the specific > example you mention the table is not generated correctly, because the "CVS > tag" doesn't actually span all the rows that it refers to, resulting in many > empty cells, so, it's certainly not the best application of the border. > Do you know where the code for this script is, perhaps we could fix the > script to generate the table correctly? I can fix it (with help from admins who need to install the updated script). I can also make it use its own variant of the style w/o borders again, if general consensus is to have borders by default.
I'm not exactly sure if there's a consensus either way. However, I don't see any particular reason for builds.cgi to not have borders on its table if other tables do have borders. Lack of the border on builds.cgi looks particularly messy when the cells with the date/time have line-wrapping between the date and the time, as happens in smaller windows / screens.
Currently, it would seem that most tables on our site are missing borders for some reason, although the guide does have the old-style `<table border=1` for all of its tables, and CVSweb does have borders, too.
I think each table that has table-like data should have thin and light borders to improve readability and formatting. Sites like Apple.com can get away with few or no borders because they put a riduculous amount of whitespace between everything, and limit the information being presented in the first place, plus, they more often use lists instead of tables like we do, but since we're not in that boat, I think it'd make sense to have light thin borders instead of no borders at all.
C.