A link to your map would help us to help you. On Jun 12, 2:54 am, Pat <[email protected]> wrote: > Actually, it happens in the V2 api as well. > > I am absolutely flummoxed after several days of trying to figure this > out. > > My app was working well, or so I thought, on V2. I do most of my > development in Firefox and try it every so often in IE. A few days > ago I tried IE and started getting the bug. > > I concurrently made the decision to port the app to V3, initially > guessing that the problem had to do with the deprecation of V2 ... > that perhaps the developers were prodding us (me) to move up to V3 by > virtue of the fact of bugs in V2. > > OK, I could go with that ... > > But then after porting the app (had to port elabels.js, and write my > own polydecoder since all my lines are stored encoded and V3 no longer > has any fromEncoded methods), the problem still occurred. > > So I spent a half day or so of going thru the Internet Explorer > Options over and over, along with clearing the Temporary Internet > Files and Temp folders uncounted times, and pressing ctrl-F5 like a > silly fool all to no avail. I wrote a completely stripped down html > file with minimal embedded javascript that just creates a simple map, > and the problem still occurs. > > No matter what I do I get this Invalid Character %7b message, or some > similar variant of it in IE8. > > ------------------------------------------- > > Message: Invalid character > Line: 1 > Char: 1 > Code: 0 > URI:http://maps.gstatic.com/cat_js/intl/en_ALL/mapfiles/246b/maps2/%7Bmod... > > ------------------------------------------- > > To top it off, it also happens when I try any of the V2 or V3 samples, > and the piece de-resistance, when I simply go tohttp://maps.google.com/ > > I am beginning to wonder if it has something to do with google maps > localization and distributed serving. FWIW, I happen to be in the > Republic of Panama, somewhere near IP address 216.113.194.129, and > not, for instance, in San Jose. > > Anyway, it seems to me that it shouldn't be this difficult. I don't > believe I have changed anything in IE's configuration that should > affect this. As a naive user I would expect google maps to work > robustly with the current release of the #2 (or is it #1 lol) brower, > and as a developer I would expect there to be some way to diagnose and/ > or correct the problem. > > --------------------------------------------------- > > In closing I'm gonna post this to the V3 group as well. And sorry > about my earlier post of the port of Elables to V3 ... I realized > right after I pressed the button that it did not belong in this group. > > Thanks, > - Pat
-- 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.
