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

Update to chromium 154.0.8032.0

changes and improvements:

(#35) I have updated the TLS fix code to address several potential issues that could lead to crashes. Both Chromium and Firefox now use exactly the same code for TLS fixes on Windows XP/Server 2003.

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