Arrow key within a text field should not move to next component
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Canonical System Image |
High
|
Zoltan Balogh | ||
| ubuntu-ui-toolkit (Ubuntu) |
Undecided
|
Unassigned | ||
| unity8 (Ubuntu RTM) |
High
|
Unassigned |
Bug Description
using keyboard/arrow keys in the store: when user reaches the end of the final written word hit right arrow on keyboard and screen moves to the next section. Similarly When navigating text field with arrow keys, arrow keys cause pagination to occur
I understand this may be the default in Qt but not the desired UX behavior.
description: | updated |
Changed in canonical-devices-system-image: | |
assignee: | nobody → Zoltan Balogh (bzoltan) |
importance: | Undecided → High |
milestone: | none → ww08-2016 |
status: | New → Confirmed |
Changed in ubuntu-ui-toolkit (Ubuntu): | |
assignee: | nobody → Zsombor Egri (zsombi) |
importance: | Undecided → High |
status: | New → Confirmed |
Zoltan Balogh (bzoltan) wrote : | #1 |
affects: | ubuntu-ui-toolkit (Ubuntu) → unity8 (Ubuntu RTM) |
Changed in unity8 (Ubuntu RTM): | |
assignee: | Zsombor Egri (zsombi) → nobody |
Andrea Bernabei (faenil) wrote : | #2 |
I believe this is the way QQuickTextInput is implemented.
What happens here is that when the cursor reaches beginning/end of the text content, it ignores the following left/right key event. That means the key event propagates to the parent. The scope receives that event and handles it, thus changing the selected item in the view.
I think there are many ways to handle this, one being that the SDK component may stop the event from propagating when the text field is focused.
PS: this is probably related. https:/
Changed in canonical-devices-system-image: | |
milestone: | ww08-2016 → 11 |
Launchpad Janitor (janitor) wrote : | #3 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in ubuntu-ui-toolkit (Ubuntu): | |
status: | New → Confirmed |
Changed in canonical-devices-system-image: | |
milestone: | 11 → backlog |
The text input components of the UITK does not force the focus to the next text input. In this case it could be the scope what forces the foces.