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
Loading
Please register or sign in to comment