However, Window.devicePixelRatio doesn't exist (it would be in the Screenimport, not Window), so the conditional always evaluates to true, so we alwaysget QtRendering, even at integer scale factors and non-HiDPI. This is what wewant for a non-integer scale factor since the alternative is even worse (seehttps://bugreports.qt.io/browse/QTBUG-67007), but for non-hi-dpi and integerscale factors, we should not use QtRendering, since it results in text that isever-so-slightly lighter and wispier, which some very sensitive people can pickup on. See the attached comparison: the string on the top was rendered withQtRendering, and the one on the bottom with NativeRendering. Note how theQtRendering version is slightly lighter.

I plan to submit a patch later today if nobody else beats me to it first.

--You are receiving this mail because:You are watching all bug changes.

Summary:QQC2-desktop-style was attempting to force the use of `Text.QtRendering` fornon-integer scale factors. However, it was accidentally using it everywhere.This patch resolves the issue, and makes it use `Text.QtRendering` only fornon-integer scale factors.FIXED-IN: 5.45

Test Plan:No visual changes when there is a non-integer scale factor.

System Settings before, no scale factor:{F5751414}

System Settings after, no scale factor:{F5751415}

Discover before, no scale factor:{F5751416}

Discover after, no scale factor:{F5751418}

To notice the differences, you will probably have to open them in differenttabs, zoom in with {key Meta +}, and switch between the tabs.