What steps will reproduce the problem?
1. In Chrome on OS X, type ctrl-a
2.
3.
What is the expected output? What do you see instead?
I would expect the Ctrl-a code sequence to be sent to the wifi keyboard.
Instead, Chrome seems to interpret it -- probably to mean go to the beginning
of line. Same thing with ctrl-e (end of line). But some control key sequences
do work, e.g. ctrl-L
I tried Firefox on OS X, and I lose even more control key sequences. Same with
Safari
What version of the product are you using? On what operating system?
2.3.5, Android 4.3 on Nexus 7. Chrome 29 on OS X 1.8.4
Please provide any additional information below.
Original issue reported on code.google.com by huyz...@gmail.com on 6 Sep 2013 at 8:58
Original issue reported on code.google.com by
huyz...@gmail.com
on 6 Sep 2013 at 8:58