ubuntu-sdk-bugs team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

I still haven’t gotten to the bottom of things, but I found a workaround
in the browser: in Browser.qml at line 70¹, if I comment out the call to
contentsContainer.forceActiveFocus(), the issue goes away.

The underlying bug still exists in the UITK.

I’m marking webbrowser-app also affected, and linking a branch that has
the workaround.


¹ https://bazaar.launchpad.net/~phablet-team/webbrowser-app/trunk/view/head:/src/app/webbrowser/Browser.qml

** Also affects: webbrowser-app (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: webbrowser-app (Ubuntu)
     Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => High

** Changed in: webbrowser-app (Ubuntu)
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1545802

Title:
  activeFocus not being forwarded to TextInput inside TextField

Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Haven’t managed to reproduce with a standalone example yet, but I can
  reliably reproduce the following issue with the browser app on a
  tablet with a bluetooth keyboard connected (this needs to be on a
  tablet so that the wide layout of the app is used, for example with a
  Nexus 7 (flo) in landscape orientation):

   1) launch the browser app with a bluetooth keyboard attached and ensure that the current tab is not a new tab
   2) press Ctrl+T to open a new tab

  Expected result: the address bar gets active focus so that the user
  can start entering a URL right away

  Current result: the address bar gets active focus for a fraction of a
  second, then looses it. When that happens, pressing Ctrl+L (which
  forces focus on the address bar) doesn’t fix it.

  
  I added some debugging to the browser (printing Window.activeFocusItem whenever it changes), and it appears that when initially forcing active focus on the address bar the QQuickTextInput inside it gets active focus, then looses it. At that point the activeFocusItem is the TextField, but it doesn’t forward it to QQuickTextInput inside itself.

  That situation can be remedied by using a bluetooth mouse to click on
  the address bar, which restores active focus on the QQuickTextInput.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1545802/+subscriptions