In case anyone is wondering it is the nonstandard function definition methods that seemed to cause the issue not the redundent parseFloats.
On Sep 23, 3:24 pm, Garthan <[EMAIL PROTECTED]> wrote: > I un nested your function defs. in jsontest and removed the uneeded > parseFloats > and it works just fine in all browsers... will post later if you > need... > > On Sep 23, 2:26 pm, Black Fog <[EMAIL PROTECTED]> wrote: > > > On 23 Sep., 21:16, marcelo <[EMAIL PROTECTED]> wrote: > > > > On Sep 23, 9:05 pm, Black Fog <[EMAIL PROTECTED]> wrote: > > > > Your polygons load fine, (even fast), with FF2. > > > fascinating. i updated to ff 3 and it is a desaster in that specific > > case (also google chrome). > > but thanks for checking out. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-API?hl=en -~----------~----~----~----~------~----~------~--~---
