Embed Notice

@p@fsebugoutzone.org @phnt@fluffytail.org @tyil@fedi.tyil.nl @waifu@mai.waifuism.life

Headless Chrome doesn't output to a screen at all, the "headful" chrome they use outputs to a virtual framebuffer (similar to headless Firefox with your description). Because Headless chrome didn't output to anything it was possible to detect when it was running. For example, a certain variable relating to graphics would be different, or a driver would be missing from the headless Chrome. There were programs that could "patch up" the discrepancies from the webpage through the browser instrumentation - but there would always be more 'telltale signs' than what the programs could hide. Also, they were able to archive sites that were known to block Chrome headless browsers.

https://freeman.vc/notes/headfull-browsers-beat-headless has a bit more information on the differences