In API v2.69 in Firefox.

The first four parameters control the border and are exactly the same as
for GPolyline, i.e.
        Array of GLatLngs
        Colour
        Weight
        Opacity
Then the next two parameters control the fill
        Fill colour in the format "#RRGGBB"
        Fill opacity, a number between 0 and 1.

If the Boundary Weight is zero or absent, then the boundary drawing
routine is not called.

If the Fill Colour is absent, then the fill drawing routine is not
called.

If either Opacity value is zero or absent, then a corresponding default
value is used.

The shape need not be closed.

If the boundary crosses itself, then the interior region is not filled.

It doesn't seem to work in MSIE6, and even GPolylines don't seem to work
in MSIE6 with v2.69. MSIE6 doesn't like the API line
        if(h.lat&&h.lng)
where h is one of the GLatLng()s in the input array, so h.lat is a
reference to the GLatLng.lat() method. MSIE complains that
        h.lat is null or not an object
I guess it's not an object, it's a method "function(){return this.Ph}.

--
The Blackpool Community Church Javascript Team
http://www.econym.demon.co.uk/googlemaps/

Works for me in FF 2.0, Opera 9.1 and MSIE 6, all on win2k.
If the boundary crosses itself, the inner region is filled.

frank aka dfd

Strange, with the IE-Tab-Extension in FF2 it doesn't do... With IE it
does.

...

"Arrived" as in you have noticed it in this version of the API, or is
there further info. to this announcement?  Is the Google team or
another party (you?) responsible for this addition?  Where can we look
for more?

Google is not doing a great job of updating the documentation for the
API, so Mike's heads up on new developments in the API is a great
source of news, but you will have to do some work yourself to find out
how it works. Even when v 2.69 becomes current it will take some time
before it gets referenced in the documentation and most certainly
longer before all methods and possibilities are documented.

If you want to read more about changes to the API read Mike's changelog
at www.mapki.com

Wasn't it ScienceMan who wrote:

I noticed it in the API code.

There's lots of undocumented stuff in the API. I've tried to mark all
the undocumented stuff in my unofficial reference. The markings may not
be 100% accurate - I've not checked to see if Google have changed their
documentation for a while.
http://www.econym.demon.co.uk/googlemaps/reference.htm

Sometimes Google document the new stuff when the version that contains
it becomes current. Sometimes they don't.

--
Google Map API Tutorial
http://www.econym.demon.co.uk/googlemaps/

Great discovery. Works perfect with SVG. See behaviour of a draggble
polygon:
http://esa.ilmari.googlepages.com/dragpolygon.htm

Win XP with IE7 does fine. Its just slower than Firefox. No
error-messages at all. By the way,
does anyone have a good link to a tutorial or knowlege how to draw own
shapes like
circles etc.? What do i have to do to add own VML and SVG tags to the
map? I had
problems with VML and  <DOCTYPE> definitions on my first tests, didn't
try SVG yet.

Stefan

Win XP with IE 6 is ok too. No bug around. Did you use a non MS patch
because of that VML exploit?

Yup. Good demo, Esa. It does work in IE6 (unpatched for VML).

Andrew