Details
-
Bug
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
6.4.0 Beta1
-
None
Description
29098: ********* Start testing of tst_QQuickListView2 ********* FAIL! : tst_QQuickListView2::tapDelegateDuringFlicking(Button DragOverBounds) '(listView->contentY() > 501)' returned FALSE. () Loc: [/home/qt/work/qt/qtdeclarative/tests/auto/quick/qquicklistview2/tst_qquicklistview2.cpp(404)] PASS : tst_QQuickListView2::tapDelegateDuringFlicking(MouseArea DragOverBounds) FAIL! : tst_QQuickListView2::tapDelegateDuringFlicking(Button OvershootBounds) '(listView->contentY() > 501)' returned FALSE. () Loc: [/home/qt/work/qt/qtdeclarative/tests/auto/quick/qquicklistview2/tst_qquicklistview2.cpp(404)] PASS : tst_QQuickListView2::tapDelegateDuringFlicking(MouseArea OvershootBounds) PASS : tst_QQuickListView2::tapDelegateDuringFlicking(Button DragAndOvershootBounds) Totals: 23 passed, 2 failed, 0 skipped, 0 blacklisted, 58079ms
It seems like the series of touch events does not generate momentum; I didn't verify exactly how much the flickable moved, but it should have built up velocity, and therefore moved farther than it was dragged.
Blacklisted for now, as with many things on Android.
Attachments
Issue Links
- relates to
-
QTBUG-88252 QEventPoint::velocity must be accurate and in logical pixels
- Reported
-
QTBUG-88346 need to check mouse and touch residual velocity modeling
- Reported
-
QTBUG-99639 Rotated flickable decelerates in wrong direction
- Closed
-
QTBUG-33891 ensure that TouchPoints always have velocity
- Closed
-
QTBUG-105190 tst_QQuickListView2::flickDuringFlicking is flaky
- Closed
- resulted from
-
QTBUG-103832 The delegate item of ListView is not pressed if the boundsBehavior is to set Flickable.StopAtBounds
- Closed