API key is required
martijnjanssen opened this issue · comments
It seems that the google-maps API now requires a key for every request. Requests without an API key seem to be blocked.
<google-map latitude="52" longitude="4"></google-map>I created the element above and did not provide a key. These were the repsponses I got:
That's right. New Maps API apps need to provide a key now. That's a
requirement of the API.
On Sun, Oct 23, 2016, 3:23 AM Martijn Janssen notifications@github.com
wrote:
It seems that the google-maps API now requires a key for every request.
Requests without an API key seem to be blocked.I created the element above and did not provide a key. These were the
repsponses I got:
[image: image]
https://cloud.githubusercontent.com/assets/9624753/19625505/dd636680-991a-11e6-84bf-5814d3eff04d.png—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#336, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAOigO_7Ns6yIiDcX7pIkBDzmLuUJrTAks5q2zW0gaJpZM4KeGNe
.
The examples don't all have an api-key property, this does not really comply with the fact that the API-key is required when including a google-maps element. I think the examples should represent the current situation, should they not?
So far, it's only throwing a coupe of warnings, but working fine, isn't it on your side?
It is working fine, just something that will be unexpected to new users. Nothing big.
The demo links on https://www.webcomponents.org/element/GoogleWebComponents/google-map are not working because of this.
The message in the modal is : Oops! Something went wrong. This page didn't load Google Maps correctly. See the JavaScript console for technical details.
And in the console : Google Maps API error: MissingKeyMapError
This is not for the example in readme.md, but for the Demo links on the left hand side, under Elements