James Moe wrote:
> On 2/1/21 2:17 PM, Robert Prins wrote:
>> I have the suspicion that this is caused by the fact that it uses a table
>> to format the page,
>>
> Set a max-width for the <td>.
A recipe for disaster.
The original mistake must be fixed instead, which is to put the whole
content in one big table. This should never be done (nowadays), especially
not if the content contains tables itself (because, AISB, a table is always
as wide as its widest row).
The situation there can be improved considerably by a few surgical moves
(BTDT):
1. Separate the big content table into two tables: one for the header
(for now), and one for the rest (from here: “content table”).
2. Put the header in a “header” element.
3. Move the content of .header into a “h1” element outside the table,
or at the very least wrap a “h1” element around it.
4. Move the navigation into a “nav” element outside the table.
5. Move .copyright outside the table as a “p” element (or “div” element
if it should contain “p”s), and remove the then-empty header table.
(Use floats if you absolutely must restore the original presentation.
[NOT recommended])
6. Put the content of the second table cell into a top-level “main” element
outside the content table. (The footer may be put into a top-level
“footer” element following the “main” element.)
7. Remove the then-empty content table.
8. Remove unnecessary right margins, and use CSS to add bottom borders and
margins as necessary.
This can even be done in the “Elements” tab of Chromium Dev Tools (BTDT).
When satisfied with the basic presentation, the new markup and CSS can
replace the old markup in the HTML and CSS file.
One of the many things then still on the to-do list is to fix the heading
hierarchy: There would be a “h1” element now, and there are “h3” elements in
the original content, but there is no “h2” element. Therefore, all “hX”
elements in the content have to be pulled up one level (h3 → h2, etc.)