qt/qtdeclarative.git/src/quick/items/qquickloader.cpp, branch 6.11

Docs: replace ambiguous 'object' with specific QML types

2026-04-20T06:24:28+00:00

Replace ambiguous `object` qdoc annotations with `var`, `QtObject` or
concrete QML types to make API intent clear and improve tooling.

Affected signatures (old → new):
- ListModel::get(int index) — object → var
- ObjectModel::get(int index) — object → QtObject
- DelegateModelGroup::get(int index) — object → var
- Component::incubateObject(QtObject parent, object properties, enumeration
    mode) → var Component::incubateObject(QtObject parent, var properties,
    enumeration mode)
- Component::createObject(QtObject parent, object properties) → QtObject
    Component::createObject(QtObject parent, var properties)
- Qt::createQmlObject(string qml, object parent, url url) → QtObject
    Qt::createQmlObject(string qml, QtObject parent, url url)
- Qt::include(string url) — return object → var
- Qt::platform (qmlproperty) — object → var
- Qt::styleHints (qmlproperty) — object → QtObject
- Qt::font(object fontSpecifier) → font Qt::font(var fontSpecifier)
- Canvas::getContext(...) — object → Context2D
- Context2D chain-style methods (save, restore, translate, rotate, scale,
    setTransform, transform, moveTo, lineTo, arc, bezierCurveTo,
    quadraticCurveTo, rect, roundedRect, ellipse, fill, stroke, fillText,
    strokeText, etc.) — object → Context2D
- createLinearGradient/createRadialGradient/createConicalGradient — object →
    CanvasGradient
- isPointInPath(...) — object → bool
- measureText(...) — object → var
- putImageData(...) — object → void
- CanvasImageData::data — object → CanvasPixelArray
- Loader::setSource(url, object) → void Loader::setSource(url, var)
- TestCase::grabImage(Item) — object → QtObject
- TestCase::createTemporaryQmlObject(string qml, object parent, string
    filePath) → QtObject createTemporaryQmlObject(string qml, QtObject parent,
    string filePath)
- TestCase::createTemporaryObject(Component component, object parent, object
    properties) → QtObject createTemporaryObject(Component component, QtObject
    parent, var properties)

Determined correct types by inspecting the corresponding C++
implementations (return/parameter types) and native types of the QML
types. QObject -> QtObject, QJSValue becomes var mostly.

Fixes: QTBUG-141127
Pick-to: 6.8
Change-Id: I27eda37c1bff6e9625d14b07668287402ef85e11
Reviewed-by: Ulf Hermann 
(cherry picked from commit 573aa2a580d12392478711594a9dcf5cf7781bb4)
Reviewed-by: Qt Cherry-pick Bot

Doc: Fix misleading statement about Loader and parent Item access

2026-02-04T10:06:19+00:00

Remove a misleading statement that implied components loaded by Loader
could directly access functions of the Loader or its parent item.

Pick-to: 6.10 6.9
Fixes: QTBUG-123141
Change-Id: If356abcb67aeff561b232517a8975e4c884885f3
Reviewed-by: Ulf Hermann 
(cherry picked from commit fc1810bc6cce17ee9763cd09fef4a11f0520b8e5)
Reviewed-by: Qt Cherry-pick Bot

Set explicit default security level of all files with default security

2025-09-17T13:31:14+00:00

The files (folders) already processed are listed in each issue in epic
QTBUG-134547

These files were processed half a year ago. In order to make it clear
that all of these files are already processed, mark them with an
explicit default security header.

For the record, this was generated with this script:

find -E . -regex ".*\.(cpp|h|hpp|mm|qml|js)$" | xargs python3 ~/bin/add-cra-header.py

in the folders listed in each subtask of QTBUG-134547

(add-cra-header.py only exist at my desktop, but it simply adds the
default security header if it doesn't already have any existing security
header)

QUIP: 23
Fixes: QTBUG-134547
Pick-to: 6.10 6.9 6.8
Change-Id: Ieb8c78ea6561fdbdd27c7b13185ece853eedf80f
Reviewed-by: Oliver Eftevaag

QtQml: Encapsulate QQmlComponentPrivate

2024-12-11T13:26:04+00:00

Other types should not be able to recklessly hack into its internals.

Change-Id: I3f98e11b303193d1c56a6e8e64de03909751030a
Reviewed-by: Sami Shalayel 
Reviewed-by: Fabian Kosmale

Add missing includes

2024-10-24T12:19:23+00:00

...in preparation of trimming down includes in QQuickItem.
As a drive-by, remove the superfluous qqml.h include from
quick/items/qquicktextutil_p.h.

Change-Id: I7ee0f459bcbfdfe07314d1f63433aaa8639870ac
Reviewed-by: Richard Moe Gustavsen 
Reviewed-by: Ulf Hermann

Doc: Replace \instantiates with \nativetype

2024-08-20T10:48:23+00:00

Since the implementation of the `\nativetype`-command in QDoc,
the `\instantiates`-command is deprecated. Replace the use of the
deprecated command in favor of its replacement.

Pick-to: 6.8
Task-number: QTBUG-128216
Change-Id: I23d9f66d3f6db2e5f827d7868497a432bb9b0626
Reviewed-by: Venugopal Shivashankar

QtQuick: Straighten out some logging categories

2024-06-19T21:09:23+00:00

Either make them static or declare them in a header. We want them to be
static wherever possible, in order to reduce the number of visible
symbols. If they can't be static, however, they should at least be
declared in only one place.

Task-number: QTBUG-67692
Change-Id: I485bb7e4379e86f72619f848399ad58c76586851
Reviewed-by: Volker Hilsheimer 
Reviewed-by: Fabian Kosmale

Loader: keep control over resizing

2024-04-11T22:20:21+00:00

A Loader with an explicitly set size is supposed to control its child's
size. However, so far, we would have kept bindings on width and height
in place - before Qt 6.2 in any case, since 6.2 (and the change to make
Item's geometry properties bindable) only when both size and width
change at the same time. Thus, if the binding was triggered afterwards,
it would have overridden the size set by the Loader.
Fix this by always removing installed bindings.

Fixes: QTBUG-117641
Pick-to: 6.7
Change-Id: Iece4d90bacd9e16a07e5018bf11fa0f7ba9c84df
Reviewed-by: Mitch Curtis 
Reviewed-by: Shawn Rutledge

Defer automatic Window transient parent until component completion

2023-10-18T15:42:10+00:00

A Qt Quick Window without an explicitly set transient parent will
automatically get a transient parent based on its object parent,
for example if it's added as a child another Window or Item in
a QML document, or if a parent is passed to Qt.createComponent
or Qt.createQmlObject.

The logic to handle this was spread out through the various places
that Window objects were added to a QML document or created,
making it hard to maintain or extend this logic. The logic is
now centralized in a single updateTransientParent() function
in QQuickWindowQmlImpl, that's triggered on component completion,
and whenever the conditions for the automatic transient parent
change after that. This allows us to extend the logic to not
apply automatic transient parent when we add support for real
(non transient) child windows later. The machinery relies on
new optional behavior in QObject to send ParentChange events
whenever the parent of an object changes.

Another issue with the previous approach was that it was doing
synchronous QWindow::setTransientParent() calls whenever one
of the conditions were met, which in some cases resulted in
overriding the explicit transientParent set declaratively by
the user. This was an issue because setting the transient
parent to null was the documented way to opt out of one of
the implicit behaviors of a Window with a transient parent,
namely that it defers its visibility until the transient
parent has been made visible. As we now defer the transient
parent magic until the component has been completed, we
know whether the user has set the property explicitly,
and can bail out of the magic if so.

As the deferred visibility of a Window was closely tied to
the transient parent logic, this logic has been refactored
as well, attempting to keep the two machineries as decoupled
as possible. As part of this refactoring the logic to warn
the user if conflicting visibility properties is detected
has been factored into a separate function.

The tst_qquickwindow::attachedProperty() needs a tweak, as
it was was relying on the secondary window not being
transient, which was the case prior to this patch because
we failed to catch the case of Window properties in our
auto-transient-parent machinery:

  Rectangle {
      property Window someWindow: Window {}
      // someWindow is now transient to the
      // rectangle's window.
  }

Now that we correctly handle this case, the check for
qWaitForWindowActive() was not sufficient to ensure
the Window.active property was true, as transient child
windows are active if their transient parent is active,
and we would not end up spinning the event loop at all,
which is required for the binding to update.

To solve this we now explicitly mark the test window
as not having a transient parent.

[ChangeLog][Qt Quick] Declaring Windows via dedicated
properties of another Window or Item will result in
an automatic transient parent relationship to the
parent Window or Item, just like declaring it as
part of the default data property.

Task-number: QTBUG-116188
Change-Id: Ia1138391d57b64838cebea4bc0a97fbfdf022772
Reviewed-by: Volker Hilsheimer 
Reviewed-by: Fabian Kosmale

Clarify relation between transient parent and child in debug logging

2023-09-28T22:28:39+00:00

It's also now clearer that it's a synchronous modification of the
relationship.

Change-Id: Ie9c72c7d195b124f842cc1df15c51cb7b4ff99e6
Reviewed-by: Shawn Rutledge