well, I'm going to answer my own question here, even though I don't really understand it. It appears that setting up a div element in the css file (which you can then apply the same font size to as the body element... or any other size) fixed the problem.
I was under the impression that css font sizes were the source of this problem (thus creating the need for the span class solution), and that infowindow sizes were calculated before the text was generated, but I guess I'm putting it down to another thing that works fine, but I just don't get... cheers, Lucas -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" 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.
