unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: larsi@gnus.org, 56008@debbugs.gnu.org
Subject: bug#56008: 29.0.50; image-mode buffer scrolled down automatically
Date: Thu, 16 Jun 2022 16:57:42 +0300	[thread overview]
Message-ID: <834k0kr9rd.fsf@gnu.org> (raw)
In-Reply-To: <87o7yszqx6.fsf@gmail.com> (message from Visuwesh on Thu, 16 Jun 2022 18:49:49 +0530)

> Cc: 56008@debbugs.gnu.org
> From: Visuwesh <visuweshm@gmail.com>
> Date: Thu, 16 Jun 2022 18:49:49 +0530
> 
> >  So this seems like it's a redisplay bug and not a programming error
> > somewhere (I was wondering if some shr code was setting window-start
> > in the wrong window or something like that).
> 
> Yes, it is not specific to shr/eww.  That's what I alluded to by saying,
> 
>     This does not happen only with eww but in other scenarios as well.  But
>     I am unable to reproduce this behaviour in those scenarios as they are a
>     lot more involved.

No, this _is_ specific to eww and shr.  Well, in a way: shr.el does
something which directly causes this.  Stay tuned.





  reply	other threads:[~2022-06-16 13:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  4:01 bug#56008: 29.0.50; image-mode buffer scrolled down automatically Visuwesh
2022-06-16 12:04 ` Lars Ingebrigtsen
2022-06-16 12:19   ` Lars Ingebrigtsen
2022-06-16 13:19     ` Visuwesh
2022-06-16 13:57       ` Eli Zaretskii [this message]
2022-06-16 14:05         ` Lars Ingebrigtsen
2022-06-16 14:14           ` Visuwesh
2022-06-16 15:49             ` Eli Zaretskii
2022-06-16 16:55               ` Visuwesh
2022-06-16 17:11                 ` Eli Zaretskii
2022-06-16 17:23                   ` Visuwesh
2022-06-16 15:48           ` Eli Zaretskii
2022-06-16 16:58             ` Eli Zaretskii
2022-06-16 17:20               ` Visuwesh
2022-06-16 17:26                 ` Eli Zaretskii
2022-06-16 12:52   ` Eli Zaretskii

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=834k0kr9rd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=56008@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=visuweshm@gmail.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/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).