-
Notifications
You must be signed in to change notification settings - Fork 256
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
google-map-marker content does not update in dom-repeat #263
Comments
I believe this is related to #168. Namely, data binding does not work properly in the marker's info window. That's because, currently, the info window uses the imperative Maps API to create it. Changes after the first setup are not detected. |
I had the same issue... the info window doesn't render properly when use a filter on a dom-repeat my solution:
|
this might be related with pull 294? I am using that patch and it's working fine, so far |
I found the solution by simply adding the map = {{map}} property to the google-map and google-map-market elements |
I know this is unrelated but how did you guys make it so your map-marker locations would update. I currently have a polymer project where we want our map marker's to auto update their position every few seconds. we know it gets the new position correctly but doesn't visually update on the map. trying to use the marker's to track moving objects, and this has been our biggest hurdle |
@cbald24 you can do it with a |
Create some google-map-marker with content (infowindow) via dom-repeat template bounded to a data array. When the bound data changes, the position of all the markers are updated, but the contents are not.
I think this is because dom-repeat efficiently reuses existing doms. When google-map calls
_attachChildrenToMap
,child.map
could already be set to the current map. Since the value is not updated, google-map-marker's_mapChanged
and indirectly_contentChanged
method is never called.The MutationObserver attached in
_contentChanged
is also never fired because of this.Example
The text was updated successfully, but these errors were encountered: