touch-packages team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

After a bit of investigation, I understand what’s going on: the Chrome
instance is a focus scope that proxies focus requests to the address
bar, and it’s itself contained in a FocusScope. Setting focus to true on
chrome doesn’t imply that the active focus will change, it only
guarantees that the next time the active focus is set on the enclosing
focus scope, chrome will receive it.

So the current code that does "chrome.focus = true" in the onTriggered
handler of the "find in page" action should really do
"chrome.forceActiveFocus()".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1508130

Title:
  'find in page' fails to focus address bar every second time

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  1. Open the Web Browser
  2. Open the Drawer widget on the top right corner
  3. Select Find In Page
  4. Confirm the address bar is focused (in find in page mode) and the keyboard appears
  5. Press Back to return to normal browsing view
  6. Open the Drawer widget again
  7. Select Find In Page again

  Expected result:

  The address bar (in find in page mode) is focused and the keyboard
  appears

  Actual result:

  Find in page mode is active but the address bar is not focused and the
  keyboard does not appear

  current build number: 152
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-10-18 22:11:48
  version version: 152
  version ubuntu: 20151016
  version device: 20150821-736d127
  version custom: 20150925-901-35-40-vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1508130/+subscriptions