I've not experimented with that particular tab code. I notice from the
documentation that by default (the way you are currently using it) it
only processes divs that exist when it initializes, as most such code
modules do. However it seems like this one does have the option to run
dynamically.
Try reading the "Advanced" documentation and use the
{manualStartup:true} option, then manually start tabber by calling
tabberAutomatic() each time, after the info window has been maximised.
With luck, that might cause it to find the new divs. If not, you might
have to manually start it a little later, to ensure that the Maps API
has finished rendering the new divs.
You can see that you might have MSIE problems by maximising your
infowindow and then pasting javascript:alert(tabberAutomatic()) into
the browser address bar. That works in Firefox, but not in MSIE8.
--
Mike Williams
http://econym.org.uk/gmap
--
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.
