If coordinates are high enough, there will be a difference between where the item is rendered compared to where it actually is and can be interacted at. For example in a very long Flickable type components.

Can be reproduced with this, use the scroll bar to jump to halfway for example and try to click the buttons there:

import QtQuick
import QtQuick.Controls
import QtQuick.Window

Window {
    visible: true
    width: 1024
    height: 600
    color: "white"
    ListView {
        anchors.fill: parent
        ScrollBar.vertical: ScrollBar { }
        model: 50000000
        spacing: 0
        delegate: Button {}
    }
}

If the view is scrolled to the same position at startup programmatically, it works fine because originY changes and it cancels out. Maybe it could be made to do this origin resetting at runtime too if the coordinates are getting too high.