qt6-bb10

History

Thiago Macieira d4c7da9a07 CBOR: fix sorting of UTF16-to-UTF16 strings This amends commit `394788c68e` (its ChangeLog applies to this commit too). That fixed sorting of UTF8-to- UTF16, but when adding more unit tests, I've discovered that some UTF-16 strings also sorted incorrectly. There were two problems: First, we were assuming that we could rely on the UTF-16 length as a proxy for the UTF-8 one, but that's not true for some cases: * both 1-, 2- and 3-codepoint UTF-8 sequences are 1 codepoint in UTF-16, so some strings would have identical UTF-16 length * 4-codepoint UTF-8 sequences shrink to 2-codepoint UTF-16 ones (2:1) but 3-codepoint UTF-8 sequences shrink to 1 (3:1), so some strings would be longer in UTF-16 but shorter in UTF-8. Second, QtPrivate::compareStrings performs UTF-16 codepoint comparisons not Unicode character ones, so surrogate pairs were sorting before U+E000 to U+FFFF. To fix all of this, we need to decode the UTF-16 string into UTF-32 and calculate the length of that in UTF-8 to be sure we have the sorting order right. Since this is a slight behavior change with a performance penalty, I am choosing to backport only to 6.7. The penalty mostly does not apply to 6.8 due to commit `61556627f2`. Pick-to: 6.7 Change-Id: If1bf59ecbe014b569ba1fffd17c4c4ddcc874aac Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>		2024-04-12 21:41:16 -07:00
..
auto	CBOR: fix sorting of UTF16-to-UTF16 strings	2024-04-12 21:41:16 -07:00
baseline	StyleSheet: respect a font weight set for header sections	2024-04-11 04:35:22 +02:00
benchmarks	qHash: implement an AES hasher for QLatin1StringView	2024-03-12 18:23:09 -07:00
global	…
libfuzzer	Add CMYK support to QColorSpace	2024-04-12 21:53:54 +02:00
manual	Add CMYK support to QColorSpace	2024-04-12 21:53:54 +02:00
shared	Add configure feature for Metal	2024-03-19 14:52:48 +01:00
testserver	Correct license for tools files	2024-03-05 12:59:21 +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.