The most recent discussions around the focus UX are so far reaffirming that all components take focus on click out of the box, anything else is likely wrong, or otherwise a special case. Click/ touch needs to pass on focus so that subsequent keyboard navigation continues from that respective component. It also needs to steal focus to be able to hide the OSK which remains as long as any text input has focus. The only thing that is not given on click/touch is visual indication of focus - unless you use the keyboard to move around.
It's still possible that we find a case where this behavior needs to be more refined, but right now it's looking like the reported bug is making the wrong assumptions. You may want to validate your specific use cases with UX - in the bug report no concrete use case is given so I can't comment on that - but I'm happy to respond if you can be more specific. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1368390 Title: Button shouldn't steal focus by default Status in Canonical System Image: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Bug description: The upstream Button component has "activeFocusOnPress: false" as its default, that doesn't seem the case for our component, it probably should. Example "MainView { height: 600 width: 350 Column { anchors { left: parent.left right: parent.right } TextInput { anchors { left: parent.left right: parent.right } focus: true } Button { text: "click" /* don't steal focus, activeFocusOnPress: false*/ } } }" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
