Hi Robert, The gist of the issue is OSK not popping up when js sets the focus in a text field. I dont think that having a way to programatically popup the OSK w/o a given "target" (text input field, etc.) is sound as a use case for a given API. It opens the gate for quite a few edge cases and adds quite a bit of complexity to have a reliable interface. It does not even work in QML afaik (you need a text field and can only hide() the inputMethod).
The issue w/ js focus not triggering the OSK is a known one (there is an upstream bug): https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1220264 There are no way around it atm, but it might change in the near future though. On Tue, Mar 25, 2014 at 9:43 AM, Robert Schroll <rschr...@gmail.com> wrote: > > I also don't know how to detect whether the user has a physical keyboard, > so we'd be stuck with this for all devices. This will change soon, when the new application api lands. you'll be able to detect the presence of the OSK, > If I'm going to go through the work of building a work around, I wonder if > it's better to write my own QML wrapper, instead of relying on > ubuntu-html5-app-launcher, and create my own javascript hooks to show and > hide the keyboard. > > BTW, there is a bug about this now: https://bugs.launchpad.net/ > ubuntu-html5-theme/+bug/1296462 > > Robert > >
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
