etienne-martin/Mapify

Doesn't work in Google Chrome

alysonsm opened this issue · 13 comments

Searching on the web I found your script and I must say, it is a really nice job of yours. It works perfectly on firefox but I am having some odd behaviours while on google chrome. I tryed many things (looked into your code, changed jquery 'bind' to 'on') to make this works, but with no success.

Here a jsfiddle so you can see it yourself:
http://jsfiddle.net/j1dftnkp/5/

It should change background color when the mouse pointer is on the chest area. I don't know if I missed something.

Can you help me with that?

Thanks for finding this bug. I'll look into it asap!

This is exactly what I've been looking for. I hope you can get it working in Chrome. Looks to be working in FireFox and IE (at least in IE9).

You need to set the name attribute of your map with the same value as the id.

My mistake. I've updated the doc and your jsfiddle.

http://jsfiddle.net/j1dftnkp/7/

It doesn't appear that the highlight portion is working in chrome. Even your site http://etiennemartin.ca/mapify/ isn't working correctly in Chrome.

You are using Chrome (43.0.2357.130) on Windows (8.1) right?

Yes that is correct.

I'm not able to reproduce the problem with the same config as yours.

Do you have Chrome extensions running in the background?

Have you tried with another computer with the same OS/browser?

I'm closing the issue until we find a way to reproduce the bug (on my side).

Thanks.

This appears to be more of a Windows 8.1 issue than Chrome. I can get this to work in the latest version of Chrome on different OS and devices, but not in Chrome on Windows 8.1. Due to this not working, I will have to look for alternative options.

Can you tell me if it's now working using this modified version? http://etiennemartin.ca/mapify2/

It's still not working for me in chrome. It does work in other browsers.

I'm seeing an issue with Chrome on Windows 7 as well. Chrome seems to support the touch event handlers, which seems to be throwing things off. A workaround is to hardcode touchIsSupported to false on line 57.

Thanks for the finding jdomingu. It's now fixed in the latest version.