>Aha. So Google produce invalid HTML when more than one map is on the >page. That's Issue 1312 which will need to be reopened. >http://code.google.com/p/gmaps-api-issues/issues/detail?id=1312
There's only one map on the page; that link to the example was with and without the js changes, just to clarify my reasoning for the proposed suggestions. >(It's an id, not a class; and CSS shouldn't have upper-case like that, but >never mind) . Yep, Id! That's what I said! :P I'm thinking MS are not planning to use case sensitivity in any of their future browsers, as I'm using Visual Studios which has the default formatter of UPPER-CASING the styles element. Thanks for the tip there! > Bear in mind too that it wouldn't take much to break your > implementation. The logo should not have an id, and the Terms link can > be moved within the DOM at will (with every release, if necessary). Your quite right about the fragile state of the code, and I'll take that into consideration. I didn't know that the logo wasn't suppose to have an id either... Bad Google! :) Well, I'll try convince the boss well be in breach of terms, and to heed such warning for the sake of keeping the more important mapping service. Tough! Thanks for your help on this one Andrew Shaun
-- You received this message because you are subscribed to the Google Groups "Google Maps API" 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-api?hl=en.
