Project

General

Profile

Actions

tickets #163427

open

bad CSS?/JS? on https://en.opensuse.org/SDB:Linuxrc

Added by mrmazda 10 months ago. Updated 9 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Wiki
Target version:
-
Start date:
2024-07-07
Due date:
% Done:

0%

Estimated time:

Description

This overlapping on https://en.opensuse.org/SDB:Linuxrc in Chromium also happens in Falkon, SeaMonkey, Pale Moon & Firefox ESR 115.


Files

wikiBadCSS202407.png (261 KB) wikiBadCSS202407.png screenshot of inescapable overlapping text mrmazda, 2024-07-07 21:19
chromium_sdblinuxrc.png (136 KB) chromium_sdblinuxrc.png crameleon, 2024-07-13 21:40
firefox_sdblinuxrc.png (222 KB) firefox_sdblinuxrc.png crameleon, 2024-07-13 21:40
Actions #2

Updated by mrmazda 9 months ago

Unlike yours, my screenshot is not from the top of the page, where overlapping does not repro. Scroll down at least to below the text "You will probably never need any parameter except install. But in case you do, here is the complete list." to see problem.

Actions #3

Updated by crameleon 9 months ago

  • Assignee set to cboltz
Actions #4

Updated by cboltz 9 months ago

  • Status changed from New to Feedback

This is a known problem with the Linuxrc page, but unfortunately it's not that easy to fix.

To summarize: The page uses HTML tables with the parameter name in the first column, and explanations and examples in the second column. The parameter names are always a single (and sometimes a quite long) word, forcing the column to the width of the longest parameter name. Also, the examples in the second column are typically <pre>-formatted text which also enforces the column width. Sadly, as soon as the table got its width extended, all content honors that width - which is normal behaviour of HTML tables.

We could add __NOTOC__ to hide the table of contents, but while it would prevent the overlap by hiding the TOC, I doubt that this would be an improvement.

In theory we could add linebreaks in the <pre>-formatted texts. That would be ok and doable for comments, but adding linebreaks in examples would make things worse and hard to understand. (A quick check shows that the longest lines are not comments.)

If you have other/better ideas to improve the formatting, I'm all ears ;-)

Actions #5

Updated by mrmazda 9 months ago

When reading a book, and one wants to revisit the TOC, it's universally known exactly what to do: goto the front. In a web page, it's little different: hit the home key. There exists no compelling need of a TOC that is visible regardless of page position. That locked in place TOC of merely 10 items is virtually pure distraction, easily recovered, whilst absent top of page.

Actions

Also available in: Atom PDF