2009/6/24 jgreg311 <[email protected]> > After looking into this deeper, I'm still not sure why defining the > property "Object.prototype.hashCode" and the function > "Object.prototype.hash" is conflicting with the google maps api. > > I don't know what the "g" is that you're referring to. > > Do you happen to have any pointers or suggestions as to how to > approach this? Removing Util.js (specifically the definition of 'Map' > within it) would be quite difficult as many items on the page rely on > it. > > Thanks for your help, > > Greg >
"g" is a variable in scope at the time the code fails. I guess that it's looping through properties of a particular object and reaching something it knows nothing about. By extending *every* object, you are messing with API objects, not just the ones you really need to alter (if indeed you do really need to). One suggestion which was made 2-3 years ago was to put the map in an iframe which doesn't use the particular troublesome library. That was when prototype.js extended Object. Please keep correspondence in the Group rather than to individuals: I've copied this to the Group thread. Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
