qt5base-lts

History

Eskil Abrahamsen Blomfeldt 6b02473e1e Fix overlapping text for Osaka font on macOS The Osaka font on macOS has all zeroes in the OS/2 table, probably because it is not intended to be cross-platform. In Qt 6 (since `f761ad3cd9`) we are trying using the same vertical metrics on all platforms, but this only works if they are valid. To work around this issue, we detect the case when ascent/descent values are both 0, since this is very unlikely to be intentional, so we fall back to the system-provided ascent and descent in these cases. Adding the test also revealed that we had missed the check for a macOS-specific bitmap font format when skipping the check for bitmap fonts in `7a18b7e2c2`. [ChangeLog][macOS][Text] Fixed a problem where using the Osaka font would lead to overlapping text. Pick-to: 6.2 Fixes: QTBUG-96880 Change-Id: Ifea7918641a68829e8f5ef20a4fb61c0a7e5b757 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>		2021-12-02 07:54:39 +01:00
..
auto	Fix overlapping text for Osaka font on macOS	2021-12-02 07:54:39 +01:00
baseline	Never handle scrollbars styled with box or border changes as transient	2021-11-29 16:02:28 +01:00
benchmarks	QWaitCondition: also benchmark std::condition_variable{,_any}	2021-11-26 18:28:50 +01:00
global
libfuzzer	CMake: Bump almost all cmake_minimum_required calls to 3.16	2021-09-22 19:36:49 +02:00
manual	Rename and restructure the baseline (lancelot) testing code	2021-11-16 14:01:50 +01:00
shared	QtBase: replace windows.h with qt_windows.h	2021-11-23 12:53:46 +08:00
testserver	Network self-test: make it work with docker/containers	2020-11-17 19:56:06 +01:00
CMakeLists.txt	CMake: Refactor optimization flag handling and add optimize_full	2020-10-06 10:07:05 +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.