[TIMOB-23805] iOS: Issue with 'TAB' button click while using ListView and Scrollable Views
| GitHub Issue | n/a |
|---|
| Type | Improvement |
|---|
| Priority | Medium |
|---|
| Status | Closed |
|---|
| Resolution | Not Our Bug |
|---|
| Resolution Date | 2017-03-03T17:13:13.000+0000 |
|---|
| Affected Version/s | Release 5.4.0, Release 5.2.2 |
|---|
| Fix Version/s | n/a |
|---|
| Components | iOS |
|---|
| Labels | n/a |
|---|
| Reporter | Neeraj Mishra |
|---|
| Assignee | Hans Knöchel |
|---|
| Created | 2016-08-22T23:35:52.000+0000 |
|---|
| Updated | 2017-03-24T19:01:20.000+0000 |
|---|
Description
Problem:
When user uses the external keyboard's 'tab' button to go the next input field while inputting text, the app is behaving weirdly(screen will be off-centered.) instead of going to the next text field.
Steps to reproduce:
1. Run KeyTest app in iPad simulator.
2. Click on a TextField in the first screen with value "View1 - Field00".
3. Click "Tab" in the Mac Keyboard or soft Keyboard.
Then the screen will be off-centered. Also, if we keep pressing it, it will be moving to next TextField in next page rather in same page.
If we remove the tag " ...." from top, it will stop distorting the screen on Tab click but even though TAB click behavior is not correct. It keeps moving to next screen instead of going to TextField in same screen.
We tried to build the app on both 5.2.2.GA(customer Environment) and 5.4.0.GA(support Environment), and we see the same behavior.
Expected Result:
Clicking on Tab should not distort the screen and Tab click should take the focus on next TextField in same Scrollable Page rather going to next page in Scrollable view.
Attachments
This may not be a bug. I don't think we support keyboard 'tab' key pressed because our sdk is primarily for mobile development that primarily uses the on-screen keyboard on each device. This is more a feature request or improvement. Also, a better alternative is to use the '<' '>' that's on the toolbar above the keyboard on an iOS device. is that working as expected?
Ok, so for the offset, it's definitely the
ScrollViewthat's caussing the issue. You cannot place aScrollableViewinside aScrollViewand handle scroll properly, since both would intercept each other. After that, I am able to focus the second field from the first field. But after that, the next row won't be focussed. This - on the other hand - is a native behavior which needs manual adjustment. I will try to update the example-code to set the field-order properly.Closing ticket with reference to the previous comments.