From: Jonathan Corbet <corbet@lwn.net>
To: Rito Rhymes <rito@ritovision.com>, linux-doc@vger.kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org, rdunlap@infradead.org,
Rito Rhymes <rito@ritovision.com>
Subject: Re: [PATCH v3 1/2] docs: allow long links to wrap per character to prevent page overflow
Date: Wed, 25 Mar 2026 13:15:16 -0600 [thread overview]
Message-ID: <87ecl7g1q3.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260323152428.30483-1-rito@ritovision.com>
Rito Rhymes <rito@ritovision.com> writes:
> 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.
>
> Examples:
> https://docs.kernel.org/6.15/firmware-guide/acpi/non-d0-probe.html
> https://docs.kernel.org/6.15/arch/x86/earlyprintk.html
>
> Signed-off-by: Rito Rhymes <rito@ritovision.com>
> Assisted-by: Codex:GPT-5.4
> ---
> v3: add latest public versioned URL examples to the patchlog
>
> Documentation/sphinx-static/custom.css | 5 +++++
> 1 file changed, 5 insertions(+)
With these two I at least see the problem - on Chrome, at least; Firefox
does a better job of it. Again I'm not convinced this is optimal, but
I've applied them as being better than what we have.
Thanks,
jon
prev parent reply other threads:[~2026-03-25 19:15 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 ` [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 [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=87ecl7g1q3.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rito@ritovision.com \
--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