Public bug reported:
The following example illustrates the problem:
import QtQuick 2.4
import com.canonical.Oxide 1.15
WebView {
url: "http://www.w3schools.com/tags/tryit.asp?filename=tryhtml_textarea";
Component.onCompleted: console.log("initial editing caps:",
editingCapabilities)
onEditingCapabilitiesChanged: console.log("editing caps changed:",
editingCapabilities)
}
When run in qmlscene on a touch device, we can see that the initial
value for editingCapabilities is 64 (selectAll). Long pressing on any
word in one of the text areas (that are initially not focused) should
trigger an update of the value (adding cut and copy caps), but it
doesn’t.
Tapping anywhere inside the same text area, then long pressing on the
word again will correctly update the value of the property, so it’s only
the first time after focusing the text field that this fails.
This was observed with both oxide 1.15.7 and 1.16.8.
** Affects: oxide
Importance: Undecided
Status: New
** Package changed: webbrowser-app (Ubuntu) => oxide
--
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/1615677
Title:
editingCapabilities value doesn’t change when long pressing a word in
an unfocused text field
Status in Oxide:
New
Bug description:
The following example illustrates the problem:
import QtQuick 2.4
import com.canonical.Oxide 1.15
WebView {
url: "http://www.w3schools.com/tags/tryit.asp?filename=tryhtml_textarea";
Component.onCompleted: console.log("initial editing caps:",
editingCapabilities)
onEditingCapabilitiesChanged: console.log("editing caps changed:",
editingCapabilities)
}
When run in qmlscene on a touch device, we can see that the initial
value for editingCapabilities is 64 (selectAll). Long pressing on any
word in one of the text areas (that are initially not focused) should
trigger an update of the value (adding cut and copy caps), but it
doesn’t.
Tapping anywhere inside the same text area, then long pressing on the
word again will correctly update the value of the property, so it’s
only the first time after focusing the text field that this fails.
This was observed with both oxide 1.15.7 and 1.16.8.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1615677/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
