Affects Version/s: Release 5.0.2, Release 8.0.2
Fix Version/s: None
Windows Android SDK 3.5GA
Sprint:2016 Sprint 11 SDK, 2018 Sprint 16 SDK, 2016 Sprint 17 SDK, 2018 Sprint 18 SDK, 2018 Sprint 19 SDK, 2018 Sprint 20 SDK, 2018 Sprint 21, 2018 Sprint 22
While a TextArea object's property "editable" is set to false, end-users cannot tap to select text like how it works on iOS. This is a parity issue.
Note that the TextArea is not disabled. The end-user can scroll the content. The issue is that no cursor is shown and it's impossible for the end-user to make cursor selections. (However, the setSelection() method works and text selections can be made programmatically.)
Steps to reproduce:
- Build and run the below code on Android.
- Tap and hold on a word in the TextArea.
- Notice that no selection was made. (This is the issue.)
On iOS, if TextField property "editable" is set false, then the end-user is unable to tap to select text either. So, in this case, both Android and iOS are in parity. I think this is the "native" iOS behavior, although it is inconsistent with iOS' own TextArea behavior.
Titanium is calling setCursorVisible(false) in the Java TiUIText.handleKeyboard() method below.
But since iOS' TextField does not allow text selection while "editable" is false, Android should continue to call setCursorVisible(false) only for the single-line TextField case.