diff options
| author | Feng Cao <fengcao@google.com> | 2021-02-04 15:05:41 -0800 |
|---|---|---|
| committer | TYM Tsai <tymtsai@google.com> | 2021-03-25 13:36:28 +0800 |
| commit | c8def0695b73b6ca5494ea28dda89db41edea060 (patch) | |
| tree | 6c5b408b569e7f98693157d44c1afa5cea8531a0 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 3be701e7670519336bddfd9f2837c19556d76de9 (diff) | |
Update the content capture text changed event merge logic
* This is only applicable when two consecutive CC events are
both TYPE_VIEW_TEXT_CHANGED event for the same view
* Before this change: we would merge if both events have
non-empty text. However, if the user types fast, CC will
not send the updates for individual word. Moreover, if the
user adds a word and then delete it fast, CC may not capture
the word since it'd be merged away.
* After this change, we change the criteria to consider whether
the current text has a ComposingSpan if it's a Spannable.
The logic is described in the code comment.
Bug: 181906241
Test: atest CtsContentCaptureServiceTestCases
Change-Id: I08d447f557f7e48ef34c5a6241c497db3ce4c5fc
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions