This repository has been archived by the owner on Nov 30, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Polylines/Polygons not responding to visible/editable changes #1255
Comments
Confirmed |
Feel like writing a spec for this? That way it is caught in the future? |
I'm just getting started into mean stack dev/coffeescript so may take me a little bit to get up to speed. |
Np just asking for help as I am getting more active on other projects. |
I've also noticed that changes to the path property (setting it to a new array) doesn't seem to get picked up. |
Updated plnkr here http://plnkr.co/edit/Ar6kuqf7IQO1HSjoCZ7M?p=preview |
nmccready
added a commit
to nmccready/angular-google-maps
that referenced
this issue
Aug 17, 2015
correctly fixes issue angular-ui#1255
I am using the latest version (v2.3.2), and this issue seems to have reappeared for the |
Please re-open a new issue linking this one. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This bug appears to have been fixed in Issue #1059, but has regressed in version 2.0.17 forward.
I modified the plnkr from the previous issue to include one polyline and one polygon to toggle visibility.
http://plnkr.co/edit/Ar6kuqf7IQO1HSjoCZ7M?p=preview
The text was updated successfully, but these errors were encountered: