#1188 new
Mathieu van Loon

force prototype 1.7 to use it's builtin evalJSON rather than FF's native parser

Reported by Mathieu van Loon | December 21st, 2010 @ 01:53 PM

prototype's builtin json parser will accept json in the form new Date(1292929262541). FF's native JSON parser will throw a SyntaxError on this string.

There seems to be no way to have the native parser construct Date objects automatically. Therefor we would like to force prototype to use it's own builtin evalJSON routines. There is no way to achieve that now, as far as we've been able to determine. Would it be possible to add a switch to prototype for this purpose?

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

The Prototype JavaScript library.

Shared Ticket Bins

People watching this ticket