ubuntu-webapps-bugs team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

I see what’s happening: when
OxideQQuickWebViewPrivate::OnEditingCapabilitiesChanged() is initially
called, the value of the edit flags stored by the oxide webview is
correct (64 == SelectAll), but to retrieve the new value
OxideQQuickWebView::editingCapabilities() is called, and at that point
(component construction not complete yet), d->proxy_ is null, so
NoCapability (0) is returned.

In this light, emitting editingCapabilitiesChanged() in
OxideQQuickWebViewPrivate::completeConstruction() after the proxy has
been set sounds like a reasonable solution.

** Changed in: oxide
       Status: Confirmed => In Progress

** Changed in: webbrowser-app (Ubuntu)
       Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1586968

Title:
  Touch selection menu initially empty when focusing a text field

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  This appears to be 100% reproducible when the device has just been rebooted (not always reproducible otherwise).
  Steps to reproduce:
   1) browse to e.g. http://pastebin.ubuntu.com
   2) long press on one of the text fields ("Poster:" or "Content:")
   3) wait for the touch selection menu to appear next to the insertion handle (note that at the moment there is a bug in oxide which also triggers the page context menu, dismissing it will get you the touch selection menu)

  Expected result: assuming the clipboard is empty (device just
  rebooted), the "Select All" action is the only one visible in the
  touch selection menu.

  Current result: no action is visible, the menu is empty (see attached
  screenshot).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1586968/+subscriptions