To repro, run the compose demo app in an emulator, type some text into a BTF2 field, and then try to use the arrow keys to move the cursor. Observed on API 33 with tip-of-tree compose as of the time of filing.
This does _not_ happen with a real device when using arrow keys with device mirroring, or with a hardware keyboard. I think what's happening is the emulator maps arrow key events to DPAD events, which are what is handled specially by the Android onPreKeyEvent handler and blocked from getting to the regular key handling logic.
This also does not match EditText behavior. The emulator arrow keys move the cursor in EditText.
This line of code is where the physical keyboard will not support dpad and thus return false. The emulator seems to support dpad when using a computer's keyboard through it, so the focus manager code below it is reached and executed.
Description
This does _not_ happen with a real device when using arrow keys with device mirroring, or with a hardware keyboard. I think what's happening is the emulator maps arrow key events to DPAD events, which are what is handled specially by the Android onPreKeyEvent handler and blocked from getting to the regular key handling logic.
This also does not match EditText behavior. The emulator arrow keys move the cursor in EditText.