GoogleMap MapClick event fires after MessageBox button (mobile)

0
0

If a user clicks a link in a marker’s InfoWindow, it is handled in googlemap.MouseClick event — I then show a MessageBox where they click OK or Cancel.

But when they tap that button and the MessageBox closes, there is then a GoogleMap.MapClick event that fires — it shouldn’t.
I can’t tell if the event was generated at the same time as the original Mouseclick (link in InfoWindow), or if it was generated the same time they hit one of the MessageBox buttons. It seems it is generated by clicking the Messagebox button — the tap goes “through” the button and registers on the map.
How do I prevent this secondary MapClick event from firing?
I tried to Remove handler before messagebox, and then add it again, but the event still fires.
This only happens on mobile.
Thanks.
  • Andrew Niese
    Yes I can confirm — a MessageBox displaying on top of a GoogleMap will generate a MapClick event after hitting a messagebox button!
  • You must to post comments
0
0

Another issue to add to my 9/25/18 comments.  Tapping a marker/map area does not generate a MapClick event in FireFox mobile. WiseJ 1.5.19.

 

 

 

  • You must to post comments
0
0

While this  (WJ-9117) still appears fixed, I have another issue now. I am getting it in both 1.5.16 and 1.5.19…. it is with MouseClick and not with MapClick.  A tap on the screen punches “through” a MenuItem , and then registers on the map (a marker’s InfoWindow HREF link), firing a MouseClick event.

The MenuItem click code fires first. Because that code changes objects that the MouseClick event later refers to, it throws an exception when the object is no longer available.  The MouseClick event should never fire in this scenario.

I’m emailing you a video of it now.

thanks

Andrew

 

  • You must to post comments
0
0

Hi Andrew,

Please have a look at Wisej-Extensions repository at GitHub and check whether the updated source code for GoogleMaps extension solves the issue you reported.

Showing 3 results
Your Answer

Please first to submit.