Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"JavaScript" is too broad, needs more engines #83

Open
l1bbcsg opened this issue May 4, 2018 · 0 comments
Open

"JavaScript" is too broad, needs more engines #83

l1bbcsg opened this issue May 4, 2018 · 0 comments

Comments

@l1bbcsg
Copy link

l1bbcsg commented May 4, 2018

Even being the birthplace of JSON, JavaScript still has several implementations and engines which behave differently.

The parser labeled "JavaScript" uses NodeJS, whichever version is currently installed indiscriminately. I tested all of the currently used node versions (4 to 10) and they all behave similarly, but this is worth documenting at least.

I think it'd be a good idea to provide tests for major browser engines too. With WebKit/V8, it's definitely possible. I did tests with PhantomJS, but it's a poor choice for multiple reasons. Couldn't figure how to run Headless Chrome properly, but it should be doable. For other engines/browsers it's trickier and may even be impossible.

PhantomJS (2.1.1 with WebKit 538.1) results compared with NodeJS 9.6.1 are:

image

The problem with phantom is that it's abandoned, incredibly slow (couldn't even fit into 5 seconds timeout in tests) and iirc uses a JS engine different from V8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant