first of all major thanks for creating Archon. Being able to run Android apps on my home machine is just marvelous.
With that said, I think I am experiencing some regressions with keyboard input after switching to the latest Archon Chrome runtime release (2.1.0 beta on x86-64 Chrome for Linux).
Where the backspace and return key would reliably perform their respective actions on Archon 1.2, with the 2.1.0 beta release their behaviour seems to be far less predictable. At times the Return key will insert a line-break for instance, while at others it might just result in an invisible character in an entry field.
As far as the backspace key is concerned: It will sometimes delete characters, but most of the time it doesn't seem to be working anymore.
As you can see I am not quite certain on the exact circumstances that trigger these issues, but I thought it might be worth it filing a report anyway. Maybe there's been some changes to how keyboard input is handled in 2.1.0 that would explain these bugs?
In any case, thanks again for all the work and effort you put into Archon and thanks in particular for giving this bug report a read!
Hi there,
first of all major thanks for creating Archon. Being able to run Android apps on my home machine is just marvelous.
With that said, I think I am experiencing some regressions with keyboard input after switching to the latest Archon Chrome runtime release (2.1.0 beta on x86-64 Chrome for Linux).
Where the backspace and return key would reliably perform their respective actions on Archon 1.2, with the 2.1.0 beta release their behaviour seems to be far less predictable. At times the Return key will insert a line-break for instance, while at others it might just result in an invisible character in an entry field.
As far as the backspace key is concerned: It will sometimes delete characters, but most of the time it doesn't seem to be working anymore.
As you can see I am not quite certain on the exact circumstances that trigger these issues, but I thought it might be worth it filing a report anyway. Maybe there's been some changes to how keyboard input is handled in 2.1.0 that would explain these bugs?
In any case, thanks again for all the work and effort you put into Archon and thanks in particular for giving this bug report a read!