Hi everyone- The error in GUnload in IE is now fixed in v2.77 (v=2.x), but is still there in v2.76 (v=2). This error will cause an alert for IE users with script debugging enabled.
If you are using v=2, the workarounds are: 1. Call a function that has a try/catch: try { GUnload() } catch(e) {} 2. Don't call GUnload
Otherwise, use v=2.x to avoid the error from occuring. I apologize for this inconvenience. In the future we'll try to get bugs like this fixed in the version they were introduced.
Thanks for the info. I have been racking my brains out wondering why my maps quit working today. I rely a lot on GUnload() because it helps me reset the default view of the map after zooming, etc.
<api.pamela...@google.com> wrote: > Hi everyone- > The error in GUnload in IE is now fixed in v2.77 (v=2.x), but is still > there in v2.76 (v=2). > This error will cause an alert for IE users with script debugging > enabled.
> If you are using v=2, the workarounds are: > 1. Call a function that has a try/catch: try { GUnload() } catch(e) > {} > 2. Don't call GUnload
> Otherwise, use v=2.x to avoid the error from occuring. > I apologize for this inconvenience. In the future we'll try to get > bugs like this fixed in the version they were introduced.
It's every two weeks, so 2.77 should become v=2 next Tuesday. The release cycle is both for the API and maps.google.com, so there's a lot of testing that goes on right now for maps.google.com functionality.
You can also explicitly ask for v=2.77 in your script tag, if you're wary of changing all your sites to always use the latest version.
Sorry for this inconvenience. - pamela
On Apr 10, 10:37 am, "heulman" <i...@creasit.com> wrote:
<api.pamela...@google.com> wrote: > It's every two weeks, so 2.77 should become v=2 next Tuesday. The > release cycle is both for the API and maps.google.com, so there's a > lot of testing that goes on right now for maps.google.com > functionality.
> You can also explicitly ask for v=2.77 in your script tag, if you're > wary of changing all your sites to always use the latest version.
> Sorry for this inconvenience. - pamela
> On Apr 10, 10:37 am, "heulman" <i...@creasit.com> wrote:
> > On 10 avr, 18:49, "iguana" <nelsonmonteir...@gmail.com> wrote:
> > > thanks for the help.
> > > the problem is that know i have to change 50 clients web sites because > > > of that change :-/
> > 2.77 seems to be ok (and a 2.78 exists too) > > so google is probably ready to make it default version
> We update the Google Maps API about every > two weeks, at which point features within the v=2.x release are > migrated into the stable v=2 release unless problems are discovered.
And sometimes even when problems are discovered...
<api.pamela...@google.com> wrote: > Hi everyone- > The error in GUnload in IE is now fixed in v2.77 (v=2.x), but is still > there in v2.76 (v=2). > This error will cause an alert for IE users with script debugging > enabled.
> If you are using v=2, the workarounds are: > 1. Call a function that has a try/catch: try { GUnload() } catch(e) > {} > 2. Don't call GUnload
> Otherwise, use v=2.x to avoid the error from occuring. > I apologize for this inconvenience. In the future we'll try to get > bugs like this fixed in the version they were introduced.
As of 10 minutes ago, 2.78 became v=2.x and 2.77 became v=2, so you should no longer have this issue with 2 or 2.x versions of the API. Please report back here if you still encounter any problems. Thanks!
On Apr 17, 6:33 am, jobo <jobo...@gmail.com> wrote:
