google-map-poly watches child elements

[nerdkid93]

google-map-poly watches the lat/lng properties of it's child elements for updated properties

[nerdkid93]

I've made these changes in my own bower install of google-maps, but it'd be nice to have them in the original repo to avoid overwriting our changes.

[nerdkid93]

Because I already fixed this in my own install, I didn't bother to create an issue for it. However, I should provide some explanation for this PR...

google-map-poly's MutationObserver only watches for new child elements to be added or removed from its content selector. I fixed this by making the observer watch not just additions and subtractions to its childList, but also attribute changes (specifically latitude and longitude). This means that the following code ($ needs to be included to map as attributes) will allow dynamic bindings where points can be moved around:

<google-map-poly>
  <google-map-point latitude$="{{p1.lat}}" longitude$="{{p1.lng}}"></google-map-point>
  <google-map-point latitude$="{{p2.lat}}" longitude$="{{p2.lng}}"></google-map-point>
</google-map-poly>

[nerdkid93]

Where is the GoogleWebComponent team?

[nerdkid93]

@e111077 Is anyone watching this project anymore?

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[e111077]

Heya GWC elements are maintained by individual googlers (not on the polymer team) that have decided to make and open source elements. It may be that they may have moved from their teams, left google, or simply forgot about these elements. The polymer team occasionally takes a look at these elements when it comes to huge breaking bugs.

I can take a look at this PR, but due to other work pulling me in the other direction right now, I won't be able to get to it this week.

In the meantime, you may be able to just fork the element, make changes and then bower install it from your release.

[e111077]

This is a great PR!

[e111077]

I just need you to resolve that CLA issue though