W.r.t. “SDK might need adapting”, yes, this is largely a toolkit bug, because a toolkit is the most practical component to keep track of when “a text field becomes focused”. You can’t expect every app author to do this themselves, and you can’t expect users to learn+remember any alternative way of invoking the OSK.
An example flow would be: a. You tap in a text field. b. The toolkit says to the shell, “hey, I just focused a text field”. c. The shell checks whether an external keyboard is connected; it is. d. The shell checks whether the last character typed anywhere was with the OSK; it was. e. The shell therefore opens the OSK, and tells the toolkit that it’s done so… (…The shell also tells the toolkit what part of the window, if any, the OSK is obscuring. Then the toolkit says, “oh dear, that’s over top of the text field”, and scrolls the view to keep the field visible. But that’s another story.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1521518 Title: No way to invoke OSK when a hardware keyboard is connected Status in Canonical System Image: Confirmed Status in Canonical Pocket Desktop: Incomplete Status in ubuntu-keyboard: New Status in Ubuntu UX: Fix Committed Status in ubuntu-keyboard package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: There are mice on the market that claim to be keyboards as well. This inhibits OSK. We can try and find out how many keys they have and be smart about it. Regardless, we should have a way of forcing the OSK, especially on touch-enabled devices. Whether it's triggered by a touch (as opposed to mouse click) on the text area, or with a button in the text field (replaced with the clear icon when you start typing). Another option is the copy/paste dropdown. <https://goo.gl/CJ1YLB>: ------------ The on-screen keyboard should appear if: * no external keyboard is connected, and a text field becomes focused; or * an external keyboard is connected, but the most recent text typed anywhere was with the OSK, and a text field becomes focused; or * an external keyboard is connected, and the most recent text typed was with an external keyboard, but you tap in the already-focused text field. (App developers are responsible for emulating this behavior in typable areas that are not text fields.) ------------ == original description == 1. Boot nexus 7 2. In the login screen, test that OSK works by tapping the password textfield 3. swipe keyboard back down after testing it works 4. Turn on Bluetooth mouse to get a mouse cursor 5. Click on password textfield OSK doesn't pop up, touch tapping on the field doesn't bring up the OSK anymore either. ie. The login screen is not usable with mouse connected - cannot type in password via OSK since it doesn't come up when clicking the password textfield with mouse. See attached screenshot. Focus on textfield. Would expect OSK to show up. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1521518/+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
