33446 2010-01-09 21:51:56 -0800 REGRESSION(r52948): JavaScript exceptions thrown on Google Maps when getting directions for a second time 2010-01-15 12:51:00 -0800 1 1 1 Unclassified WebKit JavaScriptCore 528+ (Nightly build) PC OS X 10.6 RESOLVED DUPLICATE 31871 InRadar, NeedsReduction, Regression P1 Normal --- 1 mrowe webkit-unassigned ggaren oldest_to_newest 179118 0 mrowe 2010-01-09 21:51:56 -0800 Steps to reproduce: 1) Load <http://maps.google.co.nz/> and search for Auckland. 2) Click “Get Directions”. 3) Enter “Taupo” in to the empty field and press “Get Directions”. 4) Press “Get Directions” a second time. You’ll notice after step three that directions are displayed. After step four the directions will no longer be visible and the yellow “Loading…” indicator will remain at the top of the screen. 179119 1 mrowe 2010-01-09 21:52:26 -0800 <rdar://problem/7527346> 179120 2 mrowe 2010-01-09 21:53:45 -0800 I should probably mention the JavaScript exception that I see logged in the console: TypeError: Result of expression 'a.lng' [undefined] is not a function. (main.js:709) 179653 3 ggaren 2010-01-11 18:57:19 -0800 This bug seems to be reproducible getting directions on any google maps property going from anywhere to anywhere. Another symptom is that the blue line of travel never shows up on the map. 179654 4 ggaren 2010-01-11 19:00:25 -0800 Shorter steps to reproduce: Load this URL: http://maps.google.com/maps?f=d&hl=en&geocode=&saddr=cupertino&daddr=berkeley. 181329 5 ggaren 2010-01-15 12:50:38 -0800 Committed r53341: <http://trac.webkit.org/changeset/53341> 181330 6 ggaren 2010-01-15 12:51:00 -0800 *** This bug has been marked as a duplicate of bug 31871 ***