I found a workaround: Delete this line in contextmenucontrol.js, it's
line 170
return mapdiv;
And insert these two lines instead
var dummy = document.createElement("b");
return dummy;
For some unknown reasons TabbedMaxContent doesn't like it when the div
of the map container is returned at the end of the initialize
function.
On Sep 30, 10:44 am, "Pil (Trustworthy from Experience)"
<[email protected]> wrote:
> Yes, I have to admit:
>
> ContextMenuControl and TabbedMaxContent are not compatible, i.e.
> maximizing the infowindow causes the whole map to disappear when both
> controls are used together.
> There is no error reported.
>
> I was not able to find the reason yet. Maybe the author of
> TabbedMaxContent should also have a look.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
