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

[Rito Rhymes]

Jon,

Following up on this point:

> 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.

In my previous reply I outlined the regressions I saw when applying the
CSS directly to the `<table>` elements, and why that led me to the
wrapper-based approach instead.

Given the regressions and rationale I already outlined, is the
wrapper-based approach acceptable?

Thanks,
Rito