| commit | af4caa60064d95aeffc7ab81095a269893f5f2a1 | [log] [tgz] |
|---|---|---|
| author | Keisuke Kuroyanagi <ksk@google.com> | Mon Feb 29 12:53:58 2016 -0800 |
| committer | Keisuke Kuroyanagi <ksk@google.com> | Tue Mar 08 04:58:46 2016 +0000 |
| tree | 2e58f3467bcaa7fd85b5e0b4a3c2d61f87881b5f | |
| parent | d319450307fcbd1f3dd99bf647c2c0281eb18e34 [diff] |
Call View#setHasTransientState in TextView#spanChange. setHasTransientState(true) and setHasTransientState(false) have to be coupled, but they were not always coupled in TextView. e.g. when we fire PROCESS_TEXT intent. With this CL, TextView calls setHasTransientState() always when selection is created or cleared to make sure 2 setHasTransientState calls are always coupled. Bug: 27409041 Change-Id: Ib454b0fbbc2c2f8d19818f154f415c4a5d7e2d7e