The functions mouserRightClickLocation.lon and mouseRightClickLocation.lat return null values when using the Chrome browser. See attached for error displayed by Chrome.
Does anyone know of a work-around this problem?
We are using a context menu and one of the items in the menu requires us to fetch the lat, lon of the clicked point. The function works in IE, and Firefox, but not Chrome.
Please help.
Al Vigil
Hi Al,
It looks you should attach something in this post.
Could you try to upload again?
Regards,
Don
Am trying again.
Please send instructions on how to attach an image. I do not see the attachment in the above message.
Hi Al,
Thanks for your update.
I try to reproduce that but unlucky, so I want to make sure your web edition version.
And could you create a really simple sample for help reproduce that?
Regards,
Don
Don,
Sorry it has taken so long to get back to you. Attached is sample that shows the problem. If you browse test@.aspx with Firefox and right click you will see a context menu. Clicking on the first option in the menu will display the marker at the point of the click.
If you browse with Chrome and do the same thing the marker is not displayed.
Line 790 of Marker.js is
var feature = new OpenLayers.Feature(markers, new OpenLayers.LonLat(mouseRightClickLocation.lon, mouseRightClickLocation.lat));
This call fails in Chrome becase the returned lat, lon are null.
Since Chrome is an up and coming browser we need this function.
Can you come up with an alternative for us?
Thanks,
Al Vigil
p.s. the zipped project is over two MB, so I cannot attach here. Can you tell me how to send to you? In the meantime I am going to to support@thingeo.com
Don,
Any feedback on this issue?
Please let me know,
Al Vigil
Hi AI,
Sorry that Don is in vacation in the past few days. I tried our latest version and the context menu works fine on IE and chrome, please see my screenshot below and one of our online sample; the context menu works fine and get the mouse coordinate correctly with the server side event.
websamples.thinkgeo.com/Samp...tMenu.aspx
We really want to see what exactly your code is; then we can trace the bug. If your package is too big, please send it support@thinkgeo.com and ask to forward to Don; or upload to your FTP directly and let us know the file name. I think he can serve you well.
Looking forward your sample and please feel free to let us know if you have any more questions.
Thanks,
Howard
Howard,
I have forwarded the sample I had previously sent on the 16th to support@thinkgeo.com and asked that it be forwarded to Don.
Thanks for any help you can give us,
Al Vigil
Hi Al,
Just wanted to let you know we received your sample and it was forwarded to Don.
Thanks!
Hi AI,
Sorry I just back to work and I have recieved your file. I think I will have some time work for it tomorrow.
I will let you know if I have any question about that.
Regards,
Don
Thanks Don. Welcome back!
Hi AI,
Happy new year, I still haven’t get some good progress on your question today.
But I will keep work for that and update the status.
Regards,
Don
Thank you Don, I thought you had forgotten about me. A happy new year to you too!
Al Vigil
Don, Any progress on this issue?
Thanks,
Al Vigil
Don,
Please level with me. Are you ignoring me on purpose, or because you are researching this problem and do not yet have an answer, or because of some other reason?
We went to considerable effort to create the sample code that you asked for to demonstrate the problem, as it the code was embedded deep in our project, which is over 100 MB and unsuitable for analysis. I sent you the sample code on the 16th of December and again on the 27th. I will send it again, if required, but in any case let me know if I should continue to wait for an answer or call it quits,
Thanks,
Al Vigil
AI,
I am sorry reply you so late.
In fact I go a incorrect way on your issue. I thought this problem from our map control at first, but finally I found it should be from jQuery.
In IE and FF this works well but in chrome it won’t works well, because your JS function $(MainMap.div).mouseup(function (e) haven’t been fired each time when you click right button, when I test, each 3 click it will fired once.
Here I found a topic which discuss this problem:
stackoverflow.com/questions/6978739/why-jquery-mouseup-event-is-not-working-in-google-chrome
But the solution in topic looks still haven’t solve your problem. I tried:
$(MainMap.div).bind(‘contextmenu mouseup’, function (e) {
if (e.type === ‘contextmenu’) {
e.preventDefault();
} else {…}
And tried addEventListener function, it looks this problem still there.
I am trying to find other solution so haven’t update your post. Sorry for that again.
In fact I am not good at jQuery, I think you also can have some search and try for this problem.
Any update please let me know, I am testing the JS library conflict.
Regards,
Don
Don,
Thank you for taking a look at this. We will take it from here. I will let you know if we find a solution.
Al Vigil
AI,
For a workaround, maybe you can try to find another object for bind the mouseUp event for try.
I am not sure whether that will works, because when I comment the bind event for contetmenu, the chrome still work incorrect.
Regards,
Don
