Closed
Bug 1180744
Opened 9 years ago
Closed 9 years ago
Erroneous coordinates for mousemove event in Google Maps unfer Firefox v39
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1175863
People
(Reporter: tangent.software, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.0; rv:39.0) Gecko/20100101 Firefox/39.0 Build ID: 20150630154324 Steps to reproduce: When using javascript code as follows (Google Maps v3): google.maps.event.addListener(map, 'mousemove', function(e){ e.latLng.lat(); //wrong! e.latLng.lng(); //wrong! }); Actual results: The coordinates returned are always to the south and slightly to the east of where the cursor actually is. Expected results: The correct coordinates should be contained in the event function parameter. Worked fine under Firefox v38.
Reporter | ||
Comment 1•9 years ago
|
||
This has also been reported by someone else in stackoverflow here: http://stackoverflow.com/questions/30651839/google-map-mouseevent-in-firefox-shows-incorrect-coordinates
Comment 2•9 years ago
|
||
This needs a very rapid fix. I have had folk reporting my web site is broken only to find the fault is with Firefox 39.0 . How on earth can such a blatant fault be created and not detected before release ?
Comment 3•9 years ago
|
||
Hello, I confirm the bug and I join Bill Chadwick on the need of a very rapid fix.
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
How do I downgrade to Firefox 38? I need to use Google maps NOW, and the bug is not even assigned to anyone. Ones again: Never change a working system!
Comment 6•9 years ago
|
||
Hi Ed, as adviced at https://bugzilla.mozilla.org/show_bug.cgi?id=1175863, you need to change Google script url. Regards.
Huh! I am not using google maps directly (because of handicapped UI of new maps), but via http://www.gokml.net/maps#ll=47.624197,9.402618&z=7&t=r instead. And there are many sites that are using google API, e.g. booking.com, etc... How should one fix it then? In general, the problem is not on user side, so not the user should fix it. Oh boy.
You need to log in
before you can comment on or make changes to this bug.
Description
•