1fc939a870
If you do that in JS you get "undefined" and "null", respectively. Our C++-based conversion methods should do the same. The documentation for QJSValue also suggests that QJSValue::toFoo() should behave like qjsvalue_cast<Foo>(x). So far QJSValue::toString() produced "undefined" and "null" while qjsvalue_cast<String>(x) produced an empty string. [ChangeLog][QtQml][Important Behavior Changes] qjsvalue_cast<QString>(x) now returns "undefined" for undefined JS values, and "null" for null JS values. This is in line with what QJSValue::toString() does, and also what JavaScript itself would produce when stringifying such values. Previously, qjsvalue_cast would return an empty string for both, undefined and null JS values. Change-Id: Ib93f4157f092ed769dca946541ffbcfbd7317d4c Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io> |
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer/qml | ||
| manual | ||
| system | ||
| testapplications | ||
| CMakeLists.txt | ||
| README | ||
README
This directory contains autotests and benchmarks based on QTestlib. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.
Linux X11:
* The user must be logged in to an active desktop; you can't run the
autotests without a valid DISPLAY that allows X11 connections.
* The tests are run against a KDE3 or KDE4 desktop.
* Window manager uses "click to focus", and not "focus follows mouse". Many
tests move the mouse cursor around and expect this to not affect focus
and activation.
* Disable "click to activate", i.e., when a window is opened, the window
manager should automatically activate it (give it input focus) and not
wait for the user to click the window.