diff options
| author | Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io> | 2019-02-14 08:10:03 +0100 |
|---|---|---|
| committer | Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io> | 2019-02-14 08:01:05 +0000 |
| commit | 793cfa20a3c5a44be5a67c31f6035fb4dc193edc (patch) | |
| tree | ff5fc010829bb8414dae190469b8629e3a62ea37 /tests/auto | |
| parent | 37e545e0f133ff6be9e9071e9419b0996e41fcdd (diff) | |
[Windows] Fixed regression when creating fallback fonts
In 3ccdeb4b58b681bb3a0a43f926f81fd94f527680, we removed the
specialized multi font engine on Windows, causing us to go
through the same code path when loading fallbacks as on
other platforms.
When combined with 97f73e957756753b09a778daf2ee8f0ddb97f746,
this caused an error, because the code in
QFontEngineMulti::loadEngine() only overrode the families
list, but not the singular family in the request. In the
QRawFont test, this would cause the requested fallback font
to correctly have "MS Shell Dlg2" as the only font in the
families list, but the request.family would still be
"QtBidiTestFont", the name of the main font. The singular family
in the request was preferred by the windows font database when
creating the LOGFONT. We would therefore load the latter for
the fallback as well and since it still does not support the
characters in question, we would continue searching.
Fixes: QTBUG-72836
Change-Id: I1787b57febcf6030d5c5b09bc2ef2c9558f05beb
Reviewed-by: Andy Shaw <andy.shaw@qt.io>
Diffstat (limited to 'tests/auto')
| -rw-r--r-- | tests/auto/gui/text/qrawfont/BLACKLIST | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/tests/auto/gui/text/qrawfont/BLACKLIST b/tests/auto/gui/text/qrawfont/BLACKLIST deleted file mode 100644 index c076f11635..0000000000 --- a/tests/auto/gui/text/qrawfont/BLACKLIST +++ /dev/null @@ -1,3 +0,0 @@ -# QTBUG-72836 -[unsupportedWritingSystem] -windows |