Closed GoogleCodeExporter closed 9 years ago
Thanks for the report and the workaround. It looks like this broke as a result
of revision a9375373b0ee. Rolling back that revision isn't the answer, though,
because the old code was broken in other ways in the latest V3 Maps API.
I'm going to see if there is a cleaner fix - I have a feeling the mouse offset
code can be simplified from what I had been doing - but in the meantime if the
cursor style check is taking care of it, that's great.
Original comment by m...@mg.to
on 11 Feb 2013 at 6:27
I would suggest using the mousemove and click events with google maps api.
From what i've seen chrome and firefox render the div in different way.
Firefox creates a div with a negative offset while chrome renders it using a
moz transform.
Original comment by hedi.har...@gmail.com
on 11 Feb 2013 at 7:37
Fixed in rev 396650518f06.
Thanks for the report and the excellent investigation. Using the Maps API's
events is a good idea, except that this code gets used in other contexts too,
for example to overlay polygons onto a static map. So I stuck with the DOM
events but parse the -webkit-transform style when it's used.
Tested in IE7/8/9 and recent Chrome, Safari, and Firefox.
Original comment by m...@mg.to
on 12 Feb 2013 at 11:43
Great !!
Thx for this great lib !
Original comment by hedi.har...@gmail.com
on 12 Feb 2013 at 1:32
Original issue reported on code.google.com by
hedi.har...@gmail.com
on 10 Feb 2013 at 5:54