This also occurs with OpenLayers v2 out of the box. It's a Chrome specific thing that appears mostly common with mouse-wheel events and it's tied to them improving touch functionalities. There doesn't seem to be a clean way of working around the issue at first glance.
It doesn't halt script exection, but it is kinda janky to have errors show up in the console. -- Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html _______________________________________________ mapguide-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapguide-users
