Hi Michael - Thank you, *that* explains the different behavior we've seen between the official sample and our self-hosted sample.
When you say to put my page into IE9 compatibility view, I assume you mean by adding a meta tag (ie <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />)? If I'm understanding correctly, this mimics the IE8 rendering of the page and removes access to some of the new features accessible in IE9. I'm reporting this issue in the hopes that the plan for the maps API is to support IE9 without having to handicap it into compatibility mode. Regardless, thanks for clearing up the differences issue! -- Adam On Mar 29, 12:37 pm, Michael Geary <[email protected]> wrote: > Reload the API example page with the F12 console window already open. You'll > see this message: > > HTML1200: google.com is on the Internet Explorer 9 Compatibility View List > ('C:\Users\(username)\AppData\Local\Microsoft\Internet > Explorer\IECompatData\iecompatdata.xml'). > marker-animations.html > > Then try setting your page to IE9 Compatibility View - now it will work > without error. > > -Mike > > > > > > > > On Tue, Mar 29, 2011 at 7:35 AM, adamkempa <[email protected]> wrote: > > Hi everyone, > > > Many of the IE9 issues I reported awhile back (http://goo.gl/iCUTj) > > have seemingly been fixed in the current version of the maps API > > (Thanks!). There is one remaining IE9-specific error we can recreate, > > so I've entered a bug in the tracker (http://goo.gl/Nq0HR), but there > > is one oddity we're still trying to clarify. > > > In the "markerAnimations" code sample, if a user left-clicks to pick > > up the marker, drags it off the edge of the map, and releases the > > mouse button, maps throws a JS error in IE9 ("Invalid calling object" > > inhttp://maps.gstatic.com/intl/en_us/mapfiles/api-3/4/7/main.js). > > > The odd part is that this doesn't happen on the "official" sample page > > (http://goo.gl/YGDWP) - it only happens when the sample is hosted > > elsewhere (example:http://goo.gl/ejX53). > > > The obvious explanation is that the "official" sample and external > > maps are hitting different versions of the API, but it seems > > counterintuitive that the samples wouldn't be representative of the > > experience users consulting them will have. > > > Thanks in advance for any details! > > > -- Adam > > > -- > > 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. -- 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.
