Bug 13950

Summary: REGRESSION: Embedded Google Maps overlay does not work
Product: WebKit Reporter: Antti Koivisto <koivisto>
Component: EvangelismAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: abob, ap
Priority: P1 Keywords: GoogleBug, InRadar, NeedsReduction, Regression
Version: 523.x (Safari 3)   
Hardware: Mac   
OS: OS X 10.4   
URL: http://www.fifi-wifi.fi/foo/?pg=map
Attachments:
Description Flags
test case for comment problem none

Antti Koivisto
Reported 2007-05-31 07:15:26 PDT
Overlay showing WiFi coverage is missing. Works fine with Tiger WebKit.
Attachments
test case for comment problem (170 bytes, text/html)
2007-07-11 15:57 PDT, Antti Koivisto 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Antti Koivisto
Comment 1 2007-05-31 07:17:45 PDT
<rdar://problem/5239689>
mitz
Comment 2 2007-05-31 09:18:28 PDT
Are you sure this has nothing to do with the JS exceptions showing up in the console?
Antti Koivisto
Comment 3 2007-05-31 15:09:35 PDT
I didn't notice those. Could well be.
Antti Koivisto
Comment 4 2007-07-11 15:17:27 PDT
A major problem here is that the page has a comment as the first child of html : <html><!--comment--><head> Google maps script does document.documentElement.firstChild and expects to find the head. This works in Firefox as it reparents all comments before body to head but fails in ToT where the comment is kept as a child of html. Fixing this gets rid of exceptions and makes the overlay work when clicking enable/disable button. There is some other problem besides this as the overlay still does not show up on first page load.
Antti Koivisto
Comment 5 2007-07-11 15:57:44 PDT
Created attachment 15481 [details] test case for comment problem WebKit behavior here does match the current HTML5 draft parsing rules though it does not match either Firefox or IE.
Adele Peterson
Comment 6 2007-08-30 14:48:57 PDT
<rdar://problem/5344233> is tracking this as an Evangelism problem that Google is aware of.
Alexey Proskuryakov
Comment 7 2007-12-14 13:08:54 PST
Fixed by Google.
Note You need to log in before you can comment on or make changes to this bug.