GoogleWebComponents
Update google-map-market.html
Attempted to use the attribute 'hidden' in polymer 2 I check that it does not work, as in polymer 1. In Polymer 1 in this component you use the attribute 'hidden' and it is shown or hidden. When you use this component in Polymer 2 the hidden attribute is not working as in Polymer 1, it only works the first time. Adding a new attribute that I have called 'show' can control the visibility of the marker, and it works in both Polymer 1 and Polymer 2, because it keeps the use of the 'hidden' attribute for Polymer 1 and the new 'show' attribute for Polymer 1 and 2
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).
:memo: 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.
I signed it!El 2 ago. 2018 1:26, googlebot [email protected] escribió: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.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.