Not sure about the intention of your question. Infowindows do constist of many many divs. Sould not matter very much when you create a further div that contains your content.
I'd suggest to have a look at the DOM structure of infowindows using Firebug. There you can also see the results when certain divs are removed. Why do you want to remove the infowindow after it's being used? The Maps API is not designed to do that. I think you should let the API do it's own job unless you detect that it does it's job extremly inefficient. Even in this case you should be aware: Manipulating the DOM subsequently and from outside is probably inefficient anyway. So it's generally no good idea to change the DOM created by the API. If you detected a bug or a reproducable memory leak, why don't you report that? On Sep 16, 9:55 am, Gianpiero Venditti <gianpiero.vendi...@gmail.com> wrote: > Hello, I have a doubt about the infowindow behaviour. > Let's say that I construct an infowindow with a div inside and i connect it > to a marker with a listener. > > Then if i want to remove the infowindow what's the best way to do it in > order to release memory occupied by the infowindow? > > And also do i have to explicitly remove the div inside the infowindow from > the DOM? > > Thanks in advance for the help. -- 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 google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
