Zoom in with scroll wheel seems to zoom beyond max zoom level and "skip/jump" the map's position [35819001]

Fixed

Bug

Status Update

No update yet.

Description

th...@gmail.com

created issue #1

Oct 15, 2009 11:01AM

Hi,

I have noticed a problem with Google Maps API v3 when it comes to zooming
in with the mouse wheel. The bug is reproduced as following:

1: Goto a Google v3 map :-) Ex.

http://code.google.com/apis/maps/documentation/v3/, scroll to the first map.
2: Zoom in as far as you can with the zoom bar. Have a road or something in
the viewport.
3: Try to zoom in even more with the mouse wheel. The map will try to zoom
in one more step, but the figure out that it can't so it seems to be
zoooming out again, but when it does this it will skip and you will not be
at the same position you where before you tried to zoom in with the wheel.

I am on Linux, using Firefox 3.5.3 and I have also the same error in Opera
10.00, build 4585.

Comments

jf...@gmail.com <jf...@gmail.com> #2Oct 26, 2009 11:16AM

Can you track these events by assigning event listeners on the map container? For
example:

google.maps.event.addDomListener('map_canvas', 'mousemove', function(e) {
// code here
});

Granted, it'll take a bit more code on your end to determine whether the mouse is
within map container boundaries, but this seems like a feature you can add yourself.

jf...@gmail.com <jf...@gmail.com> #3Oct 27, 2009 10:44AM

I have tried but my event handlers conflict with yours. The pixel arithmetic is
messy. It requires an additional OverlayView for the "fromPixelToLatLon" conversion.
You already have the same information for "click" & "dblclick" event handlers.

The browsers measure pixel offsets differently. Internet Explorer measures pixel
offsets relative to the parent DIV. Firefox measures pixel offsets relative to the
DIV containing the corresponding tile. An extra DIV is required in order to simplify
the Firefox arithmetic. Unfortunately, it covers your click layer which causes it to
fail.

d....@gtempaccount.com <d....@gtempaccount.com> #4Nov 2, 2009 04:55AM

OK, we'll consider it.

Thanks!

da...@google.com <da...@google.com> Dec 11, 2009 01:31AM

Marked as fixed, reassigned to da...@google.com.

th...@gmail.com <th...@gmail.com> #5Dec 11, 2009 07:07AM

The pixel arithmetic is not trivial. Browser differences must be accommodated.

Look at:

http://www.polyarc.us/polycluster/event.html

It is a lot of work just to track mouse coordinates. It is incompatable with your
event listeners.

Issue 35819001