Hi everyone, in case you are still having problems with this, I have spent many hours debugging this and finally the fix is a little hack to the plugin css:
comprehensive-google-map-plugin/style.css
You need to delete the top:100000px !important; part from line 87
object.cgmp-data-placeholder{background-color:transparent !important;border:none !important;height:0 !important;left:10000000px !important;line-height:0 !important;margin:0 !important;outline:medium none !important;padding:0 !important;position:absolute !important;<strong>top:100000px !important;</strong>width:0 !important;z-index:9999786 !important}
This will make the page resize correctly. I’m not a CSS expert so probably there’s a better solution without hacking the plugin, but it works for me for now.
Also I have to say that this problem happened when using Responsive theme v1.7.2 along with Comprehensive Google Map Plugin v7.0.29. There is a conflict between these two elements, specifically between the plugin CSS line shown above and the fitVids javascript function located in theme file responsive/js/responsive-scripts.js. This function handles resizing of video inserted via <object>, <iframe> and <embed> elements when the page is resized or when using mobiles and tablets. However the function processes all object elements even google maps’, the problem here is that google maps object does not have a defined height and width (in fact the object is hidden) which causes the function to “crash” when doing operations such as:
aspectRatio = height / $this.width();
When processing a google maps object the result is:
aspectRatio = 0 / 0 = NaN
So even though removing top:100000px fixes the huge height/width problem, it would be great if the theme was modified to distinguish between video <object> and Google Maps <object> in order to treat them differently. And ideally either the theme or the plugin should be able to resize the actual <div> for the displayed Google Map.
Anyway I think this is a brilliant plugin and the responsive theme is also great and it’s really a pity that people stopped using it because of this “huge” problem which can be fixed by just changing a line. I’ll write to the plugin and theme authors to see if I can help them in anyway to get this fixed.