summaryrefslogtreecommitdiffstats
path: root/tests/auto/corelib/text/qstringbuilder
diff options
context:
space:
mode:
authorAxel Spoerl <axel.spoerl@qt.io>2023-06-12 14:42:27 +0200
committerAxel Spoerl <axel.spoerl@qt.io>2023-06-13 20:00:31 +0000
commit8d1304f4f2cbc8e7e0f1b9c48236dde548b2bc8d (patch)
tree673a377063640602dcd46c88ba3112fd6c91ed62 /tests/auto/corelib/text/qstringbuilder
parent72d660843b126aee356a637ba5b6c86c88f46f6b (diff)
QGtk3Interface: Explicitly add monospace font provider
In case the current GTK3 theme has no monospace font defined, a monospace font requested by a Qt application can trigger a GTK warning "Theme parsing error: <data>:1:0: Expected a valid selector". The warning is triggered by Qt requesting "{font-family: monospace;}". In this case: => ensure fallback to GTK standard monospace font => request "* {font-family: monospace;}" to avoid the warning Task-number: QTBUG-112896 Pick-to: 6.6 6.5 Change-Id: I24a8da62908af9b153245f53026af60e63a600d7 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io>
Diffstat (limited to 'tests/auto/corelib/text/qstringbuilder')
0 files changed, 0 insertions, 0 deletions