I've run into a number of frustrations with the layout and functionality of the informational bubbles that are generated by the <description> tag in KML when overlayed on an embedded Google Map using GGeoXml.
1. Google strips out all classes, which makes it harder for me to format the text in the bubble. For example, <a class="MyClass">Click me</a> becomes <a>Click me</a>. I can get around this by targeting "div.MapContainer a" instead of "a.MyClass" in my CSS, but it's inexplicable to me why Google needs to remove the class. 2. Google wraps the whole thing in hard-coded styles, for example <div style="font-family: Arial,sans-serif; font-size: small;">. This makes it harder - although, again, not impossible - for me to control the formatting inside these bubbles. 3. Google adds target=_blank to all links. Why not just leave the KML in the HTML alone? So the author of the KML can say <a target=_top> or <a target=_blank> or just <a> . In my application I want the user to stay on the same page, and I'm having to contemplate all sorts of Javascript trickery to override the default behavior. In general, why doesn't Google just let the HTML specified in the KML through as is? I'm embedding this on my site, so why not let me format this the way I need it? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
