Re: [PATCH v3] docs: wrap generated tables to contain small-screen overflow

["Rito Rhymes" <rito@ritovision.com>]

> So this CSS perhaps makes sense, but..
> But why do you need to inject another <div>, creating a whole
> new extension to do so, rather than just applying the CSS
> directly to the <table> elements? I just gave that a try, and
> it would appear to work just fine.

I did try applying it directly to the <table> elements.

That works on some pages, but in my testing it introduces
regressions on others that do not happen with the wrapper
approach.

For example, on `/bpf/standardization/instruction-set.html` at
400px viewport width, applying CSS scrollability directly to
the table creates an extra outer border with an awkward gap and,
more importantly, causes cell content to wrap much more
aggressively as the viewport narrows. Instead of letting the
table remain a readable horizontally scrollable unit, the text
gets squeezed into very narrow stacked lines that are harder
to read.

Screenshots:
Double border with gap issue highlighted -
https://github.com/user-attachments/assets/0ddacc4e-edce-4c14-b129-0940e8014d3f
Text wrapping issue highlighted -
https://github.com/user-attachments/assets/c172e126-7a4c-4b3c-a01c-fd4c8f08bda6

On `/arch/arc/features.html`, the wrapping issue is not present
and it scrolls fine, but I still see the double-border issue
there. In that case there is no gap, so it mainly looks like a
thicker border.

The reason for the wrapper is that it gives one consistent
overflow treatment across the existing table cases without
changing the table element's layout behavior directly. In my
testing, applying the scrollability to the <table> itself
works for some pages but regresses others, while the wrapper
approach avoids needing targeted CSS rules for different
rendered table cases.

If helpful, you're welcome to add any screenshots as a
comment on this GitHub issue:
https://github.com/ritovision/linux-kernel-docs/issues/1

Rito