Hi Bob,
I'm sure there are a few things Google could do:
Bob Aman boba...@google.com wrote:
[...] my issue here is that while we're waiting
for a newer version of Prototype, more sites are deploying the current
version, and every time they do, that's one more site that's now
incompatible
On Dec 2, 2009, at 8:36 AM, Richard Quadling wrote:
2009/12/2 David Kaufman da...@gigawatt.com:
Mailing Tobie and Andrew bags of cash, or giving them great-paying
no-show jobs at Google probably couldn't hurt either :-)
I wouldn't mind one of those great-paying jobs. I'll turn up! I'll
Sure there is (and Google provides it):
Prototype hosted on Google's servers
http://tinyurl.com/google-hosted-prototype
I guess the left hand doesn't always know what the right hand is doing
in an organization as large as Google :-)
You misunderstand. I'm well aware of this service,
Add this code after prototype.js =). Also this code replaces FF 3.5
Native JSON.stringify with ES compatible...
It breaks compatibility!
delete String.prototype.toJSON; //! deleting this properties required
to save FF 3.5 Native JSON.stringify
delete Array.prototype.toJSON; //!
delete
Add this code after prototype.js =)
Thus far, this is the technique we've already been advocating, though
in considerably shorter form. It's a stop-gap measure at best, and
brittle at worst. However, my issue here is that while we're waiting
for a newer version of Prototype, more sites are
Hi, Bob.
Thanks for your post.
We'll be including fixes for native JSON in Prototype 1.7, a
prerelease of which is just around the corner.
I understand your frustration with this issue. It's on our top
priority list.
Best,
Tobie
--
You received this message because you are subscribed to the
We'll be including fixes for native JSON in Prototype 1.7, a
prerelease of which is just around the corner.
Just around the corner means different things on different projects.
Are we talking weeks, months? I'm trying to determine if Google
should be spending some engineering time on
