summaryrefslogtreecommitdiff
path: root/api/api.go
diff options
context:
space:
mode:
author Taran Singh <tarandeep@google.com> 2024-06-03 18:54:43 +0000
committer Taran Singh <tarandeep@google.com> 2024-06-04 21:41:00 +0000
commiteb0db5b066096cdb3e8eba8207570ebf7e2dbda4 (patch)
tree62ec11c9f7cdeb60375efabd0f36354805c886a4 /api/api.go
parent70a4f7e51240e3a61db1fcb76ac4dc09573b4700 (diff)
Fix order of binding result when using zeroJankProxy
When a new client gets bound to IME, the order of bind events are out of order: MSG_BIND arrives before MSG_START_INPUT_RESULT (with InputBindResult.result SUCCESS_WAITING_IME_SESSION). The order needs to be flipped so that sequence check doesn't mismatch in MSG_BIND. Fix: 330486656 Test: atest FlickerTestsIme Change-Id: I7ed08ed84217478f148cbaf89f1afcaa410c6bfe
Diffstat (limited to 'api/api.go')
0 files changed, 0 insertions, 0 deletions