The bug was not introduced by the MR linked in the bug description. I
reproduced the bug with this code, and pulling down the listview and
releasing it with a vertical velocity:
import QtQuick 2.2
import QtQuick.XmlListModel 2.0
import Ubuntu.Components 1.3
import Ubuntu.Components.ListItems 1.3
MainView {
width: units.gu(40)
height: units.gu(71)
Page {
id: page0
title: "Reuters"
ListView {
id: view
anchors.fill: parent
model: 15
delegate: Standard {
width: ListView.view.width
height: units.gu(5)
text: index//title
}
onVerticalVelocityChanged: print("vv = "+verticalVelocity)
PullToRefresh {
id: pullToRefresh
onRefreshingChanged: print("refreshing = "+refreshing)
onRefresh: {
refreshing = true;
refreshing = false;
// refreshTimer.start();
}
}
}
}
// Timer {
// id: refreshTimer
// onTriggered: pullToRefresh.refreshing = false
// }
}
and with UITK r1930 (before the mentioned MR) and r1918.
I think the bug was always there, the topMargin gets messed up by the
PullToRefresh. However, pre-r1931, the topMargin was (incorrectly) reset
to 0 when a new Page was pushed on the PageStack (which happens in
onRefresh for the example linked to th ebug). Now that this no longer
happens, the bug becomes visible when the Page is popped from the stack.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578619
Title:
[regression] Extra flickable margin added when using PullToRefresh
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578619/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
