M110 is shaping up to be a great release!
- JPEG-XL functionality RESTORED; thanks to @jonsneyers @mo271 and @gz83 for helping with this.
There is a new repo for the source code for this, used as a submodule in this repo. > https://github.com/Alex313031/thorium-libjxl
In case you didn't know, Google decided to be a d**k and remove JPEG-XL support after M109, as well as Windows 7/8/8.1 support. - Thorium now supports the AC3 codec, including in HEVC/H.265 videos. Thanks to @midzer for helping find a patch, which I manually converted to work on M110.
- HEVC/H.265 videos now support all profiles.
- More optimization flags for V8, Chromium's Javascript engine.
- Added four new chrome://flags flags:
– chrome://flags/#force-gpu-mem-available-mb - Set available VRAM to be used by Thorium. Options are 128, 256, 512, and 1024 Mb. Useful for systems with very low or very high video memory. The default (if unset) is 512 Mb.
– chrome://flags/#enable-native-gpu-memory-buffers - Enable native CPU-mappable GPU memory buffer support on Linux. (Linux only) You can see the effect of this on chrome://gpu in the "GpuMemoryBuffers Status" section.
– chrome://flags/#double-click-close-tab - A flag that @gz83 came up with and we both implemented. Allows you to close a tab by simply double-clicking on it, similar to an option in Vivaldi.
– chrome://flags/#show-fps-counter - Show a F.P.S. counter on each display, which also shows used/available GPU memory. Useful for Web development. - Logo has had padding removed, and a new logo was created for the windows installer .exe.
- New desktop action on Linux, to "Open New Window with a temporary profile". This can be used even if Thorium is already running. It will make a new profile in /tmp, and use that. NOTE: Upon system restart, the /tmp dir is cleared.
- Thorium mascot image added to chrome://version page, under the copyright (for fun)
IMPORTANT for Windows Users
– Two new flags from ungoogled chromium, to enable truly portable usage were added. They unencrypt your user data dir, and remove tying it to a specific machine. Meaning you can drag the .zip around with you from machine to machine, and you wont lose passwords, extensions, etc. You will need to back up your current config, or start with a fresh one. I.E. you can go from Unencrypted > Encrypted, but not Encrypted (the default) > Unencrypted. I should have introduced these a long time ago. Sorry if this annoys users of the portable .zips. Note that enabling these flags is inherently less secure.
They are:
chrome://flags/#disable-encryption and
chrome://flags/#disable-machine-id