<feed xmlns='http://www.w3.org/2005/Atom'>
<title>qt/qtdeclarative.git/src/quicknativestyle/controls/DefaultTextArea.qml, branch dev</title>
<subtitle>Qt Declarative (Quick 2)
</subtitle>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/'/>
<entry>
<title>QuickControls: Move NativeStyle into src/quickcontrols</title>
<updated>2026-02-11T22:36:27+00:00</updated>
<author>
<name>Ulf Hermann</name>
<email>ulf.hermann@qt.io</email>
</author>
<published>2026-02-02T12:07:26+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=1796f9a8b336c9600b94d67ce39174c12866b59d'/>
<id>1796f9a8b336c9600b94d67ce39174c12866b59d</id>
<content type='text'>
It's an internal helper for the windows and macos styles. It depends on
QuickControls2. Therefore it needs to be declared after QuickControls2
but before the windows and mac styles.

This way we can link its backing library into downstream modules. We do
this for two reasons:

1. Link-able modules can be used by qmlsc's direct mode. Plugin-only
   modules can't.
2. If a module is linked and its plugin is optional, we can omit the
   overhead of plugin loading.

Unfortunately, the plugin isn't optional, yet, but still this change is
a step in the right direction.

Task-number: QTBUG-107908
Change-Id: Ied1489ec91b9acdb133181d55a6069216c91375c
Reviewed-by: Mitch Curtis &lt;mitch.curtis@qt.io&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
It's an internal helper for the windows and macos styles. It depends on
QuickControls2. Therefore it needs to be declared after QuickControls2
but before the windows and mac styles.

This way we can link its backing library into downstream modules. We do
this for two reasons:

1. Link-able modules can be used by qmlsc's direct mode. Plugin-only
   modules can't.
2. If a module is linked and its plugin is optional, we can omit the
   overhead of plugin loading.

Unfortunately, the plugin isn't optional, yet, but still this change is
a step in the right direction.

Task-number: QTBUG-107908
Change-Id: Ied1489ec91b9acdb133181d55a6069216c91375c
Reviewed-by: Mitch Curtis &lt;mitch.curtis@qt.io&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Set explicit default security level of all files with default security</title>
<updated>2025-09-17T13:31:14+00:00</updated>
<author>
<name>Jan Arve Sæther</name>
<email>jan-arve.saether@qt.io</email>
</author>
<published>2025-09-16T13:35:55+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=01cd43d30e3ca2c4dd94a4a4711604adb9417517'/>
<id>01cd43d30e3ca2c4dd94a4a4711604adb9417517</id>
<content type='text'>
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 &lt;oliver.eftevaag@qt.io&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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 &lt;oliver.eftevaag@qt.io&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>DefaultTextArea: fix placeholder text alignment</title>
<updated>2023-12-12T05:53:00+00:00</updated>
<author>
<name>Vladimir Belyavsky</name>
<email>belyavskyv@gmail.com</email>
</author>
<published>2023-12-11T20:00:23+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=c4a1db07c0f833712b66688563efabc9dfce89f2'/>
<id>c4a1db07c0f833712b66688563efabc9dfce89f2</id>
<content type='text'>
The fix is similar to e3f990999b8738b9d33bfefc1e254149ff873c8a
for TextField. The root cause of the problem is the same - TextArea
doesn't inherit from Control component, so availableWidth and
availableHeight properties are not defined.

But we can use the same way of calculating the width and height of
the PlaceholderText that we use for other styles.

Pick-to: 6.7 6.6 6.5
Fixes: QTBUG-120005
Change-Id: I971c8eb5130c8cab8e23cb2b58e089f1490ed1ae
Reviewed-by: Mitch Curtis &lt;mitch.curtis@qt.io&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The fix is similar to e3f990999b8738b9d33bfefc1e254149ff873c8a
for TextField. The root cause of the problem is the same - TextArea
doesn't inherit from Control component, so availableWidth and
availableHeight properties are not defined.

But we can use the same way of calculating the width and height of
the PlaceholderText that we use for other styles.

Pick-to: 6.7 6.6 6.5
Fixes: QTBUG-120005
Change-Id: I971c8eb5130c8cab8e23cb2b58e089f1490ed1ae
Reviewed-by: Mitch Curtis &lt;mitch.curtis@qt.io&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Warn users when they customize native styles</title>
<updated>2022-12-05T07:00:35+00:00</updated>
<author>
<name>Mitch Curtis</name>
<email>mitch.curtis@qt.io</email>
</author>
<published>2022-11-21T09:51:53+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=e592a2ad31695695f0dd2069b17c6ab90ed1a739'/>
<id>e592a2ad31695695f0dd2069b17c6ab90ed1a739</id>
<content type='text'>
Since Qt 6, the default style is no longer the Basic style, but instead
depends on the platform the application is run on. In addition, the
introduction of the native styles (which are not designed to be
customized) means that users customizing controls can run into visual
issues and not understand why.

This patch partially addresses this issue by warning when a native
control is customized (i.e. a delegate is overridden):

"qrc:/main.qml:11:22: QML QQuickItem: The current style does not
support customization of this control (property: "contentItem" item:
QQuickItem(0x1637375d210, parent=0x0, geometry=0,0 0x0)).
Please customize a non-native style (such as Basic, Fusion, Material,
etc). For more information, see:
https://doc.qt.io/qt-6/qtquickcontrols2-customize.html#customization-reference"

Ideally we'd also have qmllint integration in Creator so that users get
warnings from the IDE as they code, but that's not there yet.

The patch also updates the documentation by removing the code snippet
from the note and referring users to the existing
"Using Styles in Qt Quick Controls" section, which covers the topic in
greater detail. The snippet itself is also not considered a part of the
note, so the (online) styling looked a bit off.

[ChangeLog][Important Behavior Changes] Customization of native styles
will now result in warnings. Non-native styles (such as Basic) should
be used for customization purposes, or a custom style. If you are aware
of the risks and still want to customize these controls, you can ignore
the warnings by setting QT_QUICK_CONTROLS_IGNORE_CUSTOMIZATION_WARNINGS
to 1.

Fixes: QTBUG-108519
Task-number: QTBUG-96733
Change-Id: Ib6dff4639bad76b228e0f31285d20db4e3207224
Reviewed-by: Richard Moe Gustavsen &lt;richard.gustavsen@qt.io&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Since Qt 6, the default style is no longer the Basic style, but instead
depends on the platform the application is run on. In addition, the
introduction of the native styles (which are not designed to be
customized) means that users customizing controls can run into visual
issues and not understand why.

This patch partially addresses this issue by warning when a native
control is customized (i.e. a delegate is overridden):

"qrc:/main.qml:11:22: QML QQuickItem: The current style does not
support customization of this control (property: "contentItem" item:
QQuickItem(0x1637375d210, parent=0x0, geometry=0,0 0x0)).
Please customize a non-native style (such as Basic, Fusion, Material,
etc). For more information, see:
https://doc.qt.io/qt-6/qtquickcontrols2-customize.html#customization-reference"

Ideally we'd also have qmllint integration in Creator so that users get
warnings from the IDE as they code, but that's not there yet.

The patch also updates the documentation by removing the code snippet
from the note and referring users to the existing
"Using Styles in Qt Quick Controls" section, which covers the topic in
greater detail. The snippet itself is also not considered a part of the
note, so the (online) styling looked a bit off.

[ChangeLog][Important Behavior Changes] Customization of native styles
will now result in warnings. Non-native styles (such as Basic) should
be used for customization purposes, or a custom style. If you are aware
of the risks and still want to customize these controls, you can ignore
the warnings by setting QT_QUICK_CONTROLS_IGNORE_CUSTOMIZATION_WARNINGS
to 1.

Fixes: QTBUG-108519
Task-number: QTBUG-96733
Change-Id: Ib6dff4639bad76b228e0f31285d20db4e3207224
Reviewed-by: Richard Moe Gustavsen &lt;richard.gustavsen@qt.io&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Use SPDX license identifiers</title>
<updated>2022-06-11T06:05:15+00:00</updated>
<author>
<name>Lucie Gérard</name>
<email>lucie.gerard@qt.io</email>
</author>
<published>2022-05-13T13:12:05+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=0dc4fd240a2897c5c443a0ef6d84c416843e4938'/>
<id>0dc4fd240a2897c5c443a0ef6d84c416843e4938</id>
<content type='text'>
Replace the current license disclaimer in files by
a SPDX-License-Identifier.
Files that have to be modified by hand are modified.
License files are organized under LICENSES directory.

Pick-to: 6.4
Task-number: QTBUG-67283
Change-Id: I63563bbeb6f60f89d2c99660400dca7fab78a294
Reviewed-by: Shawn Rutledge &lt;shawn.rutledge@qt.io&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Replace the current license disclaimer in files by
a SPDX-License-Identifier.
Files that have to be modified by hand are modified.
License files are organized under LICENSES directory.

Pick-to: 6.4
Task-number: QTBUG-67283
Change-Id: I63563bbeb6f60f89d2c99660400dca7fab78a294
Reviewed-by: Shawn Rutledge &lt;shawn.rutledge@qt.io&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Use up-to date LGPL license header</title>
<updated>2021-11-29T08:21:34+00:00</updated>
<author>
<name>Kai Köhne</name>
<email>kai.koehne@qt.io</email>
</author>
<published>2021-11-25T16:22:05+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=5d4679289bc5a46df4f767e7eabcee0bcf99169d'/>
<id>5d4679289bc5a46df4f767e7eabcee0bcf99169d</id>
<content type='text'>
Remove usages of outdated LGPL3 header that references LICENSES.LGPLv3
instead of LICENSES.LGPL3.

Change-Id: If7a90ec18331a68491c5a740f131a5e7b3f37df4
Reviewed-by: Volker Hilsheimer &lt;volker.hilsheimer@qt.io&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Remove usages of outdated LGPL3 header that references LICENSES.LGPLv3
instead of LICENSES.LGPL3.

Change-Id: If7a90ec18331a68491c5a740f131a5e7b3f37df4
Reviewed-by: Volker Hilsheimer &lt;volker.hilsheimer@qt.io&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix implicit size of TextArea</title>
<updated>2021-09-07T18:01:59+00:00</updated>
<author>
<name>Jan Arve Sæther</name>
<email>jan-arve.saether@qt.io</email>
</author>
<published>2021-09-01T12:53:47+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=abf96ed452578d619a89982fc5fe233239768a71'/>
<id>abf96ed452578d619a89982fc5fe233239768a71</id>
<content type='text'>
An empty TextArea had a too large size because its placeholder item
was too big. This follows a similar pattern as the former fix for
TextField (5d8e74ab89b5ae465aefab924f4f14db59328a50)

TextArea::test_ImplicitSize demonstrated this bug

Task-number: QTBUG-95679
Pick-to: 6.2
Change-Id: I2b71208a02e47a0a072326a6d600cbac90862ea7
Reviewed-by: Mitch Curtis &lt;mitch.curtis@qt.io&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
An empty TextArea had a too large size because its placeholder item
was too big. This follows a similar pattern as the former fix for
TextField (5d8e74ab89b5ae465aefab924f4f14db59328a50)

TextArea::test_ImplicitSize demonstrated this bug

Task-number: QTBUG-95679
Pick-to: 6.2
Change-Id: I2b71208a02e47a0a072326a6d600cbac90862ea7
Reviewed-by: Mitch Curtis &lt;mitch.curtis@qt.io&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Use the added placeHolderText color available in Palette</title>
<updated>2021-06-17T06:03:41+00:00</updated>
<author>
<name>Andy Shaw</name>
<email>andy.shaw@qt.io</email>
</author>
<published>2021-05-27T07:04:16+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=a7f627b08d4c3e0dc963018c67c5f8aff3f77b4a'/>
<id>a7f627b08d4c3e0dc963018c67c5f8aff3f77b4a</id>
<content type='text'>
This allows it to pick up the Palette's placeHolderText color by default
while still using the property if it is overridden with that.

Pick-to: 6.2
Task-number: QTBUG-93746
Change-Id: Ie6af95d6c60fa80f2789c2acd5964b5a347194ce
Reviewed-by: Mitch Curtis &lt;mitch.curtis@qt.io&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This allows it to pick up the Palette's placeHolderText color by default
while still using the property if it is overridden with that.

Pick-to: 6.2
Task-number: QTBUG-93746
Change-Id: Ie6af95d6c60fa80f2789c2acd5964b5a347194ce
Reviewed-by: Mitch Curtis &lt;mitch.curtis@qt.io&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Update to latest qml CMake API</title>
<updated>2021-06-05T10:52:00+00:00</updated>
<author>
<name>Craig Scott</name>
<email>craig.scott@qt.io</email>
</author>
<published>2021-05-31T06:40:54+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=5e8feb64d6a3cf50360c066e4595e41021bd0f9c'/>
<id>5e8feb64d6a3cf50360c066e4595e41021bd0f9c</id>
<content type='text'>
The new qml CMake API places a closer relationship between
the backing target and the plugin target. Both are typically
created together and they share a lot of common details.
Instead of creating them in different parts of the source
tree, they are now specified together. The src/imports
area has effectively been absorbed into the other
corresponding subdirectories below src with this change.

Task-number: QTBUG-91621
Change-Id: I9bd32e9eb78c198ccc9db04e2829303cac323502
Reviewed-by: Fabian Kosmale &lt;fabian.kosmale@qt.io&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The new qml CMake API places a closer relationship between
the backing target and the plugin target. Both are typically
created together and they share a lot of common details.
Instead of creating them in different parts of the source
tree, they are now specified together. The src/imports
area has effectively been absorbed into the other
corresponding subdirectories below src with this change.

Task-number: QTBUG-91621
Change-Id: I9bd32e9eb78c198ccc9db04e2829303cac323502
Reviewed-by: Fabian Kosmale &lt;fabian.kosmale@qt.io&gt;
</pre>
</div>
</content>
</entry>
</feed>
