[Ubuntu-webapps-bugs] [Bug 1389336] Re: Use geoclue-2.0
I've proposed a change to geoip.ubuntu.com to provide a Google/Mozilla Location Service compatible API. This means we can configure Geoclue 2.0 to use this service. Then I propose we drop geoclue (1.0) and ubuntu-geoip from the archive. ** Changed in: webkit2gtk (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Triaged Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Fix Released Status in webkitgtk package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Debian: Fix Released Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1389336] Re: Use geoclue-2.0
** Also affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Triaged Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: New Status in webkitgtk package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Debian: Fix Released Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1586968] Re: Touch selection menu initially empty when focusing a text field
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
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
[Ubuntu-webapps-bugs] [Bug 1586968] Re: Touch selection menu initially empty when focusing a text field
I instrumented the webview to print the initial value of
editingCapabilities (at Component.onCompleted) and to print the new
value whenever it changes. This is what I’m seeing:
qml: EDITING CAPS: 0
qml: INITIAL EDITING CAPS: 64
The value of editingCapabilities changes once (to 0) before component
completion. At component completion, the value has changed again (64 ==
SelectAll), but the corresponding changed signal hasn’t been emitted,
which explains why the touch selection menu isn’t aware of the SelectAll
capability, and is displayed empty. This looks like a bug in oxide.
** Also affects: oxide
Importance: Undecided
Status: New
--
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:
New
Status in webbrowser-app package in Ubuntu:
Triaged
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
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
