Contact emails [email protected]
[email protected] Summary Historically, Chromium/Skia has used compile-time constants for text contrast and gamma, with different values hard-coded per platform. This means that these values are not adjustable by the end user. Windows has a ClearType Text Tuner that guides the user through various contrast and gamma values for text rendering. Native applications generally automatically pick up these values if they use a DirectWrite based text stack. Chromium uses Skia for text rendering, and thus was not picking up these user adjustments on Windows. Lack of support for these adjustments in Chromium-based browsers has been a long-standing user complaint: * https://issues.chromium.org/issues/40918273 * https://issues.chromium.org/issues/40180569 * https://issues.chromium.org/issues/40668526 * https://issues.chromium.org/issues/40037624 * https://issues.chromium.org/issues/40067987 The Microsoft Edge Team have made several changes in both Chromium and Skia to allow for dynamic values of text contrast and gamma, which is currently behind the flag "UseGammaContrastRegistrySettings" (added in https://chromium-review.googlesource.com/c/chromium/src/+/5031537). This behavior has been experimented with in Edge since 2021 (see https://blogs.windows.com/msedgedev/2021/06/02/improving-font-rendering-in-microsoft-edge/) and has been well-received by users. We plan to enable this flag by default in Chromium 124. Feedback and suggestions are encouraged! ChromeStatus entry: Windows ClearType Text Tuner Integration - Chrome Platform Status (chromestatus.com)<https://chromestatus.com/feature/6236420349100032> -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/BL0PR00MB077114832200DF6C40C86A8DD6292%40BL0PR00MB0771.namprd00.prod.outlook.com.
