By the way, I was able to track that down using the debugging tools built into Chrome (and filtering upward from there to WebKit). Firebug is awesome, but the debugging resources built into Chrome and its WebKit-based cousins have come a very long way and are, in fact, second to none. If you haven't given them a shot, I would highly recommend it. Here's a link to the IO 2011 session about them. I've watched it two or three times and picked up new tricks each time. Good stuff.
http://www.youtube.com/watch?v=N8SS-rUEZPg Jeremy R. Geerdes Generally Cool Guy Des Moines, IA For more information or a project quote: [email protected] If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church! On Jun 14, 2011, at 9:58 PM, Tony wrote: > Everything looks fine now, thanks a lot! > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps JavaScript API v3" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-maps-js-api-v3/-/CEWzzibA1MYJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
