touch-packages team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

** Description changed:

  When launching the webapp container, the webview that is instantiated
- initially doesn’t have active focus (I don’t know which item does). The
- ancestor chain of the WebView should be comprised of FocusScopes only,
- not bare Items (Loaders are focus scopes, so they are OK), and the top-
- level ancestor should have focus.
+ initially doesn’t have active focus (the window’s QQuickRootItem does).
+ The ancestor chain of the WebView should be comprised of FocusScopes
+ only, not bare Items (Loaders are focus scopes, so they are OK), and the
+ top-level ancestor should have focus.
  
  Note: I came across this issue while working on
  https://code.launchpad.net/~osomon/webbrowser-app/context-menu-
  focus/+merge/280759, autopilot tests should verify that the webview
  initially has active focus.

-- 
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/1532739

Title:
  [webapp-container] WebView initially doesn’t have active focus

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When launching the webapp container, the webview that is instantiated
  initially doesn’t have active focus (the window’s QQuickRootItem
  does). The ancestor chain of the WebView should be comprised of
  FocusScopes only, not bare Items (Loaders are focus scopes, so they
  are OK), and the top-level ancestor should have focus.

  Note: I came across this issue while working on
  https://code.launchpad.net/~osomon/webbrowser-app/context-menu-
  focus/+merge/280759, autopilot tests should verify that the webview
  initially has active focus.

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