Hi,Running --headless=new does work for me (with chromium 132), despite what the bug reports say. I tried building headless_shell, but it requires an additional patch to build and the resulting binary is somehow larger[0] than content_shell, which we're planning to drop. So if we did ship it, it would be in a separate package (eg, 'chromium-headless-old').
Are you certain that --headless=new with additional args (eg, --temp-profile or something) won't work for your use case?
Thanks, Andres [0] root@hm90:/chromium-133.0.6943.35# strip out/Release/headless_shell root@hm90:/chromium-133.0.6943.35# ls -lh out/Release/headless_shell -rwxr-xr-x 1 root root 182M Feb 3 21:55 out/Release/headless_shell root@hm90:/chromium-133.0.6943.35# strip out/Release/content_shell root@hm90:/chromium-133.0.6943.35# ls -lh out/Release/content_shell -rwxr-xr-x 1 root root 170M Feb 3 21:55 out/Release/content_shell On 1/29/25 08:47, Ole Laursen wrote:
Just upgraded $ chromium --version Chromium 132.0.6834.110 and it looks like the old headless mode is now gone chromium --headless=old Old Headless mode has been removed from the Chrome binary. Please use the new Headless mode (https://developer.chrome.com/docs/chromium/new-headless) or the chrome-headless-shell which is a standalone implementation of the old Headless mode (https://developer.chrome.com/blog/chrome-headless-shell). Just to recap: The "new" headless thing is different from the old. It's intended to be much closer to normal Chrome, and to be used for testing where you want that similarity (web apps and extensions) where as the "old" headless is supposed to be used for engine-like tasks, screenshots, PDF-generation, printing, etc. The new headless is available as --headless whereas the old headless is available in a separate binary. Would you consider shipping the new binary? It's a loss of functionality on upgrade otherwise. Ole
OpenPGP_signature.asc
Description: OpenPGP digital signature
