Hi,

I have started migrating a Google Maps API v2 application to v3. I
used the tabbed infowindows in v2 and so choose to use the
infobubble.js utility library to get the same functionality in v3. I
have struggled with the amount of whitespace that appears beneath my
content in the infobubbles. It seems that the code that automatically
calculates the height of the infobubble is sensitive to various style
settings in the page.

Here are a couple of example pages:

http://www.holleydesigns.com/pudo/startermap_apiv3_example1.html
http://www.holleydesigns.com/pudo/startermap_apiv3_example2.html

In example1 the middle infobubble contains a very large amount of
whitespace in it. The left infobubble has almost none. The contents
are the same except for spaces between the letters. It is those spaces
that trigger the whitespace to appear in the infobubble. The right
marker has an infowindow purely for comparison. The infowindow seems
to have a minimum height of three lines, but otherwise does not appear
to be sensitive to the style settings.

I have spent a good amount of time experimenting with what impacts the
height calculation of the middle infobubble. For instance if I remove
the #mycontainer style then it sizes correctly also the following
changes to the 'mycontainer' style will fix the height calculation:
e.g. 1) Remove the 'float:left' or 2) change to 'height:0%' or 3)
change to 'width:95%' (or less) or 4) change to 'height:800px; width:
800px'.

In example2 the middle infobubble is sized correctly. The only
difference between example1 and example2 is the addition of the text
'Hi' in the <body> after the <div>'s.

Obviously in this tiny test page any of those changes produces a
simple fix, however in the context of my full application I'm not sure
it'll be so easy and without consequences.

So the point of my post is to ask whether your opinion is that the
infobubble code could, and perhaps should, be improved to make it pick
the right height value, or perhaps to point out why I have
misunderstood the situation and brought this problem upon myself.

Thanks very much for your attention,
Cheers,
Mark

-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps JavaScript API v3" 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-js-api-v3?hl=en.

Reply via email to