public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Rito Rhymes <rito@ritovision.com>
To: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, Rito Rhymes <rito@ritovision.com>
Subject: [PATCH 2/2] docs: allow long table reference links to wrap and prevent overflow
Date: Sat, 21 Mar 2026 14:08:41 -0400	[thread overview]
Message-ID: <20260321180841.10166-3-rito@ritovision.com> (raw)
In-Reply-To: <20260321180841.10166-1-rito@ritovision.com>

Some documentation pages contain docutils tables with reference links
that use long unbroken strings. Those strings can expand the table
width beyond the content column and cause page-wide horizontal
overflow.

Allow reference links in docutils tables in the main document body to
wrap when needed so the table stays within the content column and does
not break page layout.

Signed-off-by: Rito Rhymes <rito@ritovision.com>
---
 Documentation/sphinx-static/custom.css | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/sphinx-static/custom.css b/Documentation/sphinx-static/custom.css
index 4ec617d40..b41c54c71 100644
--- a/Documentation/sphinx-static/custom.css
+++ b/Documentation/sphinx-static/custom.css
@@ -154,6 +154,11 @@ a {
     overflow-wrap: anywhere;
 }
 
+/* Let rendered reference links in tables wrap when needed. */
+div.body table.docutils a.reference {
+    overflow-wrap: anywhere;
+}
+
 /* Make xrefs more universally visible */
 a.reference, a.reference:hover {
     border-bottom: none;
-- 
2.51.0


  parent reply	other threads:[~2026-03-21 18:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-21 18:08 [PATCH 0/2] docs: contain overflow from long links Rito Rhymes
2026-03-21 18:08 ` [PATCH 1/2] docs: allow long links to wrap per character to prevent page overflow Rito Rhymes
2026-03-21 18:08 ` Rito Rhymes [this message]
2026-03-22 19:20 ` [PATCH v2 0/2] docs: contain overflow from long links Rito Rhymes
2026-03-22 19:20   ` [PATCH v2 1/2] docs: allow long links to wrap per character to prevent page overflow Rito Rhymes
2026-03-22 19:20   ` [PATCH v2 2/2] docs: allow long table reference links to wrap and prevent overflow Rito Rhymes
2026-03-23 15:24 ` [PATCH v3 1/2] docs: allow long links to wrap per character to prevent page overflow Rito Rhymes
2026-03-23 15:24   ` [PATCH v3 2/2] docs: allow long table reference links to wrap and prevent overflow Rito Rhymes
2026-03-25  0:50     ` Randy Dunlap
2026-03-25  0:50   ` [PATCH v3 1/2] docs: allow long links to wrap per character to prevent page overflow Randy Dunlap
2026-03-25 19:15   ` Jonathan Corbet

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=20260321180841.10166-3-rito@ritovision.com \
    --to=rito@ritovision.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@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