webbrowser-app AP failures after UITK upgrade

According to our investigation the root problem lays somewhere in the OSK or in Qt input modul level.

Adding a Qt.inputMethod.show() to the addTab() function in the BrowserView will work the problem around. With that we could avoid reverting the UITK.

This bug was fixed in the package webbrowser-app - 0.23+14.10.20140505-0ubuntu1

---------------
webbrowser-app (0.23+14.10.20140505-0ubuntu1) utopic; urgency=low

  [ Olivier Tilloy ]
  * Work around a recent regression by forcing the OSK to show up when
    the address bar is being focused. (LP: #1316057)

webbrowser-app (0.23+14.04.20140428-0ubuntu1) trusty; urgency=low

  [ CI bot ]
  * Resync trunk

  [ Alberto Mardegan ]
  * Webapps: let SAML requests through SAML requests are used for
    instance by Google Apps for your domain; they are implemented as a
    HTTP redirect to a URL containing the query parameter called
    "SAMLRequest". Besides letting the request through, we must also add
    the SAML domain to the list of the allowed hosts. (LP: #1302780)

  [ Ubuntu daily release ]
  * New rebuild forced

webbrowser-app (0.23+14.04.20140422-0ubuntu1) trusty; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Alexandre Abreu ]
  * Fix the network dialog reload (LP: #1309138)
  * Oxide (and Chromium) does not inform of non user driven navigations
    (or more specifically redirects that would be part of an
    popup/webview load (after its been granted). Quite a few sites (e.g.
    Youtube), create popups when clicking on links (or following a
    window.open()) with proper youtube.com address but w/ redirection
    params, e.g.:
    http://www.youtube.com/redirect?q=http%3A%2F%2Fgodzillamovie.com%2F&
    redir_token=b8WPI1pq9FHXeHm2bN3KVLAJSfp8MTM5NzI2NDg3NEAxMzk3MTc4NDc0
    In this instance the popup & navigation is granted, but then a
    redirect happens inside the popup to the real target url (here
    http://godzillamovie.com) which is not trapped by a navigation
    requested and therefore not filtered. The only way to do it atm is
    to listen to url changes in popups & also filter there. (LP:
    #1294279)
 -- Ubuntu daily release <email address hidden> Mon, 05 May 2014 12:15:51 +0000

I did some investigation on what are the differences on the input elements (TextInput and TextEdit used in TextField and TextArea) and found that autoFocusOnPressed is the only difference on the component setup. In the previous setup we had this property untouched (its default value is true) and now we have it set to false. And seems this causes the problem.

I managed to reproduce the failure with a simple TextInput or TextEdit component whos autoFocusOnPressed is set to false.

inport QtQuick 2.0

Item {
    width: 100; height: 100
    Component.onCompleted: input.forceActiveFocus()

    TextInput {
        width: 100; height: 30
        text: "Here I am"
        autoFocusOnPressed: false
        onActiveFocusChanged: print("activeFocus=", activeFocus)
        onFocusChanged: print("focus=", focus)
    }
}

This example will show the cursor blinking in the text input, but OSK will not be shown ever.

I suspect OSK as first, and as second Qt QML implementation.