Too much recursion JS error

[GoogleCodeExporter]

What steps will reproduce the problem?
We are suffering this in gmaps4jsf when creating a TabbedMaxContent window 
without tabs, some HTML as summary and maximizing it. It happens in IE8 and 
FF3 at least.

What is the expected output? What do you see instead?
In the end it works but in FF it takes some time and the firebug console 
prints an error. In IE an alert is shown.

What version of the product are you using? On what operating system?
Both stable and dev versions

Please provide any additional information below.
If you need it I can provide a WAR that shows the problem.

Original issue reported on code.google.com by jose.noh...@gmail.com on 3 Sep 2009 at 9:58

[GoogleCodeExporter]

Can you provide a linked sample? TabbedMaxContent is a js client, so a deployed 
war
files works better than war file itself. Also, please try an older version of 
the
core API like 2.151?

Original comment by nian...@gmail.com on 4 Sep 2009 at 9:43

[GoogleCodeExporter]

Original comment by nian...@gmail.com on 4 Sep 2009 at 9:50

• Added labels: Class-TabbedMaxContent

[GoogleCodeExporter]

This has something to do with this function:

ExtInfoWindow.prototype.repositionMap_

There is something wrong with height which will cause infinite recursion with 
repositioning the map.

Original comment by teckc...@gmail.com on 7 Oct 2009 at 6:49

[GoogleCodeExporter]

strange.  I tried this with an ExtInfoWindow example. Difficult to reproduce
reliably, but sometimes happens when i am at zoom level 0, possibly when part 
of the
window is hidden.

Basically redraw calls repositionMap_ which calls setCenter on the google maps 
API. 
setCenter calls some functions that then call redraw again.   However, the 
google API
has not repositioned the map yet, so the same thing occurs again.

when I think about it, I'm not sure if redrawing should automatically mean
repositioning. But, quick fix is, I can put some code in there to keep it from 
recursing.

Original comment by douglass...@earthlink.net on 7 Feb 2010 at 12:21

• Added labels: Class-ExtInfoWindow, Type-Defect

[GoogleCodeExporter]

It happens more often when I open an extinfowindow and then go to zoom level 
zero. My
guess is, repositionMap_ is calling setcenter when the amount to pan is above
maxPanning, which doesn't pan enough to show the entire window.  However, it 
seems if
the infowindow is partially obscured, google maps api sometimes calls redraw, 
which
repositions again.

fixed.

Original comment by douglass...@earthlink.net on 7 Feb 2010 at 4:56

• Changed state: FixedInDev

[GoogleCodeExporter]

For documentation purposes: I think this and

#169 - http://code.google.com/p/gmaps-utility-library-dev/issues/detail?id=169

are related, since the only time I saw this error was at zoom level 0 and 1, 
when the
window would not center properly and it was partially of the screen.  However,
perhaps if the window is sufficiently large enough so that it can not fit on the
screen at once, the same could happen at any zoom level.

Original comment by douglass...@earthlink.net on 15 Feb 2010 at 2:07

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This error message occurs when I try to display more than two maps on the same 
page.

Original comment by felipewi...@gmail.com on 3 Nov 2010 at 5:39

[GoogleCodeExporter]

anyone ever tried display more than two maps with m:map within rich:dataTable? 
something like: 

<rich:dataTable...>
....
   <rich:column>
      <m:map...>
      ...
      </m:map>
   </rich:column>
</rich:dataTable>

Original comment by felipewi...@gmail.com on 3 Nov 2010 at 5:47