Fixed
Status Update
Comments
en...@google.com <en...@google.com> #2
I can't reproduce this on Chrome 22. Would you be able to provide the exact version number please? What OS and version are you running? Are you using Chrome on a computer with touch/stylus support?
Just for some more information, open chrome://flags in a new tab. Do you have the experimental "Enable touch events" turned on?
Just for some more information, open chrome://flags in a new tab. Do you have the experimental "Enable touch events" turned on?
ke...@gmail.com <ke...@gmail.com> #3
I am able to reproduce this error in Chrome 22 in incognito mode with all extensions disabled.
PC Specs:
UX31A-AB71 13.3-Inch Ultrabook
Windows 7 home premium SP 1
Intel core i7-3517U
PC Specs:
UX31A-AB71 13.3-Inch Ultrabook
Windows 7 home premium SP 1
Intel core i7-3517U
ke...@gmail.com <ke...@gmail.com> #4
I do not have the experimental 'Enable touch events' flag enabled.
en...@google.com <en...@google.com> #5
Does your computer have touch input in any sort of way?
[Deleted User] <[Deleted User]> #6
I think you've hit on the issue.
I do not believe that this model has touch input.
However, I do believe that some models in the line do have touch screens.
I found through the javascript console that Modernizr.touch == true
I do not believe that this model has touch input.
However, I do believe that some models in the line do have touch screens.
I found through the javascript console that Modernizr.touch == true
er...@gmail.com <er...@gmail.com> #7
I do indeed have a laptop with a touch screen (ThinkPad T410s), though I have the touch input disabled right now. I wouldn't mind the touch controls, as long as I could still use the mouse to pan...
j....@gmail.com <j....@gmail.com> #9
I have the same trouble.
mi...@gmail.com <mi...@gmail.com> #10
wa...@gmail.com <wa...@gmail.com> #11
I've also got this exact same issue. What I'd like to add is that while you cannot pan with the mouse or select markers, the maps still work normally using the touch screen input.
da...@redfin.com <da...@redfin.com> #12
Reproduced on an Acer Iconia Tab.
sp...@commutestream.com <sp...@commutestream.com> #13
I have a Asus UX31E with the same issue.
Chrome 22.0.1229.79 m
Disabling touch events flag made no difference.
I wonder if it has something to do with the touchpad driver?
Chrome 22.0.1229.79 m
Disabling touch events flag made no difference.
I wonder if it has something to do with the touchpad driver?
en...@google.com <en...@google.com> #14
This should now have been fixed in the release version v3.9 (which is the default). Please let us know if you're still experiencing problems with v3.9.
er...@gmail.com <er...@gmail.com> #15
Looks like it's fixed in v3.8 of the maps API as well. Chrome 22.0.1229.79 m.
ru...@gmail.com <ru...@gmail.com> #16
Hi.
This fix works only for Chrome?
I use JavaFX 2.2 web-engine for showing google-map (UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.14 (KHTML, like Gecko) JavaFX/2.2 Safari/535.14).
This issue is reproduce even for v3.9.
I load simple html-page with script:
<script type='text/javascript' src='http://maps.google.com/maps/api/js ? v=3.9&libraries=geometry&sensor=false&language=en&key=*my-dev-key*'>
</script>
This fix works only for Chrome?
I use JavaFX 2.2 web-engine for showing google-map (UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.14 (KHTML, like Gecko) JavaFX/2.2 Safari/535.14).
This issue is reproduce even for v3.9.
I load simple html-page with script:
<script type='text/javascript' src='
</script>
en...@google.com <en...@google.com> #17
da...@googlemail.com <da...@googlemail.com> #18
Problem also exists with QtWebkit (latest version - 2.2.1)
[Deleted User] <[Deleted User]> #19
It appears that google may have done a minor update this morning and fixed the issue. Can others confirm this?
[Deleted User] <[Deleted User]> #20
Still exists in QtWebkit
en...@google.com <en...@google.com> #21
QtWebKit is not a supported browser.
st...@gmail.com <st...@gmail.com> #22
I found that this bug was fixed. (in JavaFx 2.2)
Description
The example still works fine in other browsers (Firefox 15, Internet Explorer 9).