-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
intended purpose of google-maps-api? #85
Comments
After looking more into the google-maps-api web component using Polymer 2.0, I have gotten it to work rather well. I am able to display e.g. markers, polylines and ground overlays. I am including the custom-element that I worked on, in case this might be useful to someone else wanting to do the same. Comments and suggestions are welcome.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am trying to understand the intended purpose of google-maps-api. There is only brief information shown on webcomponents.org.
I have made a first test using the google-maps-api web component with Polymer 2.0. I am able to display a map and a marker, but am encountering positioning issues and also need to refresh the screen several times to get an initial render. Maybe these issues are related to Polymer 2.0 or maybe I am using the google-maps-api for the wrong purpose? Are there any examples of using google-maps-api (aside from the basic one on webcomponents.org)?
I have tested the google-maps web components for basic functionality and this works fine for me. However I need additional functionality of the google maps api, which isn't available in the google maps web component.
The text was updated successfully, but these errors were encountered: