Why I use JSON.stringify in safari and chrome to stringify a json get different result?

Question

I just simply to use JSON.stringify({"a": "123"}) to stringify a json

In chrome, the " semicolon will not be escaped, it will echo

JSON.stringify({"a": "123"})
"{"a":"123"}"

But if I use the same code in safari, the " semicolon will be escaped, like this

JSON.stringify({"a": "123"})
"{\"a\":\"123\"}"

I want to know the reason about why the chrome and safari have the different result

That's just different representations in different consoles, they are the same string. Try .length — Bergi
– Bergi, Commented Feb 26, 2019 at 15:20
Possible duplicate of Why does javascript object show different values in console in Chrome, Firefox, Safari? — Anis D
– Anis D, Commented Feb 26, 2019 at 15:20

deceze · Accepted Answer · 2019-02-26 15:30:23Z

5

It's not about JSON.stringify, it's about how the console displays value literals.

Safari chooses to make the entire line a valid literal. I.e. you could copy-paste the entire line into Javascript source code, and it'd be valid.

$Safari displays "foo\"bar"$

Chrome opts to just add decorative "" marks around the line to signify that it's a string value, but displays only the string contents as-is, without making it into a valid literal.

The advantage of Safari's method is that you can copy-paste values as code, while Chrome's advantage is that you can read a string's contents without needing to mentally parse it according to string escaping rules.

edited Feb 26, 2019 at 15:30

answered Feb 26, 2019 at 15:22

deceze♦

525k89 gold badges807 silver badges954 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Why I use JSON.stringify in safari and chrome to stringify a json get different result?

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related