JSON.stringify behaving different depending on two different pages context

Question

I am using CasperJS in order to crawl sites. I have found an interesting thing and I am not really sure why is it happening.

So, with CasperJS (and PhantomJS) you can get into the Page context, using their Evaluate PhantomJS Evaluate CasperJS method.

I have created an object in the page context's, and in order to return it to the CasperJS I convert it to a string. Here is what I do:

casper.then(function() {
    var test = this.evaluate(function() {
        var test_obj = { test_obj: ['test'] }
        console.log("TEST OBJECT VALUE:");
        var JSON_obj = JSON.stringify(test_obj);
        console.log(JSON_obj);
        return JSON_obj;
    });
});

So, in two different pages, the result is different:

When in this page context, the JSON_obj value is:

{"test_obj":"[\"test\"]"}

When in this other page context, the JSON_obj value is:

{"test_obj":["test"]}

This is bad because I catch the results in Ruby, and when doing JSON.parse, for the first case it treats the array as a string... Any idea why JSON.stringify would behave "different" when in different page contexts? Interesting to me!

Isn't that native to JS though? Might be some library is overwritting? Agh! — Nobita, Oct 31 '13 at 19:54
Have you solved this issue with overwritten `stringify` implementation? — Artjom B., Jun 09 '14 at 16:37

score 0 · Answer 1 · answered Mar 30 '20 at 16:14

0

I think it might be related to this problem - JSON.stringify() array bizarreness with Prototype.js. When a site has Prototype.js framework installed then JSON.stringify may result in different string than you'd typically expect.

answered Mar 30 '20 at 16:14

Bajena

181
2
9

JSON.stringify behaving different depending on two different pages context

1 Answers1