Bug 50832

Summary: iFrame window gets clipped when Google map pans
Product: WebKit Reporter: zac
Component: EvangelismAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Major CC: aestes, ap, jensimmons, simon.fraser
Priority: P2 Keywords: NeedsReduction
Version: 528+ (Nightly build)   
Hardware: Mac (Intel)   
OS: OS X 10.6   
URL: http://www.cottagesincanada.com/cottageretriever.asp?lang=e
Attachments:
Description Flags
screenshot none

zac
Reported 2010-12-10 10:59:45 PST
Greetings, I've tested this page on most browsers/OS setups including other webkit browsers such as Firefox and Chrome. All work as expected except for Safari (including the latest nightly build). The issue: When clicking on a marker on the Google Map, an InfoWindow pops up and is filled with an iFrame. Unfortunately, when the Google Map auto-pans to center the marker, Safari causes the iframe window to get clipped resulting in part of the iframe not being displayed. As you click more markers and the map pans further, the iFrame clipping increases. The iFrames display correctly IF the map does not pan. It's almost as if the iFrame is being treated with absolute positioning (but it isn't). If you bring up an infoWindow and see the clipping, you can drag the map to reveal the full iFrame if it is dragged into the area that the 1st iFrame was created. I tried disabling Autopan and this works as long as you don't drag the map which then results in the same issues as above. Strangely, this does not appear on my iPhone but does on all my versions of Safari and also on the iPad. Any ideas as to whether this is a documented bug and are there any workarounds? Thanks in advance and cheers, Zac
Attachments
screenshot (200.64 KB, image/png)
2010-12-11 23:36 PST, Alexey Proskuryakov
no flags
zac
Comment 1 2010-12-10 11:02:01 PST
Just discovered that I'm not the only one: http://code.google.com/p/gmaps-api-issues/issues/detail?id=2878
Alexey Proskuryakov
Comment 2 2010-12-11 23:36:30 PST
Created attachment 76314 [details] screenshot
Alexey Proskuryakov
Comment 3 2010-12-11 23:48:20 PST
Actually, this doesn't seem to be a WebKit bug. This site works fine if user agent is changed to Firefox via Develop menu, meaning that broken code is given to Safari specifically.
Note You need to log in before you can comment on or make changes to this bug.