Fixed
Status Update
Comments
ch...@wetzelrice.com <ch...@wetzelrice.com> #2
I second the motion: please add an option to disable continuous zoom.
In my case we have just migrated from v2 to v3 and all of our icons have begun to experience a momentary increase/decrease in size during each scroll action (didn't happen in v2 becase we didn't have continuous zoom switched on).
This is now causing confusion amongst our user base, so it would be great to be able to prevent it from happening by switching off continuous zoom.
In my case we have just migrated from v2 to v3 and all of our icons have begun to experience a momentary increase/decrease in size during each scroll action (didn't happen in v2 becase we didn't have continuous zoom switched on).
This is now causing confusion amongst our user base, so it would be great to be able to prevent it from happening by switching off continuous zoom.
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
Continuous zoom appears to be causing a regression bug within FireFox 4 when using custom overlays.
As a premier customer, this is a big deal. Having the ability to disable this feature would allow us to mitigate the effect as a solution is determined.
As a premier customer, this is a big deal. Having the ability to disable this feature would allow us to mitigate the effect as a solution is determined.
en...@google.com <en...@google.com> #4
William,
What is the regression? Is it limited to FF4 only? Could you post a demo link please?
What is the regression? Is it limited to FF4 only? Could you post a demo link please?
en...@google.com <en...@google.com> #5
Continuous zoom is crap. Try zooming with the slider from z=18 to z=0 and Firefox hangs for 30 seconds. Give us a way disable this please!! Even better disable by default cause it's crap, then let people enable it if they want it.
If it was such a great feature why doesn'tmaps.google.com use it???
If it was such a great feature why doesn't
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);