They're using the latest Chrome version, so that shouldn't be the
problem. I'm pretty convinced by now that their firewall/proxy does
some content filtering which messes up the Maps API when loaded.
Unfortunately, their IT crew has researched the problem, noticed the
issue and then decided to close
It might be good to check whether the same error comes up in IE's developer
console since IE seems to freak out the most over actual javascript issues.
I only suggest this because maybe there is a js issue and IE should catch
it and that might then lead to ask what version of Chrome they're usi
