GNU bug report logs -
#51794
29.0.50; invalid input events generated from a mouse click for the tab bar
Previous Next
Reported by: Mark Kennedy <mark.t.kennedy <at> gmail.com>
Date: Fri, 12 Nov 2021 21:04:01 UTC
Severity: normal
Found in version 29.0.50
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #17 received at 51794 <at> debbugs.gnu.org (full text, mbox):
i'm willing to attempt to debug it myself but not via the -Q route. i
prefer to focus on where the bad input event stream is being created.
any suggestions about where to put an elisp or C breakpoint to go
after this?
/mark
On Sat, Nov 13, 2021 at 9:41 AM Eli Zaretskii <eliz <at> gnu.org> wrote:
>
> [PLEASE USE REPLY ALL TO REPLY, SO THAT THE BUG TRACKER IS CC'ED.]
>
> > From: Mark Kennedy <mark.t.kennedy <at> gmail.com>
> > Date: Sat, 13 Nov 2021 08:50:08 -0500
> >
> > reproducing from -Q is a nightmare. your comment that it did not
> > recognize the part of the window frame is what i want to focus on.
> > the window containing the scala mode buffer contains tab-bar tabs. i
> > am clicking in either a tab (on the close icon) or to the right of the
> > tab list on the "open new empty tab" icon (still within the tab bar).
> > how could that generate the <nil> input event?
>
> I don't know. That's why I asked for a recipe: to try debugging it
> myself. If it isn't practical to provide a recipe, you will have to
> debug it on your system.
This bug report was last modified 3 years and 185 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.