I wonder if there's a way to extricate some of Chrome's rendering logic to do genuinely headless stuff. I know that things are rendered in separate processes and then piped to the browser window process and I have to wonder if there's a way to launch one without the other, and thus, without any requirements for a display server like X.
The issue with Gecko was less about rendering offscreen and more about rendering widgets (dropdowns, input boxes, etc.) which are normally handled by the windowing system.
"EA WebKit supports Win32, Win64, Playstation 3, and Xbox 360 platforms" according to the documentation, but perhaps the modularization and the EA Raster primitives gets you further along than some of the other forks.
If anyone has any questions about EA WebKit, let me know and I can pass them along.
EDIT: ...Or you can ask the parent poster, who actually works on them. :)
It's sad that WebKit lacks some easier integration (good COM/.NET object in Windows).
If you only run on Windows or OS X, it's windowless, but it's not headless.
Headless means something running on a command-line console, and you can't run either of those operating systems that way.
As far as I know, there's no genuine headless Webkit.
For a genuinely headless system, consider Chris Lord's "offscreen" branch of Gecko, discussed here: http://blog.mozilla.com/ted/2010/07/29/moz-headless-screensh...
I'd be interested in sponsoring someone who wanted to bring the offscreen branch up to mainline, and Chris would be willing to mentor you in such an effort.