I found Chrome's error console and this is their I'm receiving from extinfowindow.js :
Uncaught SyntaxError: Unexpected token < I searched the script for "<"s and commented out some that were in an error message (I found a similar problem in the Chrome group) but the error console is still giving me the same error. The only other "<"s are in increment and conditional statements. The infowindow will also still load correctly after a refresh and the error console does not give any errors. On Oct 16, 2:32 pm, robwurtsmith <[email protected]> wrote: > I wish Google Chrome had a javascript error console! > > On Oct 13, 9:35 pm, robwurtsmith <[email protected]> wrote: > > > Do you think I should create a function to test if extInfoWindow is > > active and have the map wait until it is, as described for a fix for > > GOverviewMapControl in the link you gave? > > > On Oct 13, 8:45 pm, Rossko <[email protected]> wrote: > > > > >http://thetestbed.comli.com/SKATEPARKBETA/s15.php > > > > Doesn't seem like its related, but it would be good practice to > > > explicitly declare 'map' and 'geocoder' as globals. > > > > This issue with modular code seems almost relevant, but shouldn't > > > apply with v=2 now > > > http://econym.org.uk/gmap/modularized.htm > > > I wonder if extinfowindow relies on some other modularised code? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
