text input and editing in web forms and fields
-
So far the experience of editing a sentence in a search bar is very much a pain. In duckduckgo (not the app) for example as soon as I try to edit, it goes back to the beginning of the field and the only way I can get back to the end of the sentence is by deleting everything before it... As a whole, the way you select, cut, and position your cursor is problematic and I can't be the only one to see this ! Selecting sometimes only works with entire paragraphs or lines, and there should be a more accurate way of placing the cursor, like the magnifier on ios
-
@Emphrath Hi. Apparently, you are not aware of the wonderful
work done by Kugiigi on the OSK and that you can now find in DEV or RC.
With this OSK, we can get around the problem. See https://forums.ubports.com/topic/1893/osk-enhancements-proposals/62 -
@domubpkm Oh wow it's been implemented ! Well wonderful. I'll be waiting for it to reach stable branch I think. Awesome ! Topic closed.
-
Yup it is now in RC and devel. It also fixes the cursor mover in the OSK when in the web pages albeit some change in the behavior.
Also, do you happen to use auto-correct, spell check, or such feature? That's very problematic at the moment in QtWebEngine and hopefully someone can find a solution to them.
-
@kugiigi Hello.
did i understand correctly? I'm not sure about that :
are you saying that we can also now move the cursor in a simple web page of text ? And not only in the "workable" areas ?
How to make the keyboard appear on simple web pages of text ? Because i can't do that. -
@domubpkm No, I meant only in web text fields in which of course the OSK will appear. Because currently, the cursor mover doesn't work properly in it. If I remember correctly, moving to the right doesn't work.
-
You say :' Only in web text fields in which of course the OSK will appear'.
All right, too bad!!!
I had a false hope that the current morph limitation for this could be circumvented.
And for this :
-
@kugiigi yeah I do use those and they're not perfect. I'll get back here with some more accurate feedback soon
-
@domubpkm Actually I meant only in the browser or webapps. Not text fields in native apps
-
@kugiigi yes I mean that's definitely the bulk of the issue here ^^