On 30 January 2011 22:03, Derek Tonn <[email protected]> wrote:
>
> Also, FYI, I still haven't really seen where to remove "commas" (semi-
> colons?) from that bit of .js code we've been focusing on. If Andrew
> or ??? wants to get back to me/us to give me a bit better idea of what
> specific recommendations he is making, maybe I/we can get to the
> bottom of that IE7 issue as well.
As I said, a trailing comma in an object *introduces* a non-existent
property in IE. Other browsers handle it better.
This is fine:
{ "prop1":"value1", "prop2":"value2" }
This is not:
{ "prop1":"value1", "prop2":"value2", }
because IE is expecting a third property/value pair.
Recommendation: a closing brace must not be immediately preceded by a comma.
--
You received this message because you are subscribed to the Google Groups
"Google Maps API V2" 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.
