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/1] docs: allow long unbroken headings to wrap and prevent overflow
Date: Sat, 21 Mar 2026 10:48:55 -0400 [thread overview]
Message-ID: <20260321144855.30429-2-rito@ritovision.com> (raw)
In-Reply-To: <20260321144855.30429-1-rito@ritovision.com>
Some documentation pages contain long headings with unbroken strings
that can exceed the content width and cause page-wide horizontal
overflow.
Allow headings to wrap when needed so they stay within the content
column and do not break page layout.
Signed-off-by: Rito Rhymes <rito@ritovision.com>
---
Documentation/sphinx-static/custom.css | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/sphinx-static/custom.css b/Documentation/sphinx-static/custom.css
index db24f4344..14711c7be 100644
--- a/Documentation/sphinx-static/custom.css
+++ b/Documentation/sphinx-static/custom.css
@@ -8,6 +8,13 @@ div.body h1 { font-size: 180%; }
div.body h2 { font-size: 150%; }
div.body h3 { font-size: 130%; }
div.body h4 { font-size: 110%; }
+/*
+ * Let long headings wrap before they overflow page layout.
+ */
+div.body h1, div.body h2, div.body h3, div.body h4,
+div.body h5, div.body h6 {
+ overflow-wrap: anywhere;
+}
/* toctree captions are styled like h2 */
div.toctree-wrapper p.caption[role=heading] { font-size: 150%; }
--
2.51.0
next prev parent reply other threads:[~2026-03-21 14:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 14:48 [PATCH 0/1] docs: examples of pages affected by heading overflow Rito Rhymes
2026-03-21 14:48 ` Rito Rhymes [this message]
2026-03-21 21:32 ` [PATCH 1/1] docs: allow long unbroken headings to wrap and prevent overflow Randy Dunlap
2026-03-21 21:31 ` [PATCH 0/1] docs: examples of pages affected by heading overflow Randy Dunlap
2026-03-22 12:14 ` Rito Rhymes
2026-03-22 19:29 ` Randy Dunlap
2026-03-22 19:57 ` Rito Rhymes
2026-03-22 19:09 ` [PATCH v2 " Rito Rhymes
2026-03-22 19:09 ` [PATCH v2 1/1] docs: allow long unbroken headings to wrap and prevent overflow Rito Rhymes
2026-03-23 15:30 ` [PATCH v3] " Rito Rhymes
2026-03-25 19:04 ` Jonathan Corbet
2026-03-25 21:32 ` Rito Rhymes
2026-03-25 21:46 ` Rito Rhymes
2026-03-25 22:04 ` Jonathan Corbet
2026-03-26 17:00 ` Rito Rhymes
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=20260321144855.30429-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