Livemap menus do not open in Chrome (49.0.2623.87 m (64-bit))

Question

Hi,

if I run Live map in Chrome (49.0.2623.87 m (64-bit)) the menus for Filters and settings do not open when I click on the icons. I tried to disable all add-ins without success.

In IE11 it's working but I prefer Chrome. Any idea what the cause could be?

Thanks,

Markus

Comments

I have the same issue: On my Windows 10 PC I have installed 4 different browsers. Only in Internet Explorer I can "open" the live filter, the settings, the info and the log menu. In the other 3 (latest versions of the browsers) nothing happens when I click on the bar at the left side (only the URL changes)

I do not want to delete all cookies and all cache. If you have an option to delete only the Project GC cookies and caches, then I will give it a try :-)

Answer 1

Versie 49.0.2623.110 m (64-bit) is running fine. Maybe you missed an update !!

Answer 2

It's not likely to be an issue with the Chrome version. Try opening the developer console with F12 and then clicking the Console tab. Then reload the page.

If I remember correct, errors are in the color red. These could be interesting to determine the issue.

Comments

Thanks for looking at this!
I updated now to Version 49.0.2623.110 m (64-bit), still same effect. I doubt that the console output is helpfull:
When reloading it says:
Google Maps API warning: NoApiKeys https://developers.google.com/maps/documentation/javascript/error-messages#no-api-keys
util.js:220 Google Maps API warning: SensorNotRequired https://developers.google.com/maps/documentation/javascript/error-messages#sensor-not-required

When clicking the filter or settings icon: no messages appear. However I see a difference in the URL, e.g. when clicking the filter button the URL changes from e.g. http://project-gc.com/Tools/LiveMap#c=47.mmm,7.nnn;z=18
to: http://project-gc.com/Tools/LiveMap#filter  (no more coordinates...)  in IE, where it works, the URL does not change but instead the menu window pops up.

Thanks,
Markus aka PacoBlu

---

I had a slightly similar fault in firefox not long ago. Try deleting your cache and cookies. Worked for me (Thanks target!) Quick test - does it works in an incognito session?

---

I am having the exact same issue and I am on v50 of Chrome

---

Deleting cache and cookies helped for me as well.

Thanks for the help,
Markus aka PacoBlu