qt/qtdeclarative.git, branch v5.9.9

Add changes file for Qt 5.9.9

2019-12-03T07:18:54+00:00

+ 0e65d4f97eb2c0404459d79d326628d43c0bbc71 Bump version

Change-Id: If58219be3ea1f58d3c8f87d5b7389eeb61afe6f5
Reviewed-by: Jani Heikkinen

Bump version

2019-05-23T15:52:46+00:00

Change-Id: I45bd34a11cd25a5d6e1778ae43ef37a487733896

Merge remote-tracking branch 'origin/5.9.8' into 5.9

2019-04-25T13:59:47+00:00

Change-Id: I5be12e0e63c3264d578a69a4a8c0c3fbf66d0efd

Add changes file for Qt 5.9.8

2019-04-02T10:10:14+00:00

+ 2ededacdde179357eb686901202789bbee35771a Fix crash in QQuickAnimatorProxyJob::sceneGraphInitialized()
+ f12e6003831b8aedac99e89b38665da64d0804ca Bump version
+ 3793a264b6eeecae5d4c44747fbe46c0d255a3c5 Silence a GCC 8 warning in qv4string
+ 89cdd5575bba856035946926f5575705ebd6c1b7 Silence a GCC 8 warning in qqmljsparser
+ cbb11c57773713ca18384a6c45e5dcd96330850a Silence a GCC 8 warning in qv4engine
+ 10bef7aa883cab99cfcb526d6f996f033b3f1fc0 Silence a GCC 8 warning in qquickanimation
+ 6626572f8604b2789da9253ccd7aa92d3f6013e9 Silence GCC 8 warnings in qpodvector
+ 93c3844a84f0acd382be5021d2ebe896269b7277 Silence another GCC 8 warning in qpodvector
+ 24af53cfeb998dcf3a6c6d49d312e50809a4a324 V4 Date: fix what we can within ECMA 262's limitations

Change-Id: Idc45484077f4dddca3111defb8e0b787fef0334a
Reviewed-by: Shawn Rutledge 
Reviewed-by: Ulf Hermann

Use Los Angeles to represent PST8PDT, not Vancouver

2019-04-02T10:10:09+00:00

This amends commit 24af53cfeb998dcf3a6c6d49d312e50809a4a324.

The very last test (15.9.5.43-0-8) in the ES test-suite relies on
constructing a time *just* outside the valid range, to provoke (and
check it gets) a RangeError.  However, it uses the current time-zone
offset in computing this; and the local time -> UTC conversion in the
Date constructor uses the zone information for the zone at the given
time.  The TZ db uses each zone's local mean solar time for the period
before a formal zone was introduced; and Vancouver is further West
than the nominal meridian for its zone.  The test code throws in an
hour's correction in case it's run in daylight-saving time, which
would put the test time, when run during standard time, an hour (and a
millisecond, rather than just the millisecond) outside the valid Date
range, so as to ensure it's still a ms outside when the test is run
during DST.  However, the 12m28s mean solar offset overcomes the 1ms
and puts the time back in range durign DST (but still 47m32.001s
outside during standard time, which is why this problem only surfaced
when North America entered summer time).  Fortunately, Los Angeles is
further East than the meridian in question, and uses the same zone.

Task-number: QTBUG-67010
Change-Id: I58fd7bf14366ebe5842b8abd7e6802c9c78ca27e
Reviewed-by: Lars Knoll 
Reviewed-by: Simon Hausmann 
(cherry picked from commit fb20d2f7b149725b0fcc8e5bbb377cd6dababc9b)
Reviewed-by: Edward Welbourne

V4 Date: fix what we can within ECMA 262's limitations

2018-12-07T16:50:57+00:00

Use QDateTime and QTimeZone to simplify code (when we can).
Note which defective methods are so because the ECMAScript spec
requires those defects, reference my bug report against those defects.
Fix currentTime to return a UTC time.

Fix getLocalTZA to actually deliver the standard offset, without
daylight-saving corrections.

Fix DaylightSavingTA(t) to return the difference between current
standard time offset and pertinent total offset at time t (explaining
why that's the least broken answer), rather than assuming DST is one
hour when active.  (In some places it's half an hour, in some places
two hours; and the bugs in the spec break UTC() and LocalTime() if we
only return actual DST offset, without adjusting for historical
changes to standard offset.)

Fix tests to use actual IANA IDs for zones.

Change QTime-to-Time conversion to use a modernish date, for which
time-zone data is likely to at least be consistently handled, instead
of MakeDay(0, 0, 0); that's (nominal proleptic Gregorian) 2 BC,
December 31st (represented denormally) for which any time-zone data we
have is artificial and contrived.  I chose Cassini's third centennary,
as it's not likely to be near any zone transitions and is within the
era of sane time-zone data.

Task-number: QTBUG-72109
Task-number: QTBUG-56787
Change-Id: I5f21ee2010070a5c1798134fdd2915a723208fd9
Reviewed-by: Lars Knoll 
(cherry picked from commit 2b8b7a162be52f8cd6c2bc39f498a1ddfb59dd68)
Reviewed-by: Liang Qi

Silence another GCC 8 warning in qpodvector

2018-11-19T20:12:09+00:00

qtdeclarative/src/qml/qml/ftw/qpodvector_p.h:119:22: error: ‘void* memmove(void*, const void*, size_t)’ writing to an object of non-trivially copyable type ‘class QQuickBasePositioner::PositionedItem’; use copy-assignment or copy-initialization instead [-Werror=class-memaccess]
             ::memmove(m_data + idx, m_data + idx + count,

Change-Id: I049703a0a6bb4432dfd3d3ce3c8cef13e9c2e31a
Reviewed-by: Simon Hausmann 
(cherry picked from commit 55f71cdfc5746a71bcb89f0fa4ff3447cb8b5514)
Reviewed-by: Ville Voutilainen

Silence GCC 8 warnings in qpodvector

2018-11-19T20:12:04+00:00

qpodvector_p.h:90:34: error: ‘void* realloc(void*, size_t)’ moving an object of non-trivially copyable type ‘class QQuickBasePositioner::PositionedItem’; use ‘new’ and ‘delete’ instead [-Werror=class-memaccess]
             m_data = (T *)realloc(m_data, m_capacity * sizeof(T));

qpodvector_p.h:94:22: error: ‘void* memmove(void*, const void*, size_t)’ writing to an object of non-trivially copyable type ‘class QQuickBasePositioner::PositionedItem’; use copy-assignment or copy-initialization instead [-Werror=class-memaccess]
             ::memmove(m_data + idx + 1, m_data + idx, moveCount * sizeof(T));

Change-Id: I37088986a0f8613152a355ed6f3f9572316fa607
Reviewed-by: Simon Hausmann 
(cherry picked from commit 622decbe3b2478496295e57d59f9cf16a9f70a13)
Reviewed-by: Ville Voutilainen

Silence a GCC 8 warning in qquickanimation

2018-11-19T20:11:59+00:00

qtdeclarative/src/quick/util/qquickanimation.cpp:1669:109: error: cast between incompatible function types from ‘QVariant (*)(qreal&, qreal&, qreal)’ {aka ‘QVariant (*)(double&, double&, double)’} to ‘QVariantAnimation::Interpolator’ {aka ‘QVariant (*)(const void*, const void*, double)’} [-Werror=cast-function-type]
         d->interpolator = reinterpret_cast(&_q_interpolateClockwiseRotation);

Change-Id: I8da70ef666deb3cbdbf05c5bac89f705a2ec5ea8
Reviewed-by: Simon Hausmann 
(cherry picked from commit 12afec6c2f89264b7344f9221763898c77a396fc)
Reviewed-by: Ville Voutilainen

Silence a GCC 8 warning in qv4engine

2018-11-19T20:11:56+00:00

qtdeclarative/src/qml/jsruntime/qv4engine.cpp:913:78: error: ‘void* memcpy(void*, const void*, size_t)’ writing to an object of type ‘struct QV4::Property’ with no trivial copy-assignment [-Werror=class-memaccess]
             memcpy(argumentsAccessors, oldAccessors, oldSize*sizeof(Property));

Change-Id: I6e3d6a1a26fda33aa47c315a183edba9dcd0c0b9
Reviewed-by: Simon Hausmann 
(cherry picked from commit d0c1b1e8f9dcbde14154029f7df0acc3888f675a)
Reviewed-by: Ville Voutilainen