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 1/2] docs: allow long links to wrap per character to prevent page overflow
Date: Sat, 21 Mar 2026 14:08:40 -0400	[thread overview]
Message-ID: <20260321180841.10166-2-rito@ritovision.com> (raw)
In-Reply-To: <20260321180841.10166-1-rito@ritovision.com>

Some documentation pages contain long link text without natural
break points, which can force page-wide horizontal scroll overflow
on small screens.

Use overflow-wrap: anywhere for anchor text in the docs stylesheet so
links can wrap per character as a fallback when normal word boundaries
are unavailable.

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 db24f4344..4ec617d40 100644
--- a/Documentation/sphinx-static/custom.css
+++ b/Documentation/sphinx-static/custom.css
@@ -149,6 +149,11 @@ div.language-selection ul li:hover {
     background: #dddddd;
 }
 
+/* Let long link text wrap instead of forcing overflow. */
+a {
+    overflow-wrap: anywhere;
+}
+
 /* Make xrefs more universally visible */
 a.reference, a.reference:hover {
     border-bottom: none;
-- 
2.51.0


  reply	other threads:[~2026-03-21 18:08 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 ` Rito Rhymes [this message]
2026-03-21 18:08 ` [PATCH 2/2] docs: allow long table reference links to wrap and prevent overflow Rito Rhymes
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-2-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