News for hackers. Stuff that matters.

A comment on PhantomJS 2.0 is getting ready for release. Parent comment

Re:PhantomJS 2.0 is getting ready for release by serve_yay on Monday January 26, 2015 @12:13PM (#8948136)
Yes, my team ran directly into the old webkit version issue as well. Does this 2.0 still use an old WebKit? Having trouble finding out...

Edit: it appears to be WebKit 538.1, from May 2014. But this is based on a readme which is pretty old, so it could be outdated info

[ Parent | on HN ]
Re:PhantomJS 2.0 is getting ready for release by pothibo on Monday January 26, 2015 @12:17PM (#8948171)
It uses a new version of Webkit(That includes DOM Mutation Events IIRC). But I believe that they always ship with their own version of webkit, which will always be behind.

For PhantomJS 2.0, I think they ship with a version of webkit that is > 6 months old.

[ Parent | on HN ]
Re:PhantomJS 2.0 is getting ready for release by warfangle on Monday January 26, 2015 @12:18PM (#8948189)
They don't ship with their own version of webkit; they use qtwebkit (or at least used to?).
[ Parent | on HN ]
Re:PhantomJS 2.0 is getting ready for release by simlevesque on Monday January 26, 2015 @12:17PM (#8948170)
I have solved this problem by using SlimerJS as an alternative.
[ Parent | on HN ]
Re:PhantomJS 2.0 is getting ready for release by serve_yay on Monday January 26, 2015 @12:27PM (#8948246)
Yeah, unfortunately we can't install that one on our build box, I believe because it needs X11. (As the page says it is not "totally headless")
[ Parent | on HN ]
Re:PhantomJS 2.0 is getting ready for release by simlevesque on Monday January 26, 2015 @02:02PM (#8948835)
You are mistaken. You can install SlimerJS on a box without X11. You must install Xvfb use it like this : xvfb-run slimerjs script.js

If you use casperjs you can modify the executable (it's python) and change "'default_exec' : 'slimerjs'" into "'default_exec' : 'xvfb-run slimerjs'"

[ Parent | on HN ]