I notice the same. mousedown even on markers are not firing on iPhone OS 2.0 safari

Thanks, we'll look into it. In the future it's helpful if you can point at an example
page that's failing.

I believe the marker click event works in iPhone Safari. I tried it many times on 
different finger zooms. It's easier to touch click on the marker at higher zoom, but 
the responds are a bit sluggish in all instances, especially in 3G mode. You have to 
wait a while to see the response, and it causes me to tap even more. This maybe an 
iPhone inherent issue.

~newton 

Btw in iPhone Safari, mousedown fires when you lift your finger up upon tapping, and 
mouseup event fires thereafter (always after mousedown fires.)

~newton

I also have the same experience. The click event of the marker is not triggered no
matter in iPhone Safari or iPhone simulator.

Also experiencing the click event of either button marker (zoom) or text/hyperlink
zoom is not triggering on my iPhone. My iPhone browser identifies itself as
Version/3.1.1 Mobile/5B108 Safari/525.20

My sample is here: http://www.myparks.mobi/su/g2test.cfm

--THX Keith

Doesn't work for me either. Additionally, clicking on "a href" links inside a
marker's info window (opened with openInfoWindowHtml) does nothing. You can't even
click the "close" button in the top right corner of the info window.

There is a very clear and abrupt change from version 2.122 upwards. In this version and ALL later versions touch 
events are ignored. The frustrating thing is that a function than never worked before -- panning -- suddenly 
started working on these very same versions (post 2.121).

So -- it it true that we can have panning on the iPhone or touch events -- but not both on the same map at the 
same time?

On my iPhone simulator nothing is clickable inside the map not even the map controls
that I wrote myself and those only use onclick events in a simple a tag. Everything
outside the map works fine and can even open info windows. However I have not tested
this on a real iPhone - currently lacking one :-). Anyhow, as I read for most users a
link to maps.google.* should anyway open with the iPhone's map application (not
included in the simulator), isnt't that so?

 Bug 630  was marked as duplicate of this one, so here's my example page. On this very
simple map page, none of the map controls (zoom, pan, satellite/terrain/map) are
clickable, when using the iPhone Safari. Tested on the latest iPod Touch model
(software version 2.1.1).

http://he.fi/misc/gmaps-api-bug-630.html

Mozilla/5.0 (iPod; U; CPU iPhone OS 2_1_1 like Mac OS X; en
-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5F138 Safari/525.20

Same here. Can't click the markers on iPhone safari..

Same problem as others above, onclick event not working for markers.  Example page = 
http://www.geophlog.com

is there a list of restrictions for iphone/gmap apps? things which cannot be done on
the iphone which can be done on the desktop?

(No comment was entered for this change.)

(No comment was entered for this change.)

My iPhone 3G with 2.1 firmware shows the same problem. I want to implement the touch
and gesture events for the map controls and the click events on markers, however I
can't use both events at once.

There are over 10 million iPhones, please fix this!

Robbin Habermehl

(No comment was entered for this change.)

Is there any progress with this issue? 

Is there any progress with this issue? 

if fixed when should it be released ?

This was fixed in the latest release (2.139e). Please test your mashups with it to 
see if you see any issues. Feel free to mail me an iPhone so I may test as well. :)

Pamela, if you implement  Issue 434  I'll give you my iphone :)

The touch events definitely seem fixed for selecting markers and things like that. But, it still seems to ignore the 
tap event when I click a link inside of a info window. At least from inside of Mobile Safari. 

Thanks!

Having the same problem with 2.139e - the infowindow is closed when clicked inside, the only form element 
that you can use seems to be textarea. Does this need to be made a new issue?

That's a new issue, please file as such.

added as  issue 926 .

http://code.google.com/p/gmaps-api-issues/issues/detail?id=926