Yes, our maps did not work in iframes until the 167 fix. We could not add markers at all, the reason for updating to 173 was to try and fix the drag issue.
I've modified the variables as you've suggested so that the complex objects are not being passed and that actually fixed the drag in IE6. The example has been updated, and is still not working in firefox and chrome. Haven't retested on safari or opera. On Sep 8, 12:52 pm, Andrew Leach <[email protected]> wrote: > On Sep 8, 8:25 pm, DJ <[email protected]> wrote: > > > Forgot to add, everything works in IE7 and IE8, > > the issue appears in IE6, firefox, safari, chrome, opera. > > Your code attempts to pass the map object between frames as an > argument in a function: > > gmap = new window.google.maps.Map2(document.getElementById > ('visualization')); > window.parent.runOver(gmap,wrapper); > > That's going to cause problems, because a number of browsers can't > pass complex objects like that very well. > > In the issue you reference, RichardDavies79's test case creates a > reference when it needs to: > > var map = parent.map; > > which would presumably work the other way round as well if you gave > your iframe an id so you could reference it: > > var gmap = iframe.gmap; > var wrapper = iframe.wrapper; > > Failing that, have you tried setting v=2.167 where that issue was > fixed? > > 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 -~----------~----~----~----~------~----~------~--~---
