I've just created a much simpler illustration of the problem: http://myplace.walthamforest.gov.uk/chrome/pentagon.htm. I'm convinced now that this is a bug, because in this example I lifted the KML directly from http://code.google.com/apis/kml/documentation/kml_tut.html and just added a PolyStyle element.
I just assumed VML because the API documentation makes you add the XML namespace for VML to your HTML tag. Whatever part of WebKit is causing the problem, I hope they fix it quickly! -William On Oct 6, 9:54 am, chrismarx <[EMAIL PROTECTED]> wrote: > yup, definitely looks different in chrome, firefox displays as you > said, although, I think its a problem with the way webkit is handling > the canvas rendering, since that's what it uses, not svg or vml- > > On Oct 6, 4:18 am, wwarby <[EMAIL PROTECTED]> wrote: > > > I was just testing a Google Maps application I'm writing for cross- > > browser compatibility when I noticed this very uncool rendering > > problem in WebKit > > browsers:http://myplace.walthamforest.gov.uk/chrome/bug.htm. > > > It's a KML layer with two polygons, both have an innerBoundary and > > outerBoundary to create a cut-out effect. The idea is to dim the area > > outside my London borough, and dim the area outside London even more > > to focus the user's attention on our borough. IE, Firefox and Opera do > > what I expect with the KML layer, only Chrome and Safari fail by > > filling the cutout with the style of the outer region, so if it's a > > bug, it's obviously in WebKit's handling of VML. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
