Comment 3 for bug 1324955
Revision history for this message
| Michael Sheldon (michael-sheldon) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Just to update this based on our conversation on IRC:
It doesn't look like it can be reliably handled solely in the keyboard; since all we have to go on are reports of focus changes, which happen asynchronously from the perspective of the keyboard and the app. So the app could have changed pages or processed the text field in some way before we can commit to it.
Rather than just fixing this in AbstractButton, it sounds like the best option would be to have TextFields explicitly call commit on the QML side, when losing focus; this will then block until the text has been committed.