All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org,
	Clinton Phillips <clintdotphillips@gmail.com>,
	Daniel Lundberg Pedersen <dlp@qtec.com>,
	Hans Verkuil <hverkuil+cisco@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Petr Vorel <pvorel@suse.cz>, Randy Dunlap <rdunlap@infradead.org>,
	Rito Rhymes <rito@ritovision.com>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] docs: custom.css: don't limit randering to old 800px monitors
Date: Fri, 10 Jul 2026 09:27:23 -0600	[thread overview]
Message-ID: <87fr1qn9us.fsf@trenco.lwn.net> (raw)
In-Reply-To: <1950557405f1150acb1de50de1801f2413223b87.1783673996.git.mchehab+huawei@kernel.org>

Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:

> Right now, base.css style imposes a maximum limit of 800 horizontal
> pixels to be compatible with very old SVGA monitors.
>
> Remove such artificial limit, letting the output to be adjusted to
> the browser windows size.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
>  Documentation/sphinx-static/custom.css | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/sphinx-static/custom.css b/Documentation/sphinx-static/custom.css
> index 5aa0a1ed9864..1055db7dc1dd 100644
> --- a/Documentation/sphinx-static/custom.css
> +++ b/Documentation/sphinx-static/custom.css
> @@ -3,6 +3,8 @@
>   * CSS tweaks for the Alabaster theme
>   */
>  
> +div.body {  max-width: none; }
> +

800px is clearly a dumb limit, I have no problem changing that.  Going
to arbitrary width doesn't seem good for readability, though.  What do
you think about, instead, setting a limit in a resolution-independent
say, to (say) 60em?

Thanks,

jon

  reply	other threads:[~2026-07-10 15:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10  9:00 [PATCH] docs: custom.css: don't limit randering to old 800px monitors Mauro Carvalho Chehab
2026-07-10 15:27 ` Jonathan Corbet [this message]
2026-07-10 19:19   ` Mauro Carvalho Chehab
2026-07-10 19:52     ` Jonathan Corbet
2026-07-10 22:10       ` Mauro Carvalho Chehab
2026-07-11  7:48         ` Mauro Carvalho Chehab

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=87fr1qn9us.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=clintdotphillips@gmail.com \
    --cc=dlp@qtec.com \
    --cc=hverkuil+cisco@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=pvorel@suse.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.