This is how Chrome pushes out other browsers: first you make a browser that is fast in some aspect. Then you build an app that takes advantage of that aspect.

This is how Chrome pushes out other browsers: first you make a browser that is fast in some aspect. Then you build an app that takes advantage of that aspect. In this case Chrome can handle a lot of events and Google Maps generate a lot of events. So in Chrome it is smooth. In other browsers (I use Firefox) the browser will choke on events and the map will lag. Maybe is just a matter of compiling Firefox with better defaults (more memory allocated, smaller tick rate for events, I don't know, I'm just making suppositions, I have no clue how a browser works) but it feels slower. To prevent this I throttle the events (checkbox checked): I kill the event if it arrived too fast or the change in mouse position is too small. This will make the map more responsive. Please note that I don't say that Chrome does this intentionally. But it happens. I've put more information here at the time: https://stackoverflow.com/questions/16645766/google-maps-api-v3-no-smooth-dragging/22030838#22030838 https://stackoverflow.com/questions/16645766/google-maps-api...