bug#75183: 30.0.50; replace not working

[Eli Zaretskii <eliz@gnu.org>]

> Cc: 75183@debbugs.gnu.org
> Date: Mon, 30 Dec 2024 22:51:47 +0000
> From: jindam.vani--- via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> On 30 December 2024 14:22:23 UTC, Eli Zaretskii <eliz@gnu.org> wrote:
> >> Cc: 75183@debbugs.gnu.org
> >> Date: Mon, 30 Dec 2024 12:10:00 +0000
> >> From: jindam.vani--- via "Bug reports for GNU Emacs,
> >>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> >> 
> >> On 30 December 2024 07:10:11 UTC, Juri Linkov <juri@linkov.net> wrote:
> >> >> * excuse, please see this video at https://jumpshare.com/s/UZguLzkuu4rpKdagaLvi
> >> >> * to view video, we need chromium based web browser!
> >> >
> >> >Ah, this explains why it doesn't work in Firefox.
> >> >
> >> >>>> >It's _query_replace, so you need to confirm each replacement, e.g., by
> >> >>>> >pressing SPC.
> >> >>>> 
> >> >>>> * pressing spc or y doesnt have any effect
> >> >>>
> >> >>>Probably because there's no match for "q67" in the buffer.
> >> >
> >> >Could please type 'C-h l' afterwards to see what keys/events were emitted.
> >> 
> >>  <tool-bar> <isearch-forward> <isearch-forward> ;; isearch-forward
> >>  <touchscreen-begin>				;; ignore
> >>  <touchscreen-update> <touchscreen-update> <touchscreen-update> <touchscreen-end> ;; mouse-set-point
> >>  <text-conversion> ;; analyze-text-conversion
> >>  <text-conversion> ;; analyze-text-conversion
> >>  <left>		   ;; left-char
> >>  1		   ;; self-insert-command
> >>  <return>	   ;; exit-minibuffer
> >>  <tool-bar> <isearch-query-replace> <isearch-query-replace> ;; isearch-query-replace
> >>  <text-conversion>			 ;; analyze-text-conversion
> >>  <text-conversion>			 ;; analyze-text-conversion
> >>  <text-conversion>			 ;; analyze-text-conversion
> >>  <return>				 ;; exit-minibuffer
> >>  <touchscreen-begin> <touchscreen-begin> ;; ignore
> >>  <touchscreen-update> <touchscreen-update> <touchscreen-end> ;; view-echo-area-messages
> >>  ;; handle-switch-frame
> >>  ;; handle-switch-frame
> >>  ;; handle-switch-frame
> >>  ;; handle-switch-frame
> >>  <touchscreen-begin> <touchscreen-update> <touchscreen-update> <touchscreen-end> ;; mouse-set-point
> >>  C-h l ;; view-lossage
> >
> >So this is on Android or something? 
> 
> yes, android
> 
> > And the "disappearing keyboard"
> >is the soft keyboard used on mobile devices?  If so, perhaps Po Lu
> >could help us out?

Po Lu, could you please chime in and advise?