Google Chrome is built around Webkit in a way that allows it to grab the latest version of Webkit from time to time, so new Webkit features and fixes get implemented automatically.
Adobe took a specific old version of the Webkit code and modified it to create AIR. New Webkit features and fixes only get implemented if the Adobe guys retrofit the changes to their code. When the Google API sees a browser identify itself as "Webkit", it assumes that it correctly supports <canvas>, but AIR is based on a version of Webkit that doesn't provide all the <canvas> features that Google Maps uses. In particular semitransparent polys. AIR allows the user to change its user agent string. If they edit it, replacing "Webkit" with "Firefox" then the API will use SVG instead of <canvas>, producing a better result. However, there's nothing you can do on your page that will produce this behaviour. -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
