Ah I see now!
What I think is happening, is 'fitBounds' tries to find a zoom level
that allows the whole of the 'bounds' to be visible. Because the map
has a logo and nav buttons etc, the whole map area would not permit
the required area to be totally visible.
If for example you where using fitBounds to layout a groundoverlay, or
even a bunch of markers, you probably dont some of them hidden behind
the chrome of the map.
Course dont know what you actully trying to do*, but could you perhaps
send the zoom level though?
Or if you know its always going to be used in this way you could
reasonably safely just zoom in a step?
Or could maybe try using disableDefaultUI and only enable controls
after the fitBounds - but probably the logo will still get in the
way...
* another reason a link to your actual map rather than just a demo is
sometimes useful too.
2009/9/12 Dones <
manuel...@gmail.com>: