© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
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)