Handle tables with many columns

[alandefreitas]

Boost.URL has this table that's too large and ends up outside the area of the main content:

https://www.boost.org/doc/libs/master/doc/antora/url/reference.html

There should be a solution where we can scroll right or some other option.

Of course, we can also rethink this individual Boost.URL table format. We migrated it from previous QuickBook documentation. But I expect this problem to reoccur with other libraries.

[rbbeeston]

Tables are generally a pain to deal with in this format. My preferred method would be to allow the table to scroll inside the div, and not allow it to go outside the div, but there are other who are strongly opposed to that.

The alternatives would be to find ways to shrink the table to force it to conform to the size or allow the container div to expand, even if it goes outside of pre-set boundaries.

[cdw9]

I think it makes sense to have a horizontal scroll when necessary - it is already being done on the code blocks. It's also going to be needed on mobile devices.

Ultimately, the tables should be reviewed to see if the data actually needs to be in a table. In this case, it could be presented in a different way.

[cdw9]

I committed a fix, it's currently part of https://github.com/boostorg/boostlook/pull/43/commits

[rbbeeston]

One of the downsides to the way the data is handled is that we don't have much control over what we get to work with. So we have to do more of a "one size fits all" solution regarding tables.

Vinnie is not a fan of extra scrollbars within the document, so while adding scrolling is fine, try to hide or minimise the scrollbars themselves.