Also, while these changes are specific to Edge, we hope to be able to contribute them back to Chromium so that all Chromium-based browsers on Windows enjoy a consistent font rendering experience. Today, the changes described above must be manually enabled, but after a rollout period we plan to have this behavior enabled by default in the Edge 92 stable channel. The difference is even more pronounced on CJK characters, where anti-aliased pixels comprise a larger percentage of each rendered glyph. Consequently, font rendering with the hardcoded settings in Skia results in text that is subtly lighter than Windows’ system defaults. The final compositing of glyph bitmaps in Chromium is handled by the Skia graphics library and does not respect the Windows system settings for contrast enhancement and gamma correction of anti-aliased text.
#Zoom microsoft edge webview2 code#
This enables code reuse across platforms, but on Windows, the results are typically different than the rest of the system’s text rendering. The benefit of using DirectWrite is that certain system-wide user settings are respected and use the same rendering pipeline across all other native Windows applications.Ĭhromium, by contrast, only utilizes DirectWrite for part of the text-rendering pipeline: font enumeration, glyph information retrieval, and glyph bitmap generation it handles its own text shaping, layout, and rendering. Like many native Windows applications, Legacy Microsoft Edge utilized the DirectWrite framework to render glyphs to the screen. To give some context as to why this change was made, we need to look at how the Legacy Microsoft Edge rendered text. Left is ClearType and right is Grayscale.īehind the scenes, the registry key KEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DISPLAY1 is modified to a value between 50 and 400. Font rendering at maximum contrast level (400).