I just find 2 bug in Keyman in the phone, and keyman in browser

Keyman
1

Hello
the first bug is that
When I set one sentence
nul ‘ABC’ + ‘D’ > ‘EFG’
on the keyman developper, this sentence will ‘kill’ the program and make the keyboard shut down on the phone.
I must change the sentence to
nul ‘ABC’ + any(D) > ‘EFG’
then everything will recover

the second bug is on the first page chrome browser, when I tried to searchin the browser.triggered some generation rule, the letter before the generation will be repeated and left many unnecessary letters behind. It will only happen in this page but won’t happen in a google search engine in www.google.com

Can you solve those bugs?
Thanks

2

Can you please open a separate issue for each of these bugs, including full details on how to reproduce them, including:

  • an example keyboard that triggers the bug
  • exact sequence of keystrokes to type to trigger the bug
  • the phone model and version (or operating system + version if appropriate)
  • application you are using when you encounter the bug
  • exact Keyman version you are using
  • any error messages that you see (screenshots, etc)
  • anything else that you think is relevant to the issue

Without those details, it will be impossible for us to investigate the bugs.

3

vietnam keyboard
in the iphone 13 mini
keyman version is 17.0.335
I post on facebook and twitter
The keyboard become blank, no error message .

I removed those rules with nul in the left in my keyboard, because it seems like every nul in the left will have the chance to trigger this bug when the consequence was triggered.
I think the relevant thing is when I meet the end of a word, when I push space or back space, it will happen. I think it is because the system is always automatically scanning the nul. When I meet the end of a word the system will keep scanning.

4

I’m sorry, but that is not enough information for us to reproduce the issue. Please follow the instructions I provided: we need a sequence of keystrokes that causes the issue.

The diagnosis is not really very useful to us: the exact steps to reproduce the issue is what we need.

A screenshot of the problem when it arises is also helpful (as I mentioned earlier).