Another observation that I should have added in the long comment: what I understand from reading the code is that the author of the component probably did not intend 1.2 to work that way. The way 1.2 TextField behaves is just a consequence of an excessive alias which made the initialization of TextField's activeFocusOnPress have another effect instead (i.e. set TextInput's activeFocusOnPress)
-- 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/1513897 Title: TextField regression/behavior change in 1.3 Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Having an AbstractButton as secondaryItem of a TextField used to not change the TextField focus status when pressing the button but with 1.3 it does (i.e. the TextField used to not gain focus when pressing on secondaryItem and now it does) Code at http://paste.ubuntu.com/13125887/ Is this an intended change or a behaviour regression? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1513897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
