title: "google is not defined" when using Google Maps V3 in Firefox remotely
body: <p>Here's my conundrum:
  I have a page that uses Google Maps V3 and jQuery. It all worked well locally in FF5, Chrome and Safari. </p>
  
  <p>Once I uploaded to a web site, I get a "google is not defined" error on the first line that I try to use a google object</p>
  
  <pre><code>var defaultLocation = new google.maps.LatLng(lat, lng);
  </code></pre>
  
  <p>It <strong>only occurs in FF</strong> and <strong>only occurs remotely</strong> (i.e., if I load the file into FF locally, it works well). Chrome and Safari seem to be working great regardless, as is my Android and iPod browsers.</p>
  
  <p>Here's what I tried so far:</p>
  
  <ol>
  <li>Moved <code>&lt;script type="text/javascript" src="http://maps.google.com/maps/api/js?sensor=false"&gt;&lt;/script&gt;</code> to top of the <code>&lt;head&gt;</code> section.</li>
  <li>Moved all content of <code>$(function() {...});</code> to a function called <code>initialize()</code> and added <code>&lt;body onload="initialize()"&gt;</code></li>
  <li>Played with scripts and css files order</li>
  <li>Pasted the URL <a href="http://maps.google.com/maps/api/js?sensor=false">http://maps.google.com/maps/api/js?sensor=false</a> into FF address box and verified I'm getting the legit script</li>
  </ol>
  
  <p>But since this is only happening in FF on a remote machine and works well otherwise, I don't think it has anything to do with my code. Maybe the load order in FF5 is screwed. Maybe it prioritizes network resources differently than other browsers. I really do not know what to make of it at this point.</p>
  
  <p>Any help is appreciated.<br>
  Guy</p>
  
  <p><strong>Update:</strong><br>
  Just wanted to add the following fact: After trying the previous on a Mac, I tried FF5 in Windows, and have replicated the exact same behavior.<br>
  For good measure, I tried Pale Moon as well - same results. Chrome 14, Opera 11.50 and even frickin' IE9 (which wasn't included in the test plan) work. It just FF5, now on both Mac and Windows 7, that fails on that page.  </p>