e3kskoy7wqk/Chromium-for-windows-7-REWORK 149.0.7827.53 on GitHub

Update to chromium 149.0.7827.53

This build is now a full 100 major versions higher than the last officially supported Windows XP build, which was 49.0.2623.112.

Fixes:

changes and improvements:

features:

(#1) Restored DXVAVideoDecodeAccelerator.
(Experimental) WebGL hardware acceleration can now be enabled on Windows XP by installing the Microsoft Visual C++ Redist 2015-2019 for Windows XP, or alternatively by extracting the files from either the x86 or x64 folder inside libgles_and_dwrite_chromium_xp.zip into the directory containing chrome.exe and overwriting any existing files. You also need to add the command line parameter --use-angle=d3d9 ¹²³.
(Experimental) DWrite font rendering can now be enabled on Windows XP by extracting the files from either the x86_dwrite or x64_dwrite folder in libgles_and_dwrite_chromium_xp.zip into the directory containing chrome.exe. (many thanks to @mjd7989)
(#61) Added d3d11-video-decoder to the chrome://flags page.
Added disable-direct-write to the chrome://flags page. This allows you to enable GDI font rendering.
The --disable-dwm-composition command line option. This allows you to disable use of DWM composition for top level windows.
(#79) MV2 has been supported. (thanks to @bershanskiy)

Tips:

Enable color emojis: First, make sure the DWrite related files from libgles_and_dwrite_chromium_xp.zip have been copied to the correct location. Then, install the Segoe UI Emoji font (seguiemj.ttf) from Windows 10.

Footnotes

Whether hardware acceleration can be enabled also depends on your hardware. Hardware acceleration is only available on certain hardware. ↩
Using --use-angle=d3d9 will prevent WebGL 2 from being enabled. This means you need to make a trade off based on your needs. If you care about WebGL 2 and do not mind losing hardware acceleration, do not add --use-angle=d3d9. Otherwise, add --use-angle=d3d9. ↩
(https://github.com/e3kskoy7wqk/Chromium-for-windows-7-REWORK/issues/13) swiftshader is always available, which means even in the worst case, WebGL can still be used via software acceleration and will not be completely disabled. ↩