1175863 - Google Maps API V3 drawing manager bug (caused by Gecko now supporting event.offsetX/Y)

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect)

Description

[oskar]

Attachment: bug.jpg

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:39.0) Gecko/20100101 Firefox/39.0
Build ID: 20150603092413

Steps to reproduce:

I was trying to draw a polygon by Drawing Manager.
Try here: http://codepen.io/anon/pen/LVzpGG


Actual results:

If the map DIV's parent has margin, polygon was showing end of new line in bad position.




Expected results:

It should work like in older versions of Firefox or like with no margin.

Comment 1

[Alice0775 White]

[Tracking Requested - why for this release]:regression since Firefox39beta

Comment 2

[Alice0775 White]

Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=2b9f5019abf1&tochange=4100738d662d

Triggered by: Bug 69787

The following UA spoofing helps:
user_pref("general.useragent.override", "Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.65 Safari/537.36");

So this is also Google's bug. (See also Bug 1171938.)

Comment 3

[jen strickland :jenstrickland]

Tracked for 39, 40, and 41, as this is a regression, and the behavior was working in 39 Beta, and expectation would be that it would continue to.

Comment 4

[Liz Henry (:lizzard) (relman/hg->git project)]

Wontfix for 39.

Comment 6

[it-solutions]

I vote for this bug to be solved soon, as it really makes Google Maps (with mouseevents on markers) unusable in FF (except if you position your map div at the topleft corner of your browser window).

Comment 7

[Alice0775 White]

This is google's bug.
https://code.google.com/p/gmaps-api-issues/issues/detail?id=8278

Comment 13

[Kohei Yoshino [:kohei]]

Not a Core bug actually.

Comment 14

[Hallvord R. M. Steen [:hallvors]]

I consider them contacted since there's a bug report on https://code.google.com/p/gmaps-api-issues/issues/detail?id=8278

Comment 15

[Kohei Yoshino [:kohei]]

https://developer.mozilla.org/en-US/Firefox/Releases/39/Site_Compatibility#DOM

Comment 16

[Boris Zbarsky [:bzbarsky]]

> Wontfix for 39.

Do we have a commitment from Google to fix their end of this?  Why did we decide to go ahead and ship bug 69787 given the known breakage?

Comment 17

[Robert O'Callahan (:roc) (email my personal email if necessary)]

On June 7 we were told "It has been assigned to someone last week." Then I kind of forgot about it :-(.

There's at least one site (not an important site) that's broken without offsetX/Y support, which is why I implemented it. We can expect that to grow since every other browser has had them for a long time. So, we could revert the patch, but then I'm not sure how to proceed so we can eventually enable offsetX/Y.

FWIW Google's internal bug number for this is b/20820906.

Comment 18

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Since Maps API widgets don't have their own IFRAME, I guess hiding offsetX/Y from Google Maps but making them available to other code is not really an option.

Any suggestions to make Maps work that don't require disabling offsetX/Y indefinitely?

Comment 19

[Kohei Yoshino [:kohei]]

As per Bug 1181130 Firefox 38.0.1 is being planned. Could we just back out Bug 69787 from 38 so we give Google 4 weeks to fix the issue before 39 is out?

Comment 20

[Kohei Yoshino [:kohei]]

Sorry I meant 39.0.1 of course.

Comment 22

[Jessy]

It is not only a problem on Google maps but also on openlayers 3

Comment 23

[jkirk_14]

Not sure if this is because Google put in a fix already, but this seems to solve my problem with mouseover events:

In js source,
Change
http://maps.googleapis.com/maps/api/js?sensor=false
to
http://maps.googleapis.com/maps/api/js?v=3

Comment 24

[jkirk_14]

Or works adding the v=3 parameter and keeping sensor=false:
http://maps.googleapis.com/maps/api/js?v=3&sensor=false

Working example:
http://jsfiddle.net/mojs7421/

Comment 25

[Theodor Imholz]

Thanks for the input. It works much better.

Comment 26

[it-solutions]

Agreed, thank you jkirk, this helps avoiding the bug (not sure, if that is called a solution)...

Comment 27

[jkirk_14]

Agreed - I'm not affiliated and just wanted to share a fix I found while we wait for Google/Mozilla to sort it out.  There's clearly something in the V3.exp API that differs from V3 and should be easy to pinpoint.

Comment 29

[Jessy]

Openlayers 3.7 seemed to have fixed the problem as well

Comment 33

[Sylvestre Ledru [:Sylvestre]]

As it is not a Firefox bug per say and Google Map & Openlayers fixed the bug, I am going to wontfix it.