The condition for fixing up the alias property index was wrong. Instead
of checking the last list element, it was checking the first element
twice.
To avoid further mistakes and to make the logic easier to reason about,
use std::find and std::distance to compute the index, and rely on the
compiler to potentially optimize the loops.

Amends 5b775e96c067995bf21cdf5a3641c50d5b7b272d

Pick-to: 6.11 dev
Fixes: QTBUG-144701
Change-Id: I589378b6cbc8d68f550ff7ec67be9a420ebee4d5
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>

tst_qquicktext::contentSize(spyWidth.size()) fails consistently on
Windows. Instead of blacklisting it, add QEXPECT_FAIL to it. And remove
the test blacklists for other Windows compilers, as they also look to be
consistently failing and not flaky (QUIP 24).

Task-number: QTBUG-88646
Task-number: QTQAINFRA-7559
Pick-to: 6.8
Change-Id: I4e1519767b1804cbe09954d1f25ca11c6c478ac4
Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io>
(cherry picked from commit c4179b8e121ef9caae8c11adddb8cad2dfc08662)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

When a ViewportOnly rebuild is triggered in TableView by a row
or column insertion or removal, delegate items that survive the
operation (i.e. are not part of the removed range) should not
be pooled and reused. Instead they should simply stay in place
and have their context properties updated to reflect any shift
in flat index, row or column. This avoids a full pool cycle,
preserves any ongoing visual state such as animations, and
suppresses unnecessary pooled/reused signals.

To achieve this, released items are now staged in a temporary
m_releasedItems cache rather than moved directly to the reuse
pool. During the rebuild, resolveModelItem() first searches the
cache for an item whose QPersistentModelIndex matches the
requested cell. If found, the item is reclaimed directly.
Once the rebuild is complete, commitReleasedItems() transfers
any remaining cached items (those whose cells genuinely
disappeared) to the reuse pool, like before.

In order to achieve this, a new QPersistentModelIndex is stored
on each delegate item. That way we know which cell it originally
belonged to, even after changes to the model shifted its
row and column position.

A new auto-test, verifyThatOnlyRemovedRowsArePooled, is included
that verifies the new expected behaviour.

The changes in this patch also uncovered that the test model used
throughout in the test file was implemented with too many assumptions,
and therefore needed some TLC.

Fixes: QTBUG-116650
Fixes: QTBUG-134741
Change-Id: I0b935320b6e7dca215df438f5981a154a8c10385
Reviewed-by: SanthoshKumar Selvaraj <santhosh.kumar.selvaraj@qt.io>
(cherry picked from commit de4b7283c978ca384f6c8bf9f27387158804b601)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

When a QQuickPopup is open inside a QQuickWidget,
pressing Tab on the last focusable item in the popup would move
keyboard focus to a widget outside the QQuickWidget instead of cycling
back to the first item in the popup.

QQuickItem::nextPrevItemInTabFocusChain() has a parameter `warp` which
is used by QQuickWidgets and embedded windows. To prevent wrapping
between the first and last focusable items in the QML scene.

This was working as intentional, with the exception that it would ignore
cases when the current focused item is inside a tab fence. In such
cases, we still want the item to wrap, we just want it to wrap inside
the tab fence, which nextPrevItemInTabFocusChain() already takes into
consideration, as long as we don't return early when wrap=false.

Fix it by only returning early from wrap=false, when not inside a tab
fence.

Fixes: QTBUG-138101
Pick-to: 6.10 6.8
Change-Id: Iab0914161f0a80c3b0df0385cfb1fd0c0027ac7a
Reviewed-by: Doris Verria <doris.verria@qt.io>
(cherry picked from commit 77c3189bc00ebd302b5a211d039db49228dca105)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

QQuickPopupPrivate::windowInsets() returns a QMarginsF object.

The constructor used is
constexpr QMarginsF(qreal left, qreal top, qreal right, qreal bottom) noexcept;

The values passed for top and right were swapped. Fix it in this patch.

Add test that verifies that the margins are set in the correct order.

Pick-to: 6.8
Change-Id: I25af57ac5ee6ddd056dda310392f7f9b2633f302
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
(cherry picked from commit b41c6899490135268d27ccfb0cf552f1379387e8)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

This reverts commit 439864b68e4dbc500b7eb941e3d0d48e538e8a78.

Reason for revert: Breaks qmlsc (QTBUG-145981)

Fixes: QTBUG-145981
Reopens: QTBUG-145611
Pick-to: dev
Change-Id: I9eff05139cd4659ce822a34a04b4ffe66813d310
Reviewed-by: Sami Shalayel <sami.shalayel@qt.io>

This reverts commit d7666a15ce36f3e5e5ab5722da43c82124cba8b7.

Reason for revert: Breaks qmlsc (QTBUG-145981)

Task-number: QTBUG-145981
Reopens: QTBUG-145611
Pick-to: dev
Change-Id: I5bacc0b026fb79085e7e608de9b6634318880eb4
Reviewed-by: Sami Shalayel <sami.shalayel@qt.io>

When a Text element uses StyledText with <br> tags, maximumLineCount,
wrapMode: Wrap, and elide: ElideRight, constraining its width could
cause implicitWidth to grow far beyond the correct value.

The root cause is twofold:

1. The loop that creates unwrapped lines for implicit width calculation
used '<=' instead of '<', causing one extra line to be created and
finalized beyond maximumLineCount paragraphs.

2. The multiline-elide code path creates a trailing line via
createLine() to compute the elided text. That line is left unfinalized,
so endLayout() finalizes it at QFIXED_MAX width, inflating
maximumWidth(). Finalize it at zero width right after use.

Fixes: QTBUG-142933
Change-Id: I64bab9512b8400ed63a4dda709259488a2b49a21
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
(cherry picked from commit 021778a0ad7d5758cee5f5592017e46b4e12171d)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

When QAbstractItemModel::data() returns an invalid QVariant (representing
'undefined' in JS) for a role bound to a typed property like
'required property string foo', the property-to-property binding's write
was silently failing. This happened because writeValueProperty() only uses
QMetaType conversions which cannot convert an invalid QVariant to a
QString. The property kept its old value, and subsequent valid writes
of the same value would not trigger change signals.

Update QQmlPropertyToUnbindablePropertyBinding::update() to perform
proper type coercion using metaTypeToJS() and metaTypeFromJS().

Fixes: QTBUG-145016
Change-Id: I8421e813ddde50d4c252907045448b22a36a0a70
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
(cherry picked from commit 7c8cb7eb67df93ef6232ef498c97f460e822a984)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

Support attached and grouped properties for UiArrayBindings, in the same
way as UiObjectBinding do. Extract the attached/grouped property code for
visit(UiObjectBinding*) and endvisit(UiObjectBinding*) into a helper and
use the helper for visit(UiArrayBinding*) and endvisit(UiArrayBinding*).

Amends the unknownPropertyDuplicateBinding.qml test that complains about
a missing grouped property not existing, and add a test that binds an
object list to an attached property.

Fixes: QTBUG-140138
Change-Id: I20a4ceafa152aedb4e56cc9a7a05ecff1828659a
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
(cherry picked from commit 186bf1a4addff83a43735ba68a830c799384528d)
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
Reviewed-by: Nicolas Fella <nicolas.fella@kdab.com>