As discussed in the issue tracker I am implementing this. Throttling is absolutely vital for browsers with poor garbage collectors, but is not used for modern browsers.
On 6 Feb 2010 01:15, "bratliff" <[email protected]> wrote: Version 3.28 broke my mousemove event handler because the map controls were moved to a different layer in the DOM hierarchy. I do not know why you guys refuse to add a map canvas "mousemove" event handler to the API. You are aware of the various browser quirks. You have a comprehensive test environment with different operating systems & different browsers. You are in a position to make changes if you reorganize the DOM heirarchy. You already have the Lat/ Lon coordinates calculated for your "click" event handler. It is exactly the same information triggered on a different condition. If you do implement it, please do not throttle it. The application ought to be able to decide which events to ignore, not the API. Without a "mousemove" event listener, developers cannot provide feedback to their users. Light weight markers require it. Anything similar to GLayers also requires it. I can fix my "mousemove" event handler but it will break again if you make changes to the DOM heirarchy. -- 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]<google-maps-js-api-v3%[email protected]> . For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en. -- 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.
