However, the previous CSS had a (non-default) table definition which provided cell borders and coloured rows as alternating stripes. This was useful for reading show details in the notes generated for Community News shows.
Now these tables can be confusing because the rows don't align well. A cell with a single line of text is in the centre of an adjacent cell with two lines of text. This could be resolved with borders, cell shading or 'top' alignment, preferable with all three!
The old table definition used id="t01".
The new CSS looks good.
However, the previous CSS had a (non-default) table definition which provided cell borders and coloured rows as alternating stripes. This was useful for reading show details in the notes generated for Community News shows.
Now these tables can be confusing because the rows don't align well. A cell with a single line of text is in the centre of an adjacent cell with two lines of text. This could be resolved with borders, cell shading or 'top' alignment, preferable with all three!
The old table definition used `id="t01"`.
davmo
changed title from New CSS makes some tables less readable to New CSS makes some tables less readable, and other issues2024-10-18 21:41:50 +00:00
rho_n
was assigned by davmo2024-10-18 21:46:32 +00:00
I just processed a show (4231) which had a lot of pieces of text (commands) using <code> tags. The font used with these commands is almost indistinguishable from the font used in the ordinary text. Previously there was a more distinct difference between the normal text and the <code> sections.
There might be a case for changing the background colour of <code> tagged text (as done on archive.org).
I just processed a show (4231) which had a lot of pieces of text (commands) using `<code>` tags. The font used with these commands is almost indistinguishable from the font used in the ordinary text. Previously there was a more distinct difference between the normal text and the `<code>` sections.
There might be a case for changing the background colour of `<code>` tagged text (as done on archive.org).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The new CSS looks good.
However, the previous CSS had a (non-default) table definition which provided cell borders and coloured rows as alternating stripes. This was useful for reading show details in the notes generated for Community News shows.
Now these tables can be confusing because the rows don't align well. A cell with a single line of text is in the centre of an adjacent cell with two lines of text. This could be resolved with borders, cell shading or 'top' alignment, preferable with all three!
The old table definition used
id="t01".New CSS makes some tables less readableto New CSS makes some tables less readable, and other issuesI just processed a show (4231) which had a lot of pieces of text (commands) using
<code>tags. The font used with these commands is almost indistinguishable from the font used in the ordinary text. Previously there was a more distinct difference between the normal text and the<code>sections.There might be a case for changing the background colour of
<code>tagged text (as done on archive.org).Fixed and merged into main