On Dec 28, 6:52 pm, metadings <[email protected]> wrote: > After some coding to fall ill i found out, that IE appends an > undefined item to an array, where as Firefox does not: > > Has a last 'undefined' array item (in IE): > > var points = [ > new latlng(1, 2), > new latlng(2, 3), > ]; > > Does it fine: > > var points = [ > new latlng(1, 2), > new latlng(2, 3) > ]; > > This caused IE not to like my script. It's not googles mistake, but > you could catch undefined/nulls...
That is actually a common problem with maps (and most applications) in IE. I don't know that extra overhead in the API to fix a problem that only happens in IE would be worth it, particularly since it is easy to fix. -- Larry > > Happy new year! > > On 27 Dez., 00:46, Andrew Leach <[email protected]> wrote: > > > > > > > > > 2010/12/26 metadings <[email protected]>: > > > > Details zum Fehler auf der Webseite > > > > Benutzer-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; > > > Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR > > > 3.5.30729; .NET4.0C; .NET4.0E) > > > Zeitstempel: Sun, 26 Dec 2010 14:29:26 UTC > > > > Meldung: 'undefined' ist Null oder kein Objekt > > > Something is not defined when the API needs it. > > > Please follow the posting guidelines and give a link to your map. You > > might check that all your variables are in the correct scope (for > > example, that "map" is not local to your initializing function). -- 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.
