headless-browser

I have seen posts that you can change the build on Heroku, to use PhantomJS with the Cedar stack, but is it possible to run a headless browser on the unicorn stack? Yes, and someone already wrote a buildpack for including PhantomJS (the internet and open source are amazing). If you want to run headless PhantomJS on a Heroku dyno, you will need to: Switch to Heroku multi-buildpack: https://github.com/ddollar/heroku-buildpack-multi Setup Ruby buildpack for your app: https://github.com/heroku/heroku-buildpack-ruby Setup PhantomJS buildpack for your needs: https://github.com/stomita/heroku

Going through the casperjs documentation I couldn't find where I could see the console.log from client-side javascript. Is this possible? I'm not really sure to fully understand your question, but you can do something like the following: var casper = require('casper').create({ logLevel: "debug" }); casper.on('remote.message', function(message) { this.echo(message); }); casper.start('http://google.com/', function() { this.evaluate(function sendLog(log) { // you can access the log from page DOM console.log('from the browser, I can tell you there are ' + log.length + ' entries in the log'); },

I would like to generate HTML Snapshots using Watir , hosted on Heroku . Google's Full Specification for Making AJAX Applications Crawlable suggests using HTMLUnit ... see How do I create an HTML snapshot? point #3. HtmlUnit is a Java-only headless browser emulator; and unfortunately jRuby is not an option on Heroku. So HtmlUnit is ruled out (to my knowledge). If you're interested I have another question open regarding HtmlUnit as a service hosted on Google App Engine... Making AJAX Applications Crawlable? How to build a simple web service on Google App Engine to produce HTML Snapshots? ...

I have what is hopefully a simple task, but it's going to take someone that's versed in CefSharp to solve it. I have an url that I want to retrieve the HTML from. The problem is this particular url doesn't actually distribute the page on a GET. Instead, it pushes a mound of Javascript to the browser, which then executes and produces the actual rendered page. This means that the usual approaches involving HttpWebRequest and HttpWebResponse aren't going to work. I've looked at a number of different "headless" options, and the one that I think best meets my needs for a number of reasons is

New User here. After hours of building my smoke and regression tests, I found out after reading many cases online that phantomjs is known to be a trouble to run with protractor. Jenkins has been running phantomjs for all the tasks it has been given so far. They need these tests to run as part of ci which does not have a windowing system installed. So I would appreciate it if there is a recommendation for completely headless browser or a headless chrome(that would be most beneficial) and a step by step to set it up. I already have a conf.js and a e2e.conf.js file. My code works perfectly fine

I've been looking at the following article about Headless Chrome: https://developers.google.com/web/updates/2017/04/headless-chrome 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 https://www.google.com/ chrome --headless --disable-gpu --print-to-pdf https://www.google.com/ And 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\ When I run the

Tried setting the browser size on chrome --headless by using Selenium webdriver commands. I get this webdriver error: - Failed: unknown error: cannot get automation extension from unknown error: page could not be found: chrome-extension://aapnijgdinlhnhlmodcfapnahmbfebeb/_generated_background_page.html (Session info: headless chrome=58.0.3029.81) (Driver info: chromedriver=2.29.461571 (8a88bbe0775e2a23afda0ceaf2ef7ee74e822cc5),platform=Linux 4.4.0-72-generic x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 10.07 seconds Build info: version: