Comment #6 on issue 1907 by erig...@google.com: The literal chars 0x2028 and 0x2029 should be avoided in JSON
http://code.google.com/p/v8/issues/detail?id=1907
Well, then the spec should be fixed.
Some of us tried to get this issue fixed during the ES3.1 - early ES5 days, so that JS agreed with JSON on the meanings of \u2028 and \u2029. That would have kept the formal subset relationship between JS and JSON intact. We did not achieve consensus in doing so. On this issue and the encoding issue raised here, I wish you had joined this fight before it was settled.
Once all five major browser implementations and the spec all agree on a common behavior, we must then assume web content relies on this behavior and we no longer dare "fix" it without very good evidence that we won't break the web.
-- v8-dev mailing list v8-dev@googlegroups.com http://groups.google.com/group/v8-dev
