qt6-bb10

History

Thiago Macieira c07c2d5a52 CBOR/JSON: fix crash when comparing strings with different length Amends `8e5ce9cd36`, which introduced the QtPrivate::equalStrings() call. At that time, equalStrings() had already required equal lengths (see `1560e0161a`), so no excuse. [ChangeLog][QtCore][QCborMap and QJsonObject] Fixed bug that could result in a crash or failing to find a entry in the map/object with non- ASCII keys. Manual conflict resolution for 6.9: - Port from keyView() to key(), because the former is a 6.10+ feature. Fixes: QTBUG-133744 Change-Id: I6b0f8b0a2e47d3ef905afffda6c4c079814a0914 Reviewed-by: Marc Mutz <marc.mutz@qt.io> (cherry picked from commit 54daec43a041cb69cff31cbfd1dd0b7127e8ba87) (cherry picked from commit 8e94b67ba11fecfee134950eaae5c5b29812e82c) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> (cherry picked from commit d4a90a3f3013eae4e837fbd2df63d5803f19608a)		2025-03-17 13:10:27 +00:00
..
auto	CBOR/JSON: fix crash when comparing strings with different length	2025-03-17 13:10:27 +00:00
baseline	Raster engine: Fix painting of zero length, square cap wide lines	2025-03-01 04:54:25 +00:00
benchmarks	Add maybe_unused in benchmark to guard against nodiscard in the future	2025-03-03 08:21:00 +00:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
libfuzzer	Complete color space toICC write	2024-05-31 16:24:50 +02:00
manual	Improve hinted rendering quality on Windows	2025-02-08 13:53:37 +00:00
shared	De-duplicate the disabling of crash dialogs in our unit tests	2025-01-20 21:30:42 +00:00
testserver	Add REUSE.toml files	2024-11-07 08:38:49 +01:00
CMakeLists.txt	Rid of 'special case' markers	2023-04-13 18:30:58 +02:00
README	…

README

This directory contains autotests and benchmarks based on Qt Test. 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.