public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Rito Rhymes <rito@ritovision.com>
To: konstantin@linuxfoundation.org
Cc: git@vger.kernel.org, rito@ritovision.com
Subject: [PATCH v1 6/6] improve mobile rendering of docutils tables
Date: Sat, 14 Mar 2026 03:59:22 -0400	[thread overview]
Message-ID: <20260314075922.67391-7-rito@ritovision.com> (raw)
In-Reply-To: <20260314075922.67391-1-rito@ritovision.com>

On narrow viewports, docutils tables become hard to read: the releases
table compresses too tightly, and the signatures fingerprint values
wrap and lose scanability.

Both /releases.html and /signature.html use table.docutils, and their
cells contain data values (versions, dates, fingerprints) rather than
sentence prose. Keep mobile behavior consistent with desktop by
treating these as single-line values and preserving readability.

Make docutils tables horizontally scrollable within their container so
cells can keep single-line values without forcing column collapse or
value wrapdown on narrow viewports.

Adjust border drawing for the scrollable table state by resetting
default cell borders and reapplying explicit grid edges to avoid
uneven/doubled outer borders.

Signed-off-by: Rito Rhymes <rito@ritovision.com>
---
 korgi/static/css/main.css | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/korgi/static/css/main.css b/korgi/static/css/main.css
index 16d97cd..04955c6 100644
--- a/korgi/static/css/main.css
+++ b/korgi/static/css/main.css
@@ -382,6 +382,22 @@ dt {
         margin: 1em;
         padding: 1em;
     }
+    table.docutils {
+        display: block;
+        overflow-x: auto;
+        -webkit-overflow-scrolling: touch;
+        width: 100%;
+    }
+    table.docutils th,
+    table.docutils td {
+        white-space: nowrap;
+        padding: 0 5px;
+        border: 1px solid #ccc;
+        border-collapse: collapse;
+    }
+    table.docutils > caption {
+        padding-left: 5px;
+    }
     pre,
     .literal-block {
         white-space: pre;
-- 
2.51.0


      parent reply	other threads:[~2026-03-14  7:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13  6:52 GitGitGadget's website is responsive, how about kernel.org? Johannes Schindelin
2026-03-13 13:04 ` Konstantin Ryabitsev
2026-03-13 13:14   ` Rito Rhymes
2026-03-13 13:16     ` Konstantin Ryabitsev
2026-03-13 13:56       ` Rito Rhymes
2026-03-13 15:58       ` Junio C Hamano
2026-03-14  6:20         ` Rito Rhymes
2026-03-14 16:48           ` Junio C Hamano
2026-03-14 18:54             ` Rito Rhymes
2026-03-16 14:58               ` Konstantin Ryabitsev
2026-03-16 17:14                 ` Rito Rhymes
2026-03-14  7:59   ` [PATCH v1 0/6] Allow site layouts to render properly on mobile devices Rito Rhymes
2026-03-14  7:59     ` [PATCH v1 1/6] add viewport meta tag for proper mobile rendering Rito Rhymes
2026-03-14  7:59     ` [PATCH v1 2/6] prevent wrapped headings from overlapping with text above it Rito Rhymes
2026-03-14  7:59     ` [PATCH v1 3/6] add 848px mobile banner adjustments to prevent overflow Rito Rhymes
2026-03-14  7:59     ` [PATCH v1 4/6] add responsive extras and footer layout adjustments to contain overflow Rito Rhymes
2026-03-14  7:59     ` [PATCH v1 5/6] contain horizontal overflow in core content and homepage releases layout Rito Rhymes
2026-03-14  7:59     ` Rito Rhymes [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260314075922.67391-7-rito@ritovision.com \
    --to=rito@ritovision.com \
    --cc=git@vger.kernel.org \
    --cc=konstantin@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox