<feed xmlns='http://www.w3.org/2005/Atom'>
<title>qt/qtdeclarative.git, branch v5.9.6</title>
<subtitle>Qt Declarative (Quick 2)
</subtitle>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/'/>
<entry>
<title>Add changes file for Qt 5.9.6</title>
<updated>2018-05-30T11:29:13+00:00</updated>
<author>
<name>Antti Kokko</name>
<email>antti.kokko@qt.io</email>
</author>
<published>2018-05-28T06:05:39+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=283a900c4e8518fef33a2c89cb597fbf1e6ad78c'/>
<id>283a900c4e8518fef33a2c89cb597fbf1e6ad78c</id>
<content type='text'>
Change-Id: I989ea0802f459b2440ee580e94340a1e64bf00e4
Reviewed-by: Shawn Rutledge &lt;shawn.rutledge@qt.io&gt;
Reviewed-by: Simon Hausmann &lt;simon.hausmann@qt.io&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Change-Id: I989ea0802f459b2440ee580e94340a1e64bf00e4
Reviewed-by: Shawn Rutledge &lt;shawn.rutledge@qt.io&gt;
Reviewed-by: Simon Hausmann &lt;simon.hausmann@qt.io&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>On network redirects, update finalUrl, not url</title>
<updated>2018-05-25T06:30:41+00:00</updated>
<author>
<name>Ulf Hermann</name>
<email>ulf.hermann@qt.io</email>
</author>
<published>2018-05-23T10:28:46+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=8556133d620e7b64076d7b73de00451e16545c3b'/>
<id>8556133d620e7b64076d7b73de00451e16545c3b</id>
<content type='text'>
We want all further imports to be relative to the redirected URL, not
the base one.

Note that this will incorporate any prior URL interceptions into the
final URL if a redirect happens. We don't really want this to happen
because the result of interception is not meant to be the base for
further URL lookup. However, as interception occurs before redirection,
this is unavoidable. Don't use URL interceptors on remote URLs.

Task-number: QTBUG-67882
Change-Id: I6693d14c8af8212dda9954d0bd0293c3c85441ef
(cherry picked from commit cda2680d801acce4e221b23e88d9b3c5504f86e8)
Reviewed-by: Simon Hausmann &lt;simon.hausmann@qt.io&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We want all further imports to be relative to the redirected URL, not
the base one.

Note that this will incorporate any prior URL interceptions into the
final URL if a redirect happens. We don't really want this to happen
because the result of interception is not meant to be the base for
further URL lookup. However, as interception occurs before redirection,
this is unavoidable. Don't use URL interceptors on remote URLs.

Task-number: QTBUG-67882
Change-Id: I6693d14c8af8212dda9954d0bd0293c3c85441ef
(cherry picked from commit cda2680d801acce4e221b23e88d9b3c5504f86e8)
Reviewed-by: Simon Hausmann &lt;simon.hausmann@qt.io&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Software render: Fix warnings flood</title>
<updated>2018-05-08T08:26:36+00:00</updated>
<author>
<name>Friedemann Kleint</name>
<email>Friedemann.Kleint@qt.io</email>
</author>
<published>2018-02-19T10:51:24+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=047e3f480e9ebed55b21025f19ed7ed7351df118'/>
<id>047e3f480e9ebed55b21025f19ed7ed7351df118</id>
<content type='text'>
Add missing QPainter::end(), fixing:

QBackingStore::endPaint() called with active painter on backingstore paint device

Task-number: QTBUG-66452
Change-Id: Ia00e61953528b15015b3e41ba1868e670818cf14
Reviewed-by: Laszlo Agocs &lt;laszlo.agocs@qt.io&gt;
(cherry picked from commit 047f161b1a706e81034ccd8d4700a3126c16dfe4)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add missing QPainter::end(), fixing:

QBackingStore::endPaint() called with active painter on backingstore paint device

Task-number: QTBUG-66452
Change-Id: Ia00e61953528b15015b3e41ba1868e670818cf14
Reviewed-by: Laszlo Agocs &lt;laszlo.agocs@qt.io&gt;
(cherry picked from commit 047f161b1a706e81034ccd8d4700a3126c16dfe4)
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix QML context leak with visual data model and list property models</title>
<updated>2018-05-07T08:43:02+00:00</updated>
<author>
<name>Simon Hausmann</name>
<email>simon.hausmann@qt.io</email>
</author>
<published>2018-04-26T09:47:27+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=a71d01300371721a3d84336262fee41ccfa4563d'/>
<id>a71d01300371721a3d84336262fee41ccfa4563d</id>
<content type='text'>
When using the VDM or QML list properties as models, the delegate model
injects an intermediate QQmlContext that provides access to the
properties of the exposed QObject as context properties. Before commit
e22b624d9ab1f36021adb9cdbfa9b37054282bb8, that context was marked to be
owned by the parent QQmlContext.

When the reference counting was introduced, that parent became
referenced from the cacheItem (DelegateModelItem), but that intermediate
QQmlContext became floating and was leaked.

This can be observed by running the objectListModel test of
tst_qquickvisualdatamodel with detect_leaks=1 in ASAN_OPTIONS.

The leak is fixed by re-introducing the exceptional case of a parent
holding a strong reference to the child, in just this one case.

Change-Id: Iabc26990d39757b0abe0cddf69e76e88e40fba40
Reviewed-by: Lars Knoll &lt;lars.knoll@qt.io&gt;
Reviewed-by: Michael Brasser &lt;michael.brasser@live.com&gt;
(cherry picked from commit 01df9e5f46fd05a80f8f6fcaa91204e6184ded6f)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When using the VDM or QML list properties as models, the delegate model
injects an intermediate QQmlContext that provides access to the
properties of the exposed QObject as context properties. Before commit
e22b624d9ab1f36021adb9cdbfa9b37054282bb8, that context was marked to be
owned by the parent QQmlContext.

When the reference counting was introduced, that parent became
referenced from the cacheItem (DelegateModelItem), but that intermediate
QQmlContext became floating and was leaked.

This can be observed by running the objectListModel test of
tst_qquickvisualdatamodel with detect_leaks=1 in ASAN_OPTIONS.

The leak is fixed by re-introducing the exceptional case of a parent
holding a strong reference to the child, in just this one case.

Change-Id: Iabc26990d39757b0abe0cddf69e76e88e40fba40
Reviewed-by: Lars Knoll &lt;lars.knoll@qt.io&gt;
Reviewed-by: Michael Brasser &lt;michael.brasser@live.com&gt;
(cherry picked from commit 01df9e5f46fd05a80f8f6fcaa91204e6184ded6f)
</pre>
</div>
</content>
</entry>
<entry>
<title>QQuickItem: Guard against null deref in transformations</title>
<updated>2018-05-02T16:23:05+00:00</updated>
<author>
<name>Robin Burchell</name>
<email>robin.burchell@crimson.no</email>
</author>
<published>2018-04-09T13:41:02+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=b5bc53a1cb26968414282245bb72460b29dd87d2'/>
<id>b5bc53a1cb26968414282245bb72460b29dd87d2</id>
<content type='text'>
Change-Id: Ieb14322c104d816842e04e521b556bfc11855f1c
Task-number: QTBUG-67024
Reviewed-by: Robin Burchell &lt;robin.burchell@crimson.no&gt;
Reviewed-by: Michael Brasser &lt;michael.brasser@live.com&gt;
(cherry picked from commit f9686bc68696ad1e99a0587f15d05300d003d990)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Change-Id: Ieb14322c104d816842e04e521b556bfc11855f1c
Task-number: QTBUG-67024
Reviewed-by: Robin Burchell &lt;robin.burchell@crimson.no&gt;
Reviewed-by: Michael Brasser &lt;michael.brasser@live.com&gt;
(cherry picked from commit f9686bc68696ad1e99a0587f15d05300d003d990)
</pre>
</div>
</content>
</entry>
<entry>
<title>QQuickContext2DFBOTexture: use normalized sub rect when using FBO with POT texture</title>
<updated>2018-04-23T09:10:56+00:00</updated>
<author>
<name>Richard Moe Gustavsen</name>
<email>richard.gustavsen@qt.io</email>
</author>
<published>2017-12-14T11:16:31+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=40e54cedaad19263c0dacadbb96a971b53c31b90'/>
<id>40e54cedaad19263c0dacadbb96a971b53c31b90</id>
<content type='text'>
When creating a Canvas item with renderStrategy set to Canvas.FramebufferObject
we might end up creating an FBO with a POT texture (e.g on iOS) that doesn't match
the size of the canvas. The result will be that the image turn out scaled.

QSGTexture::normalizedTextureSubRect() is a function that needs to be
overridden to be used. So this patch will create a subclass of QSGPlainTexture
that overrides it, and returns the normalized subrect inside the
FBO that that matches the size of the canvas.

Task-number: QTBUG-59192
Change-Id: I0f0e57e117656df21a94b7015bd160c44485046d
Reviewed-by: Morten Johan Sørvig &lt;morten.sorvig@qt.io&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When creating a Canvas item with renderStrategy set to Canvas.FramebufferObject
we might end up creating an FBO with a POT texture (e.g on iOS) that doesn't match
the size of the canvas. The result will be that the image turn out scaled.

QSGTexture::normalizedTextureSubRect() is a function that needs to be
overridden to be used. So this patch will create a subclass of QSGPlainTexture
that overrides it, and returns the normalized subrect inside the
FBO that that matches the size of the canvas.

Task-number: QTBUG-59192
Change-Id: I0f0e57e117656df21a94b7015bd160c44485046d
Reviewed-by: Morten Johan Sørvig &lt;morten.sorvig@qt.io&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge remote-tracking branch 'origin/5.9.5' into 5.9</title>
<updated>2018-04-11T10:21:14+00:00</updated>
<author>
<name>Qt Forward Merge Bot</name>
<email>qt_forward_merge_bot@qt-project.org</email>
</author>
<published>2018-04-11T10:21:13+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=f23d1d54a06b0f3473e17300c3a1c495bcc25fdc'/>
<id>f23d1d54a06b0f3473e17300c3a1c495bcc25fdc</id>
<content type='text'>
Change-Id: Id51ad58cceaa8d00999cf1881c28d179a564fd97
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Change-Id: Id51ad58cceaa8d00999cf1881c28d179a564fd97
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix crash when calling QQmlEngine::clearComponentCache()</title>
<updated>2018-04-10T07:08:02+00:00</updated>
<author>
<name>Simon Hausmann</name>
<email>simon.hausmann@qt.io</email>
</author>
<published>2018-03-15T16:08:21+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=67b091c49cafb607db9756333aaa7229817f7348'/>
<id>67b091c49cafb607db9756333aaa7229817f7348</id>
<content type='text'>
We must protect various resources in the type loader with our existing
lock. The QQmlTypeLoaderQmldirContent is now value based, so that we can
release the lock on the shared cache early. Copying it involves
adjusting the refcount of the QHash and QString instances in the
QQmlDirParser.

The safety of this was verified with a TSAN build and the example
supplied in the task. It crashed reliably with TASN errors first and
with this patch it runs without errors.

Task-number: QTBUG-41465
Change-Id: I616843c4b8bdfd65d1277d4faa8cb884d8e77df8
Reviewed-by: Lars Knoll &lt;lars.knoll@qt.io&gt;
(cherry picked from commit a3ad52526f79c1528f170c8affe5af00b68ca61d)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
We must protect various resources in the type loader with our existing
lock. The QQmlTypeLoaderQmldirContent is now value based, so that we can
release the lock on the shared cache early. Copying it involves
adjusting the refcount of the QHash and QString instances in the
QQmlDirParser.

The safety of this was verified with a TSAN build and the example
supplied in the task. It crashed reliably with TASN errors first and
with this patch it runs without errors.

Task-number: QTBUG-41465
Change-Id: I616843c4b8bdfd65d1277d4faa8cb884d8e77df8
Reviewed-by: Lars Knoll &lt;lars.knoll@qt.io&gt;
(cherry picked from commit a3ad52526f79c1528f170c8affe5af00b68ca61d)
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix bug preventing ungrabMouse() on TouchCancel</title>
<updated>2018-04-09T03:36:36+00:00</updated>
<author>
<name>Daniel d'Andrada</name>
<email>daniel.dandrada@luxoft.com</email>
</author>
<published>2017-10-09T15:39:44+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=2597e43497aa8a223d65c669f07bd2e8fdf7e1f1'/>
<id>2597e43497aa8a223d65c669f07bd2e8fdf7e1f1</id>
<content type='text'>
The order matters. There won't be a mouseGrabberItem() after
the cancelExclusiveGrabImpl() call. So ungrab the mouse before
calling it, not after.

This cherry-pick includes some other changes to
tst_qquickwindow.cpp (parts of
9d8fe2ac121162c15be6728495be2235b728325a) that enable the
cherry-picked test function touchEvent_cancelClearsMouseGrab()
to be the same as it is in 5.10 branch.

Task-number: QTBUG-63680
Task-number: QTBUG-67445
Change-Id: I1ba6401c5d8eb3417907eb1e6ca20816b501f3ac
Reviewed-by: Qt CI Bot &lt;qt_ci_bot@qt-project.org&gt;
Reviewed-by: Shawn Rutledge &lt;shawn.rutledge@qt.io&gt;
(cherry-picked from 0821180dc833376a738742e33f728983b9ca6f84)
Reviewed-by: Tasuku Suzuki &lt;tasuku.suzuki@qt.io&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The order matters. There won't be a mouseGrabberItem() after
the cancelExclusiveGrabImpl() call. So ungrab the mouse before
calling it, not after.

This cherry-pick includes some other changes to
tst_qquickwindow.cpp (parts of
9d8fe2ac121162c15be6728495be2235b728325a) that enable the
cherry-picked test function touchEvent_cancelClearsMouseGrab()
to be the same as it is in 5.10 branch.

Task-number: QTBUG-63680
Task-number: QTBUG-67445
Change-Id: I1ba6401c5d8eb3417907eb1e6ca20816b501f3ac
Reviewed-by: Qt CI Bot &lt;qt_ci_bot@qt-project.org&gt;
Reviewed-by: Shawn Rutledge &lt;shawn.rutledge@qt.io&gt;
(cherry-picked from 0821180dc833376a738742e33f728983b9ca6f84)
Reviewed-by: Tasuku Suzuki &lt;tasuku.suzuki@qt.io&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix out of bounds reads in Array.concat</title>
<updated>2018-04-03T08:36:56+00:00</updated>
<author>
<name>Lars Knoll</name>
<email>lars.knoll@qt.io</email>
</author>
<published>2018-03-19T14:07:28+00:00</published>
<link rel='alternate' type='text/html' href='https://code.qt.io/cgit/qt/qtdeclarative.git/commit/?id=560360a1b7218865b71ae284dc920c38ffdd60d6'/>
<id>560360a1b7218865b71ae284dc920c38ffdd60d6</id>
<content type='text'>
In some cases, when our simple array data had an offset and
data would wrap around, ArrayData::append would write out
of bounds data into the new array, leading to crashes.

Task-number: QTBUG-51581
Change-Id: I55172542ef0b94d263cfc9a17d7ca49ec6c3a565
Reviewed-by: Simon Hausmann &lt;simon.hausmann@qt.io&gt;
(cherry picked from commit f495d4b660107536d0a67ba48e88550278f13893)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In some cases, when our simple array data had an offset and
data would wrap around, ArrayData::append would write out
of bounds data into the new array, leading to crashes.

Task-number: QTBUG-51581
Change-Id: I55172542ef0b94d263cfc9a17d7ca49ec6c3a565
Reviewed-by: Simon Hausmann &lt;simon.hausmann@qt.io&gt;
(cherry picked from commit f495d4b660107536d0a67ba48e88550278f13893)
</pre>
</div>
</content>
</entry>
</feed>
