You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, thanks very much for the gokml.net version! Even after the rebranding, it is still my main map service.
In the last 3-4 weeks, searches with one exact match have opened up in an all-black Street View that I have to close to see the map. Any ideas for a fix? Examples, at various scales:
Chrome 65.0.3325.162 (Official Build) (32-bit), but the same was happening with Chrome 64 as well.
In the Developer Console, I don't get any errors, but I do get two warnings:
[Deprecation] The deviceorientation event is deprecated on insecure origins, and support will be removed in the future. You should consider switching your application to a secure origin, such as HTTPS. See https://goo.gl/rStTGz for more details.
addDomListener @ js:116
Google Maps API warning: NoApiKeys https://developers.google.com/maps/documentation/javascript/error-messages#no-api-keys
CB.j @ maps.google.com/maps-api-v3/api/js/32/5a/util.js:230
Because of the "insecure origins" warning, I tried https as well. However, the Google API scripts are currently loaded via http only, so aren't loaded when using https.
Thank you!
The text was updated successfully, but these errors were encountered:
First off, thanks very much for the
gokml.net
version! Even after the rebranding, it is still my main map service.In the last 3-4 weeks, searches with one exact match have opened up in an all-black Street View that I have to close to see the map. Any ideas for a fix? Examples, at various scales:
The same also happens without the
#q=...
.Chrome 65.0.3325.162 (Official Build) (32-bit), but the same was happening with Chrome 64 as well.
In the Developer Console, I don't get any errors, but I do get two warnings:
Because of the "insecure origins" warning, I tried https as well. However, the Google API scripts are currently loaded via http only, so aren't loaded when using https.
Thank you!
The text was updated successfully, but these errors were encountered: