Is the path option of PolygonOptions a part of the public API? I don't see it in the API reference.
I came across of this same bug when migrating my map application from API version 3.3 to 3.4. I see that the bug has now been fixed in API version 3.5 but it still exists in API version 3.4. This is really troubling because on the one hand Google encourages to develop the map applications using the latest API version but makes it impossible because trivial regressions like this happen all the time (I mean, isn't an empty path like the first test case you come up when testing a polygon API). On the other hand using the released version of the API is not much better if bugs like this will not fixed in that API version. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/jjM51gJ2_egJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
