Fixed
Status Update
Comments
ch...@wetzelrice.com <ch...@wetzelrice.com> #2
[Comment deleted]
cs...@google.com <cs...@google.com>
zw...@google.com <zw...@google.com>
en...@google.com <en...@google.com>
ch...@wetzelrice.com <ch...@wetzelrice.com> #3
Just discovered that when you drag the marker off the map and it vanishes you can drag
the map in the direction that the marker vanished and the marker will appear somewhere
else on the map (presumably to a place you dragged it to where it became stuck)
the map in the direction that the marker vanished and the marker will appear somewhere
else on the map (presumably to a place you dragged it to where it became stuck)
en...@google.com <en...@google.com> #4
This is the intended behaviour. If you want the map to follow/pan to a marker when you
drag it, you can add events to handle that.
drag it, you can add events to handle that.
en...@google.com <en...@google.com> #5
Sorry, I misread you bug.
Description
Attached is a working example of the issue. There are two event handlers attached at the body level and there is a button in the middle of the map. One of the event handlers has filtering and one without filtering. On desktop's both event handlers fire when the button is clicked but on tablets the one with a selector key does not fire.
I think i have tracked it down to line 4467 of jQuery.2.1.4
I believe the issue is because google maps generates a click event handler from a touch event and when it does it sets the button clicked to 1 and not 0. A 1 indicates a middle button click and not a left button click. This causes jQuery to think the event should not be bubbled(or something like it) and therefore ignores the event for the handler.
The line that generates the click handler is in common.js of google maps.
c.initMouseEvent(b, !0, !0, window, 1, d.pageX, d.pageY, d.clientX, d.clientY, !1, !1, !1, !1, 1, null);