(No comment was entered for this change.)

(No comment was entered for this change.)

It sounds uncertain that this is an issue with the API or a glitch in the way HTML is
rendering in the browser.

Can you reply back with a link to a more complete example that isolates the problem?

Thanks!

Example showing the ill behavior:
http://www.artprodesign.com/gmaps-example1

Just click on the icon subsequently to see the window's height grow.

Workaround using <br /> tag in the beginning of the infoWindow content:
http://www.artprodesign.com/gmaps-example2

Another possible workaround is avoiding using DOM node completely for content and
using the innerHTML property to retrieve the content in string form. I.e. instead of:

var contentElem =
document.getElementById("info_window_content").cloneNode(true);

using:

var contentElem =
document.getElementById("info_window_content").innerHTML;

However documentation says:
---quote---
The InfoWindow options object is an object literal containing the following fields:

    * content contains either a string of text or DOM node to display within the info
window when it is opened.
---end quote---
... so it should work equally well with string and DOM node.

Thanks for the test link.  I reproduced the issue and confirmed the issue occurs
whenever InfoWindow.open() is called.

The problem I found was related to <p> elements inside the info window's content
node.  I experimented with setting content using an HTML node and also with an HTML
string, both containing just a single <p> tag.  I reproduced the buggy behavior in
both cases.

I've experienced some odd behavior using <p> tags in other contexts, e.g. Google
Gadgets + dynamic height.  So there's definitely something quirky going on here. 
We'll take a look.


Thanks for filing the issue.

(No comment was entered for this change.)

(No comment was entered for this change.)

InfoWindow indeed stopped growing, but there is another problem. For cases when it
used to grow, it now incorrectly autodetects the height of the infoWindow (it should
be slightly taller, the bottom margin is non-existent). Again it happens only if the
content of infoWindow starts with certain tags (<p>, <h3>, etc.), all is ok if the
content starts with e.g. <br />. And imho, it's not strictly bound to <p> tag, but
rather to certain types of tags (and it only matters what is in the beginning of the
content).
Again you can check links:
http://www.artprodesign.com/gmaps-example1
http://www.artprodesign.com/gmaps-example2
2nd link has just extra <br /> tag in the beginning of infoWindow content, other than
that it's identical to 1st.

I've tested another thing. If you just change <h3> to <div> or <span>, then the
bottom margin is too large, as this link shows:
http://www.artprodesign.com/gmaps-example3

So the summary is: If the infoWindow content begins with:
<p>, <h3>, ......... then bottom margin is too small (practically non-existent)
<div>, <span> ...... then bottom margin is too large
<br />, <hr /> ..... then the margins work correctly

Interesting.

Would you mind filing this in a separate issue?