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

Update to chromium 149.0.7827.53
Brave Browser v1.93.22 (Chromium 149.0.7827.54) (You need to rename the brave.exe to another name in order to launch the Brave Browser, you also need to place api-ms-win-core-winrt-error-l1-1-0.dll for the corresponding architecture into system32.)

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:

(#64, #74) An error caused by LoadLibraryExW.
(#84) Speedtest crashes Brave Browser.

changes and improvements:

(#79) Use a simpler way to support MV2. (thanks to @bershanskiy)
(#62) The original libgles_and_dwrite_chromium_xp.zip has been updated to webgl_hw_and_dwrite.zip, which now includes DWrite.dll specifically created for Windows XP/Vista and Windows 7/8.1, an updated D3DCompiler, and more detailed usage instructions. (thanks to @mjd7989)

features:

(#1) Restored DXVAVideoDecodeAccelerator.
(Experimental) WebGL D3D9 hardware acceleration ¹²³ and DirectWrite on Windows XP/Vista, as well as color emojis on Windows XP through Windows 8.1. See webgl_hw_and_dwrite.zip created by @mjd7989. (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)

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. ↩