You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 30, 2020. It is now read-only.
PhantomJS 2, uses WebKit 538.1, which was released in November 2013.
Significant improvements have been done in browsers in these 2+ years. Both in terms of performance, new HTML apis (not so relevant for us) and new language support (ES6/ES2015 etc).
Because Qt Project deprecated the QtWebkit they use in favor of Blink-based QtWebEngine, a more modern version would only come with (yet unplanned) PhantomJS 3 which would rewrite this...
The challenge is to have a headless setup suitable for running in production.
Alternatives
Chromium (Blink). Communicate through WebDriver/Selenium, or run-headless-chrome
Firefox (Gecko). Communicate through WebDriver/Selenium, or SlimerJS
Servo. Communicate/setup through??
Fast but highly experiemental webengine, part of Mozilla's Rust project
Headless approaches
Get xfvb-run (virtual X11) to work on Heroku. Possible but not easy
It will require a custom build Chromium for foreseeable future, since graphics backend is compile time choice and Linux builds use X11 or Wayland probably.
PhantomJS 2, uses WebKit 538.1, which was released in November 2013.
Significant improvements have been done in browsers in these 2+ years. Both in terms of performance, new HTML apis (not so relevant for us) and new language support (ES6/ES2015 etc).
Because Qt Project deprecated the QtWebkit they use in favor of Blink-based QtWebEngine, a more modern version would only come with (yet unplanned) PhantomJS 3 which would rewrite this...
The challenge is to have a headless setup suitable for running in production.
Alternatives
Fast but highly experiemental webengine, part of Mozilla's Rust project
Headless approaches
xfvb-run
(virtual X11) to work on Heroku. Possible but not easyRelated to #6
The text was updated successfully, but these errors were encountered: