overlapping mouse area onEntered onExited order is diffrent in qt5 and q6

we have 2 overlapping mouse areas 

MouseArea

{ id:aaa width:250 height:250 propagateComposedEvents: true hoverEnabled: true onEntered:

{ console.log("aaa- onEntered") }

onExited: { console.log(" aaa onExited") } }
MouseArea

{ id:bbb x:100 width:250 height:250 propagateComposedEvents: true Rectangle

{ anchors.fill: parent; color: "blue"; }

hoverEnabled: true onEntered: { console.log(" bbb- onEntered") }

onExited: { console.log(" bbb onExited") } }

notice bbb is above aaa in z order

the bug: in QT5 if we hover over bbb then aaa then back to bbb
we get the following prints 
qml: bbb- onEntered
qml: bbb onExited
qml: aaa- onEntered
qml: aaa onExited
qml: bbb- onEntered
qml: bbb onExited

that's good- the logic is first to exit area and then enter a new area
but in QT6 we get
qml: bbb- onEntered
qml: bbb onExited
qml: aaa- onEntered
qml: bbb- onEntered
qml: aaa onExited
qml: bbb onExited

that's BAD! hovering from bbb to aaa gives good logic, but hovering from aaa to bbb (aaa.z<bbb.z) we first enter bbb area and only then exit aaa area.

again, this is a qt6 bug.