unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Noé Lopez via Guix-patches via" <guix-patches@gnu.org>
To: 75296@debbugs.gnu.org
Cc: sirgazil@zoho.com
Subject: [bug#75296] [PATCH website] website: blog: Avoid long words overflowing in post previews.
Date: Fri, 03 Jan 2025 13:56:45 +0100	[thread overview]
Message-ID: <87ed1koy2a.fsf@xn--no-cja.eu> (raw)
In-Reply-To: <20250102183516.17026-1-sirgazil@zoho.com>

Hi,

I think “overflow-wrap: break-word;” would be more appropriate, as it
does not cut off information or letters in half.

Good evening,
Noé

> From: Luis Felipe <sirgazil@zoho.com>
> 
> This prevents long, unbreakable text (e.g. a commit hash) in post
> previews, from overflowing and overlapping the content of other
> previews.
> 
> * website/themes/initial/css/item-preview.css (.item-preview): Hide
> overflow.
> ---
>  website/themes/initial/css/item-preview.css | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/website/themes/initial/css/item-preview.css b/website/themes/initial/css/item-preview.css
> index 16e698f..750047a 100644
> --- a/website/themes/initial/css/item-preview.css
> +++ b/website/themes/initial/css/item-preview.css
> @@ -5,6 +5,7 @@
>  .item-preview:visited {
>      color: #4D4D4D;
>      display: block;
> +    overflow: hidden;
>      padding: 10px 15px;
>      text-align: left;
>  }
> 
> base-commit: 53f18814bd231acb5f452de8b511d3260013ca79
> -- 
> 2.46.0




  reply	other threads:[~2025-01-03 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-02 18:35 [bug#75296] [PATCH website] website: blog: Avoid long words overflowing in post previews sirgazil--- via Guix-patches via
2025-01-03 12:56 ` Noé Lopez via Guix-patches via [this message]
2025-01-03 15:17   ` Luis Felipe via Guix-patches via
2025-01-04 18:23 ` [bug#75296] [PATCH website v2] website: blog: Prevent content from " sirgazil--- via Guix-patches via
2025-01-06 12:24   ` bug#75296: " pelzflorian (Florian Pelz)

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ed1koy2a.fsf@xn--no-cja.eu \
    --to=guix-patches@gnu.org \
    --cc=75296@debbugs.gnu.org \
    --cc=noe@xn--no-cja.eu \
    --cc=sirgazil@zoho.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).