That commit will use the native EC5 apis if they're available. But Prototype doesn't provide them if they're not present, which it easily could do. That's basically what I was suggesting.
On Fri, Feb 26, 2010 at 5:48 AM, Walter Lee Davis <wa...@wdstudio.com>wrote: > Or maybe continue to provide a layer of spackle over the differences, by > calling the native facility from within the Prototype methods if it's > available, and providing the internal method for browsers that haven't > caught up to the spec (or are building to their own special spec). > > Walter > > > On Feb 26, 2010, at 8:15 AM, Robert Kieffer wrote: > > That said, I'd like to see Prototype be a bit more aggressive about >> funneling people toward the EC5 APIs. Now that Proto's implementation is >> "EC5 compliant" why not do what http://www.json.org/json2.js does and >> test for the presence of the JSON API and, if not found, simply create it? >> Keep Object.toJSON and String.evalJSON around for a little while, for >> backward compatibility, but in the docs direct people to migrate away from >> these as they'll eventually go away (right?) >> > > -- > You received this message because you are subscribed to the Google Groups > "Prototype: Core" group. > To post to this group, send email to prototype-core@googlegroups.com > To unsubscribe from this group, send email to > prototype-core-unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/prototype-core?hl=en > -- You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en
