Issue 780 - gmaps-api-issues - Bug: Removed overview map causes checkResize to fail (Webkit/Safari)

Issue 780:	Bug: Removed overview map causes checkResize to fail (Webkit/Safari)
	2 people starred this issue and may be notified of changes.	Back to list

Status:	Fixed
Owner:	----
Closed:	Jan 2009
Type-Defect
ApiType-Javascript
Internal-1443516
Fixed-2.142

Reported by robert.coup, Oct 15, 2008

What steps will reproduce the problem? Please provide a link to a
demonstration page if at all possible, or attach code.
1. Add an overview map control to a map
2. Remove it
3. Call gmap.checkResize() and get a JS error

see demo at: http://rcoup.dojotoolkit.org/gmaps/overview_resize.html


What version of the API are you using?
(In the JS API, you can tell this by checking the value of G_API_VERSION.)

132d

What operating system and browser are you using?

Only seems to fail in Webkit-based browsers (Safari, Webkit, Chrome) on any OS.

May be related to:
http://code.google.com/p/gmaps-api-issues/issues/detail?id=521


*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************

Comment 1 by pamela.fox, Oct 20, 2008

Is it possible this bug was fixed in 2.133? I'm not seeing a JS bug anymore.

Comment 2 by robert.coup, Oct 20, 2008

Hi Pamela,  I'm still seeing the same error in Webkit & Safari (on OSX) with 133d.

Comment 3 by pamela.fox, Oct 20, 2008

Does the error show up in the JS Console in Safari? I'm honestly not too familiar 
with Safari debugging. 
Do you get it in Safari/Windows as well, or will I need a mac to replicate?

Comment 4 by robert.coup, Oct 20, 2008

Fails for me on Safari3.1/WinXP as well.

The basic error shows up in the GLog console in the test, but I used the script
debugger from a webkit nightly (http://nightly.webkit.org/) to figure out what's
noted on the test page.

The test page catches the error - comment out the try/catch blocks and it should
throw it all the way up to the browser error console.

Comment 5 by pamela.fox, Oct 21, 2008

Got it. Will report soon.

Comment 6 by pamela.fox, Oct 22, 2008

(No comment was entered for this change.)

Status: Accepted
Labels: Internal-1443516

Comment 7 by pamela.fox, Jan 07, 2009

(No comment was entered for this change.)

Status: FixedNotReleased

Comment 8 by pamela.fox, Jan 19, 2009

This is now fixed in 2.142

Status: Fixed
Labels: Fixed-2.142