I have added this as an "big issue" on the V8 Google code home :
http://code.google.com/p/v8/issues/detail?id=573&q=JSON&colspec=ID%20Type%20Status%20Priority%20Owner%20Summary%20HW%20OS%20Area%20Stars
Please, "star" this issue to make it more noticeable by the V8
team ...
--DBJ
--
You received
As commented in your commit, I think the support approach is cleaner and
more future-proof (that is when Chrome implements JSON parsing controls
properly).
2010/1/12 John Resig
> As a note: I added identical errors earlier today but skirted around
> the need to have any sort of support property:
On 1/11/10 8:26 PM, DBJDBJ wrote:
Simple and effective ... Thanks.
My approach is 'slightly' different ( http://dbj.org/dbj/?p=470 ) but
perhaps sacrifices size and simplicity to be (maybe) faster.
Does anyone know why CHROME window.JSON.parse accepts non-standard
strings ? I am writing this in
Simple and effective ... Thanks.
My approach is 'slightly' different ( http://dbj.org/dbj/?p=470 ) but
perhaps sacrifices size and simplicity to be (maybe) faster.
Does anyone know why CHROME window.JSON.parse accepts non-standard
strings ? I am writing this in CHROME 4.0.228.1.dev and it accepts
As a note: I added identical errors earlier today but skirted around
the need to have any sort of support property:
http://github.com/jquery/jquery/commit/44e6beb10304789044de2c5a58f5bb82e8321636
--John
On Mon, Jan 11, 2010 at 7:51 PM, AlexSexton wrote:
> I went ahead and wrote a support flag
I went ahead and wrote a support flag and an implementation of a check
for nonstandard window.JSON.parse methods (including chrome) inside of
the ajax httpData method.
My change is here:
http://github.com/SlexAxton/jquery/commit/57313eb69a7c87f862440b062932e91c0e162c6c
I think consistently throw
