The page itself is rather complex but of course if the experts out there can't help very much without the actual source code then I'll attempt to post a page which reproduces the problem but without extraneous complexity. I was rather hoping that this might be a 'well known' problem to which somebody would have an easy answer. I did read the posting guidelines but thought I'd try something simple before diverting more hours to going the route of reproducing the problem. My apologies. By the way, since my original posting we have at least determined that the Invalid Argument exception is only raised if we load the latest-and-greatest API (i.e. perform the load specifying only the major version) -- if we simply change our code to load version 3.1 of the API then the exception is not raised and the page works as expected (but the exception occurs if we specify 3.2). This isn't yet production code which is why we're not yet following the API documentation guideline to always specify the minor version when loading the API. Since we were working on other areas of the application (and hadn't noticed that there had been a new release of the API) we had assumed that the code changes we had been making broke the application. Hope this helps. BTW Rossko thanks for the prompt response.
-- 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.
