Hi Esa, You are right using a string instead of a number can also do the trick. However I was hesitant to go this route as it was not described in the documentation.
So maybe the docucmentation needs to be updated? Looks like it was the 4/14 API update that brought this issue up as they reconfigured the polys to render with the canvas element. http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/6310d4992ce4b2ab -Lawrence. On Apr 26, 5:07 am, Esa <[email protected]> wrote: > Just noticed that there is a conflict between documentation and the > JavaScript warning that is thrown. > > Documentation states data type "number" for fillOpacity, > strokeOpacity, strokeWeight and zIndex. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. 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.
