80b39d24ec
The variation selectors only make sense in the context of the previous glyph and should never be shaped by themselves, therefore we should not pick a different font engine for these even if the cmap does not support it. They are sometimes needed to properly resolve the emojis, but the OpenType rules in the font may not be written with them in mind. If the cmap lookup fails for these, then Harfbuzz will map them to a zero-width space, thus ignoring them when resolving the OpenType rules. We treat these the same as other control characters and just ignore them when doing font merging. Note: This was handled through an ad hoc mechanism prior to the introduction of the emoji segmenter in 6.9.When the emoji segmenter is disabled, we still use this mechanism, which depends on us not ignoring the character in that case. Fixes: QTBUG-133480 Change-Id: I8fa4e8d5e1aabad0946b8fd3fff044e2b2af5d0e Reviewed-by: Lars Knoll <lars@knoll.priv.no> (cherry picked from commit cf674f38450f623d94e5695a221a186c0e551e27) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
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.