Mouseout event doesn't trigger after set_icon is called [35818520]

Fixed

Bug

Status Update

No update yet.

Description

sa...@gmail.com

created issue #1

Jun 29, 2009 10:48PM

Last week regarding the issue: 1425, Internal-1945540, a javascript error
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.

Comments

je...@gmail.com <je...@gmail.com> #2Jun 29, 2009 10:57PM

not sure if this is a bug or the intended behaviour
this is a way to get the new bounds

zoomChangeListener = google.maps.event.addListener(map,'zoom_changed',function (event) {
zoomChangeBoundsListener = google.maps.event.addListener(map,'bounds_changed',function (event) {
console.log(map.get_bounds());
google.maps.event.removeListener(zoomChangeBoundsListener);
});
});

sa...@gmail.com <sa...@gmail.com> #3Jul 1, 2009 11:53PM

Not sure- I'll discuss with team.

l....@gmail.com <l....@gmail.com> #4Jul 3, 2009 11:35PM

Quoted from

http://code.google.com/apis/maps/documentation/v3/events.html :

Note: If you are trying to detect a change in the viewport, be sure to use the
specific bounds_changed event rather than constituent zoom_changed and center_changed
events. Because the Maps API fires these latter events independently, getBounds() may
not report useful results until after the viewport has authoritatively changed. If
you wish to getBounds() after such an event, be sure to listen to the bounds_changed
event instead.

It seems like this is the intended behaviour (at least in API V3)

l....@gmail.com <l....@gmail.com> #5Jul 4, 2009 12:13AM

I believe this issue has been fixed a while ago by adding an 'idle' event for the Map
object.

pa...@gmail.com <pa...@gmail.com> #6Jul 13, 2009 05:25AM

Marked as fixed, reassigned to pa...@gmail.com.

I don't understand

comment #4

. The issue is NOT fixed, it's still present.

This is clearly a bug, because the map is in inconsistent state when zoom_changed handler is called - the zoom is the new one, but the bounds are still the old ones!!! This should never happen!

Thanks for workaround in

comment #1

, this seems to be the only way how one can get the bounds in the zoom_changed event. But this is not a clean way, the issue should be fixed!!!

l....@gmail.com <l....@gmail.com> #7Jul 13, 2009 08:51AM

comment #3

- using bounds_changed event instead of zoom_changed in this case is nonsense. It will fire at any occasion when bounds are changed, but here we are only interested in cases when the zoom is changed!

Issue 35818520