Wrong text selection after scolling when Textarea is readonly and embeded in a Flickable .

[Sheep]

As the title says, this can be reproduced by running the file in "+touch/texteditor.qml" in the "texteditor" example. as you may notice in the attached video, when i try to select the text at the top, its working fine, but when selection handles are persistent and i scroll to the text at the bottom, and i try to select, the app is selecting wrong text.

demo video

1. Is it a bug or i have to set some other poperties
2. how can i make the app deselect the selected text, because if you text the same app and select "Copy", the selection handles remain there. i tried setting the "persistentSelection" property to false, but it didnot help either.

Am using Qt 6.5.1.

[Sheep]

Hasn`t anyone experienced this issue, it can be easily reproduced by running the qml texteditor example on android, try typing a lot of text, ensure you return to the "readonly" state (tap the "tick" icon at the extreme top left after typing the text), then scroll to the extreme bottom or extreme top and try to select any word ...you will notice the textarea will select wrong words instead.

[KH-219Design]

I cannot try at the moment to reproduce this myself, but based on the video (and the fact that you are using an example written by Qt team) it certainly seems like a bug.

Do you think this is the same bug: https://bugreports.qt.io/browse/QTBUG-115004

They seem to indicate (on the bugreports site) that it is fixed in 6.5.3. You could try using 6.5.3 and see if that helps.

[Sheep]

At last some response...
I used Qt 6.7.2 version , with android Clang arm64-v8a, sorry i forgot to include that, but still i will try your solution.

[KH-219Design]

@Sheep more generally, I want to emphasize that to your point (1) "is it a bug", I certainly feel that this qualifies as a bug. That's my opinion/assessment as a long-time Qt user. (and as an owner of an Android phone and long-time Android user.) But I am not a Qt employee nor have I contributed code to the framework.

So you might get a better answer posting/reporting on the bugtracker. https://doc.qt.io/qt-6/bughowto.html

If you open a bug and they end up flagging it as a duplicate of the older ticket, that should be fine on their end.

On the other hand, if you post your video onto the prior bug (the one I linked earlier), they may tell you to open a fresh new ticket.

Or someone may even say "your video shows the intended behavior" and perhaps they will give you some workaround or tips.

In any case, you are more likely to get attention from a Qt developer that way.