WebKit version in PhantomJS 1.9.1

[Dmitry M]

Hello everyone,

I'm trying to add to some integration testing for my project. I'm running into a problem though where my page isn't rendering properly. I'm seeing no errors in the remote console. I suspect this may have something to do with the webkit version. Current Chrome that I'm using for development is version 537.36 (via navigator.userAgent) and PhantomJS 1.9.1 reports version 534.34. How do I interpret this version numbers? How old is current PhantomJS webkit vs latest chrome?

Thanks,

Dmitry

[James Greene]

It's old... approximately from the same time as Safari 5.1.

Sincerely,
    James Greene

--
You received this message because you are subscribed to the Google Groups "phantomjs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phantomjs+...@googlegroups.com.
Visit this group at http://groups.google.com/group/phantomjs.
For more options, visit https://groups.google.com/groups/opt_out.

[Vitaliy Slobodin]

or as Google Chrome 13.

Regards,
Vitaliy.

James Greene wrote:

It's old... approximately from the same time as Safari 5.1.

Sincerely,
    James Greene



On Wed, Oct 30, 2013 at 3:12 PM, Dmitry M <dmi...@gmail.com
<mailto:dmi...@gmail.com>> wrote:

    Hello everyone,

    I'm trying to add to some integration testing for my project. I'm
    running into a problem though where my page isn't rendering
    properly. I'm seeing no errors in the remote console. I suspect
    this may have something to do with the webkit version. Current
    Chrome that I'm using for development is version 537.36 (via

    navigator.userAgent) and Phantom JS 1.9.1 reports version 534.34.

    How do I interpret this version numbers? How old is current
    PhantomJS webkit vs latest chrome?


    Thanks,

    Dmitry

    --
    You received this message because you are subscribed to the Google
    Groups "phantomjs" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to phantomjs+...@googlegroups.com

    <mailto:phantomjs%2Bunsu...@googlegroups.com>.

    Visit this group at http://groups.google.com/group/phantomjs.
    For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google
Groups "phantomjs" group.

To unsubscribe from thi s group and stop receiving emails from it, send

[Dmitry M]

Thanks for the info.

Is there any (sane/easy) way to update this with a custom build? For instance it looks like current stable build of PhantomJS is using Qt 4.8. Is Qt 5.1 a drop in replacement by any chance?

Thanks again gentlemen.

Dmitry

[Ariya Hidayat]

Please try to look around. Your first question is somehow mentioned in
the FAQ and your next question has been discussion in this
mailing-list for a while.

Let me know if something is still not clear.

--
Ariya Hidayat, http://ariya.ofilabs.com
http://twitter.com/ariyahidayat
http://google.com/+AriyaHidayat

[Andrew Hamilton]

This is another "wait for/help with 2.0" answer. 

An update to the FAQ to include the changes expected with version 2 might be handy to link people to. A list of the issues that should be solved in GitHub would be ideal, I'll see if I can write something up later if anyone agrees it's a good idea. I'm not sure about the website contribution policy, but if someone can point me in the right direction, I'd even take care of that. 

[James Greene]

The big caveat is that we can only guess which issues will be resolved by the upgraded WebKit in Phantom 2.0... until we actually integrate the updated WebKit in Phantom 2.0 dev.  ;)

Chicken or the egg?  I don't think preemptively marking too many bugs is worthwhile, as we have a suspicion that the upgraded WebKit (and Qt) will quite literally resolve around 50% of the open bugs in Phantom.

Sincerely,
    James Greene

[Andrew Hamilton]

Yeah, I hadn't really looked at the issues page before, just individual issues. Looks like it would be easier at this point to just dump all the issues after the new QT/Webkit is in place and start over. Haha. I'm just seeing so many "can this get fixed?" questions where the answer is, "2.0 will probably fix it", and with the extended wait on 2.0, they are becoming more prevalent. I really wish I had the first clue on how to contribute, I'm just a PHP dev and I barely have any free coding time as it stands. If there is something non-code oriented that needs work, I can probably devote some time. 

Sincerely,
    James Greene

>>     <mailto:phantomjs%2Bunsubscribe...@googlegroups.com>.

[Dmitry M]

Hello Ariya,

I first want to say how much I appreciate the amount of effort that has been put into this project. Thank you.

I reviewed the FAQ but it didn't tell me what I needed to know - approximately how old the webkit is. Now that I know it's roughly 2 years old, I can understand why some of my code is failing. The list of supported features wasn't really helpeful.

In any case I haven't been able to find anything about phantomjs 2.0, or manually dropping in Qt 5.1 (with a newer webkit). Is that adviseable?

[James Greene]

No, you cannot just drop in Qt 5. Too many incompatibilities. If it were that easy, we would've done it long ago.

Sincerely,
    James Greene
    Sent from my [smart?]phone

[Ariya Hidayat]

Like James said, Qt 5 is a different beast all together. Sorry to
repeat myself but please refer to the past discussions, e.g.
https://groups.google.com/d/msg/phantomjs/EiXb4iRU7WA/6nOOksNAv_kJ.

As for the first concern, it is always intended (by design) not to
encourage folks to look for things like "WebKit version". Whenever
there is a problem, *always* troubleshoot and analyze the problem
step-by-step, possibly by reducing the cases to something much simpler
to digest. In my own experience, searching for a quick
solution/dismissal has never been effective in solving or even giving
any hints at all to the problem in hand.

Best regards,