On Aug 12, 8:49 pm, sdm <[email protected]> wrote:
> First, JSON was the problem. We have a call in our header to include
> json.js and used xx.parseJSON() in our code. The problem with that is
> JSON is native to IE8 and maybe partially native to IE7. This caused
> it to break in IE but work fine in Firefox. To fix it, we adjusted
> the JSON a little and changed the code to call JSON.parse(xx). This
> did the trick. Perhaps in the IE native JSON environment parseJSON()
> exist but not JSON.parse so removing the double calls so that our app
> uses the original JSON and not IE version of JSON. Have fun.
I didn't understand your explanation about JSON.
IE8 and FF3.5 have a global object JSON and its methods
JSON.parse()
JSON.stringify()
Other browsers support the same names by including Douglas Crockfords
json2.js script on page.
http://www.json.org/js.html
IE8 and FF3.5 run Crockfords code natively, so they should be faster.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Maps API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Maps-API?hl=en
-~----------~----~----~----~------~----~------~--~---
