unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ralph Schleicher <rs@ralph-schleicher.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 47705@debbugs.gnu.org
Subject: bug#47705: [PATCH] EWW: Customize display of images
Date: Mon, 12 Apr 2021 19:36:15 +0200	[thread overview]
Message-ID: <86o8ejmmls.fsf@lima.oberreute.mueller-schleicher.de> (raw)
In-Reply-To: <87wnt7zyph.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 12 Apr 2021 10:36:26 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

>> Additionally, images or ALT texts are always displayed on a line by
>> itself.  This may waste a lot of vertical space, e.g. when displaying
>> the Common Lisp HyperSpec.  The attached patch fixes these issues.
>
> But not this bit.
[...]
> shr should instead include images in-line if they are "small" -- i.e.,
> if they've got a height that's somewhat comparable to the line height,
> but not otherwise.
>
> This sounds like trivial thing to do, but it's not -- we don't know the
> size of the images until we load them (usually), and shr doesn't to
> re-flowing at all.
>
> shr could do inline images if the images have known width/heights (and
> the images are "small"), though.  Patches welcome.

I see your point.  Would it be acceptable if, as a first step, inlining
of images is combined with shr-inhibit-images non-nil?  Then we know
that the ALT texts fit into a line.

-- 
Ralph






  reply	other threads:[~2021-04-12 17:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-11 10:15 bug#47705: [PATCH] EWW: Customize display of images Ralph Schleicher
2021-04-12  8:36 ` Lars Ingebrigtsen
2021-04-12 17:36   ` Ralph Schleicher [this message]
2021-04-13  7:33     ` Lars Ingebrigtsen
2021-04-13 21:06       ` Ralph Schleicher
2021-04-13 22:08         ` Jose A. Ortega Ruiz
2021-04-14  8:38         ` Lars Ingebrigtsen
2021-04-14 19:27           ` Ralph Schleicher

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=86o8ejmmls.fsf@lima.oberreute.mueller-schleicher.de \
    --to=rs@ralph-schleicher.de \
    --cc=47705@debbugs.gnu.org \
    --cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).