Fixed
Status Update
No update yet.
Comments
je...@gmail.com
I second the motion: please add an option to disable continuous zoom.
In my case we have just migrated from v2 to v3 and all of our icons have begun to experience a momentary increase/decrease in size during each scroll action (didn't happen in v2 becase we didn't have continuous zoom switched on).
This is now causing confusion amongst our user base, so it would be great to be able to prevent it from happening by switching off continuous zoom.
In my case we have just migrated from v2 to v3 and all of our icons have begun to experience a momentary increase/decrease in size during each scroll action (didn't happen in v2 becase we didn't have continuous zoom switched on).
This is now causing confusion amongst our user base, so it would be great to be able to prevent it from happening by switching off continuous zoom.
sa...@gmail.com
Continuous zoom appears to be causing a regression bug within FireFox 4 when using custom overlays.
As a premier customer, this is a big deal. Having the ability to disable this feature would allow us to mitigate the effect as a solution is determined.
As a premier customer, this is a big deal. Having the ability to disable this feature would allow us to mitigate the effect as a solution is determined.
l....@gmail.com
William,
What is the regression? Is it limited to FF4 only? Could you post a demo link please?
What is the regression? Is it limited to FF4 only? Could you post a demo link please?
l....@gmail.com
Continuous zoom is crap. Try zooming with the slider from z=18 to z=0 and Firefox hangs for 30 seconds. Give us a way disable this please!! Even better disable by default cause it's crap, then let people enable it if they want it.
If it was such a great feature why doesn'tmaps.google.com use it???
If it was such a great feature why doesn't
pa...@gmail.com
I say if the zoom level changes +/- more than 1 then don't use the feature. If you're just stepping incremently between zooms, I guess it works okay. Or Animate the transition over a longer period of time, but then that'll take too long.
you really notice this problem when using the fitBounds() function...
you really notice this problem when using the fitBounds() function...
l....@gmail.com
Thanks, I tested it in IE7, FF3 and Safari 4.
Works in all now.
Works in all now.
Description
was being thrown that also appeared to be having an impact on some of the
map events.
Specifically, the mouse-out event was not firing for markers in both IE8
and FF. Yesterday, coinciding with the announcement of the bug being
fixed, I was able to confirm that this bug (which appeared alongside the
error message stated in 1425) was also corrected.
Today, I did a clean-cache reload in both FF and IE8 and found that the
mouse-out event was again NOT working. While I am not getting the previous
javascript error, I can observe that the resultant behavior (as I
previously described in 1425) has returned -- a behavior that I was able
to confirm was working fine just yesterday.