79, if I add -enable-logging then -dump-dom produces output: > "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -enable-logging -headless -disable-gpu -dump-dom If you're looking for an easy way to use Headless Chrome, I highly recommend it. I guess the next step is being able to step through the dumped DOM like PhantomJS with DOM selectors and whatnot, but I suppose that's a separate question.įor what it's worth, I recently came across a Node API for Headless Chrome called Puppeteer ( ), which is really easy to use and delivers all the power of Headless Chrome. "C:\Program Files (x86)\Google\Chrome\Application\chrome" -headless -disable-gpu -print-to-pdf=D:\output.pdf
79, but you'll probably have to specify a different path for the output file in order to have the necessary permissions to save it.Īs such, the following two commands worked for me: "C:\Program Files (x86)\Google\Chrome\Application\chrome" -headless -disable-gpu -enable-logging -dump-dom Also, the -print-to-pdf command works as well in Chrome.
What am I doing wrong?Īs noted by Mark Rajcok, if you add -enable-logging to the -dump-dom command, it works. When I run the commands, something seems to process for a second, but I don't actually see anything.
I just upgraded Chrome on Windows 10 to version 60, but when I run either of the following commands from the command line, nothing seems to happen: chrome -headless -disable-gpu -dump-dom Ĭhrome -headless -disable-gpu -print-to-pdf Īnd I'm running all of these commands from the following path (the default installation path for Chrome on Windows): C:\Program Files (x86)\Google\Chrome\Application\ I've been looking at the following article about Headless Chrome: