4 ms·

Most of the tools listed use PhantomJS or QT core browser as the base. The problem is that PhantomJS doesn't support many new API-s or the rendering is differen

by riston 10y ago

Most of the tools listed use PhantomJS or QT core browser as the base. The problem is that PhantomJS doesn't support many new API-s or the rendering is different. There is also headless chrome browser in development, not sure if there are any prebuilt binaries out there?

jordybg 10y ago
Going to ask same question, about headless Chrome, any recent information on that, anyone?
- gowan 10y ago
  it is issue 546953[1] in the chromium issue tracker. [1] https://bugs.chromium.org/p/chromium/issues/detail?id=546953 https://bugs.chromium.org/p/chromium/issues/detail?id=546953
- caleblloyd 10y ago
  There is a Google Group for it: https://groups.google.com/a/chromium.org/forum/#!forum/headless-dev https://groups.google.com/a/chromium.org/forum/#!forum/headl... I check every now and again. I'm super interested in headless PDF generation (using Nigtmare now)
gowan 10y ago
what new apis should phantomjs support? download support[1] is the only new api in development. it's not tagged for the 2.5 release[2]. [1] https://github.com/ariya/phantomjs/pull/14225 https://github.com/ariya/phantomjs/pull/14225 [2] https://github.com/ariya/phantomjs/issues/14458 https://github.com/ariya/phantomjs/issues/14458
- nmk 10y ago
  FileReader support is not fully implemented (addEventListener is not present). Just ran into this last week. There has been an open issue for this for three years[1]. [1] https://github.com/ariya/phantomjs/issues/11733 https://github.com/ariya/phantomjs/issues/11733
sebcat 10y ago
I've been using chromium-headless for certain automated tasks, and I've been getting a lot better results than from PhantomJS in terms of correctly rendered resources, resource consumption and execution speed. If your business depends on rendering engines and you're using PhantomJS, chromium-headless is probably something you want instead. I build from chromium src, and my code is more or less an extension with its own BUILD.gn with a deps on //headless. Once you've built the initial tree (took a night for me), builds will be really fast. Most of the interaction with the browser is by the chrome debugging protocol, as with "normal" chromium. Generally speaking, you want to target that, instead of the internal APIs. There are some tweaks you need to be aware of. Chromium needs a homedir, so you want to configure that. There's state stored between sessions, so if you want process invocations stateless, consider spending some time hacking or run the process in a fresh namespace/chroot/docker/jail/whatever each time. I had to write my own protocol handler and URLRequestJobs because I render pages from archives on disk and that was the easiest way to get that started at the time. I don't know if vanilla chromium supports it, but I'm pretty sure I've seen a --headless flag somewhere... If not, headless_shell is pretty easy to build following the official build instructions[1]. I'm running on RHEL/Fedora/CentOS. There's also unofficial images on docker hub if you want to go that route. [1]: https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md https://chromium.googlesource.com/chromium/src/+/lkgr/headle...
- Flenser 10y ago
  Here's the bug to follow if you want to follow progress (the anchor comment in the url is for when screenshot capturing landed) https://bugs.chromium.org/p/chromium/issues/detail?id=546953#c54 https://bugs.chromium.org/p/chromium/issues/detail?id=546953...
- boundlessdreamz 10y ago
  What about startup time? phantomjs is the only headless browser I have tested which starts up relatively fast.
  - sebcat 10y ago
    Can't test now, but around a few tens of milliseconds for about:blank
spangry 10y ago
Also selenium grid docker containers. Unfortunately their Python documentation isn't the best (though there's some excellent third-party created Python documentation available). To save you the head-scratching I went through, it's basically just: - Start a 'selenium hub' - Start up as many firefox/chrome 'node' containers and link them to the hub. - Point webdriver at the hub port and url. I will eventually get around to building some Alpine containers for this, one day. I find the official ones a bit 'heavy' given all it really invoves in installing openJDK and running a jar file / browser driver.

by riston 10y ago

jordybg 10y ago

Going to ask same question, about headless Chrome, any recent information on that, anyone?

gowan 10y ago
it is issue 546953[1] in the chromium issue tracker. [1] https://bugs.chromium.org/p/chromium/issues/detail?id=546953 https://bugs.chromium.org/p/chromium/issues/detail?id=546953
caleblloyd 10y ago
There is a Google Group for it: https://groups.google.com/a/chromium.org/forum/#!forum/headless-dev https://groups.google.com/a/chromium.org/forum/#!forum/headl... I check every now and again. I'm super interested in headless PDF generation (using Nigtmare now)

gowan 10y ago

what new apis should phantomjs support? download support[1] is the only new api in development. it's not tagged for the 2.5 release[2]. [1] https://github.com/ariya/phantomjs/pull/14225 https://github.com/ariya/phantomjs/pull/14225 [2] https://github.com/ariya/phantomjs/issues/14458 https://github.com/ariya/phantomjs/issues/14458

nmk 10y ago
FileReader support is not fully implemented (addEventListener is not present). Just ran into this last week. There has been an open issue for this for three years[1]. [1] https://github.com/ariya/phantomjs/issues/11733 https://github.com/ariya/phantomjs/issues/11733

sebcat 10y ago

I've been using chromium-headless for certain automated tasks, and I've been getting a lot better results than from PhantomJS in terms of correctly rendered resources, resource consumption and execution speed. If your business depends on rendering engines and you're using PhantomJS, chromium-headless is probably something you want instead. I build from chromium src, and my code is more or less an extension with its own BUILD.gn with a deps on //headless. Once you've built the initial tree (took a night for me), builds will be really fast. Most of the interaction with the browser is by the chrome debugging protocol, as with "normal" chromium. Generally speaking, you want to target that, instead of the internal APIs. There are some tweaks you need to be aware of. Chromium needs a homedir, so you want to configure that. There's state stored between sessions, so if you want process invocations stateless, consider spending some time hacking or run the process in a fresh namespace/chroot/docker/jail/whatever each time. I had to write my own protocol handler and URLRequestJobs because I render pages from archives on disk and that was the easiest way to get that started at the time. I don't know if vanilla chromium supports it, but I'm pretty sure I've seen a --headless flag somewhere... If not, headless_shell is pretty easy to build following the official build instructions[1]. I'm running on RHEL/Fedora/CentOS. There's also unofficial images on docker hub if you want to go that route. [1]: https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md https://chromium.googlesource.com/chromium/src/+/lkgr/headle...

Flenser 10y ago
Here's the bug to follow if you want to follow progress (the anchor comment in the url is for when screenshot capturing landed) https://bugs.chromium.org/p/chromium/issues/detail?id=546953#c54 https://bugs.chromium.org/p/chromium/issues/detail?id=546953...
boundlessdreamz 10y ago
What about startup time? phantomjs is the only headless browser I have tested which starts up relatively fast.
- sebcat 10y ago
  Can't test now, but around a few tens of milliseconds for about:blank

spangry 10y ago

Also selenium grid docker containers. Unfortunately their Python documentation isn't the best (though there's some excellent third-party created Python documentation available). To save you the head-scratching I went through, it's basically just: - Start a 'selenium hub' - Start up as many firefox/chrome 'node' containers and link them to the hub. - Point webdriver at the hub port and url. I will eventually get around to building some Alpine containers for this, one day. I find the official ones a bit 'heavy' given all it really invoves in installing openJDK and running a jar file / browser driver.