My favorites | Sign in
Project Logo
             
New issue | Search
for
| Advanced search | Search tips
Issue 1479: Got an error popup on map click after a map resize with relative sizes in IE6-7-8
5 people starred this issue and may be notified of changes. Back to list
 
Reported by aradvert, Jul 15, 2009
Please, take a look into attached code. It creates a map with relative
sizes (width: 50%; height: 50%;). Run a page, resize the browser window
several times and click on the map surface. You will got an error popup in
IE6-IE7-IE8, but it is ok in FF3.


What version of the API are you using?
2.166. Tried also 2.148 and 2.156 with the same effect.


What operating system and browser are you using?
Windows XP SP2-SP3
IE6, IE7 and IE8 replicates an error, while FF3 does not.


*********************************************************
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.
*********************************************************

090715 IE7+_resizing_broken.html
1.5 KB   Download
Comment 1 by aradvert, Jul 15, 2009
Mmm... I can't understand what is happening. I've just tried to make a resizeable map
with no CSS pure JavaScript only and it also produces the same bug! The thing I can't
understand is I already have a production site with resizeable map and it works OK!
Looks like I'm doing something wrong, but I can't see what it is...
I would very appreciate any feedback. Also going to post to GMaps group.
Sorry if it is my fault.
Sincerely yours...
090715 resizing_broken.html
2.6 KB   Download
Comment 2 by aradvert, Jul 15, 2009
The problem seems to occurs deep inside a code, that does some job with map type
controls. Also, if I comment out map.setUIToDefault() method call, it works fine and
no error occurs.
I'll try to reproduce the problem with different map controls and will write results
here later.
Comment 3 by aradvert, Jul 15, 2009
Yep, it looks like the bug is because of old friend ;) map.setUIToDefault().

Changed that call to a set of equal (?) calls:

map.addMapType(G_PHYSICAL_MAP);        
map.addControl(new GLargeMapControl3D());
map.addControl(new GScaleControl());
map.addControl(new GMapTypeControl());

and it works fine now.
Comment 4 by d...@google.com, Jul 20, 2009
Thanks for updating this issue with your progress.

So it looks like the bug occurs when:
- using IE6, IE7, IE8
- setting map dimensions using relative sizes
- calling GMap2.setUIToDefault()

Is that correct?


I reproduced the bug on IE6, and I also noticed this error is thrown even when
GMap2.checkResize() isn't called.

This looks like a regression bug from 2.147 and 2.148 since the error doesn't exist
on 2.147.

Thanks for reporting this.  Can you confirm you're seeing the same?
Status: Confirmed
Labels: Internal-1992199 Regression-Yes Browser-IE6 Browser-IE7 Browser-IE8 Introduced-2.148
Comment 5 by aradvert, Jul 21, 2009
Yes, the bug occurs in IE6-7-8

Looks like the map dimenstions doesn't matter - I tried with relative sizes at first,
but after that I created purely JavaScript resize function to resize map canvas to
fixed size and it still produced the error.

The bug is directly related to GMap2.setUIToDefault(). If one replaces the call to
GMap2.setUIToDefault() to equvalent code, the error disappears. More exactly, the bug
appears somewhere deep in map type controls positioning code. I don't know why this
code works on a map click, but when I launch script debugger on the error, it shows a
code that plays with map type control's DIV and breaks on accessing its offsetTop
property.


Glad to be helpful :) I like Google Maps very much, thanks for your work! :)
Comment 6 by d...@google.com, Jul 22, 2009
(No comment was entered for this change.)
Status: FixedNotReleased
Comment 7 by pamela.fox, Jul 22, 2009
 Issue 1350  has been merged into this issue.
Comment 8 by d...@google.com, Jul 30, 2009
(No comment was entered for this change.)
Status: Fixed
Labels: Fixed-2.169
Comment 9 by pamela.fox, Aug 16, 2009
Issue 1556 has been merged into this issue.
Comment 10 by rnew...@thecia.net, Aug 16, 2009
Issue 1556 is also fixed, but it's not the same bug as this one, because 1556 happens on Firefox while 1479 is 
an IE-only problem.
Sign in to add a comment

Hosted by Google Code