This is a known bug with Google Maps API v3.  I suspect it is not
limited to Google (i.e. Firefox has some work on their part to do) but
that is unconfirmed.  I created a Google Wave to help other maps api
developer collaborate on possible alternatives to bypass this issue:

https://wave.google.com/wave/waveref/googlewave.com/w+IRzfxGprA

-- 
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 [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-js-api-v3?hl=en.

Reply via email to