public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH htdocs] download: use <wbr> to break up some long <pre> text
Date: Fri, 22 Dec 2023 08:51:02 -0700	[thread overview]
Message-ID: <875y0q2q3d.fsf@tromey.com> (raw)
In-Reply-To: <20231219102817.17546-1-vapier@gentoo.org> (Mike Frysinger's message of "Tue, 19 Dec 2023 05:28:17 -0500")

>>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:

Mike> These URLs with parenthetical asides can generate very wide text on
Mike> smaller devices which makes scrolling/panning a pain.  Use <wbr> in
Mike> a few places to let the browser know it may add line breaks when
Mike> needed.  On small devices, we get much more comfortable view, while
Mike> on desktops, things look exactly the same as before.

TIL <wbr>.
Anyway it seems fine.  Thanks for doing this.

Tom

      reply	other threads:[~2023-12-22 15:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 10:28 Mike Frysinger
2023-12-22 15:51 ` Tom Tromey [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=875y0q2q3d.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).