commit | aff7c622da59699e02d8593a7d3f094900b051c4 | [log] [tgz] |
---|---|---|
author | Yohei Yukawa <yukawa@google.com> | Tue Jul 12 19:33:20 2022 -0700 |
committer | Yohei Yukawa <yukawa@google.com> | Tue Jul 12 19:33:20 2022 -0700 |
tree | 31b8cbec1250dfe01ca7fd114c090513236b3b45 | |
parent | 7e29c3b0d215c11d8c0da85c0d5d299111135137 [diff] |
Simplify IMMS#reportPerceptibleAsync() IMMS#mCurFocusedWindow is guaranteed to be associated with the current IME client process. As long as the calling process has the same window token, checking calledFromValidUserLocked() is just redundant and could even make it a bit unclear about what security model we are enforcing there. Bug: 34886274 Test: presubmit Change-Id: Iafb2b6d82fcccb4a33eceebff3d08b96fde8dc03