According to the docs, holes in polygons must be "wound in the opposite direction to the outer path."

The native version seems to be able to handle holes regardless of the winding of their coordinates: "A hole is specified in exactly the same way as the outline.",

Neither the web plugin nor the JS SDK handle the winding direction of the polygons/holes, so holes that are not correctly wound don't render correctly.

It's possible to detect the direction of a polygon; the web version could warn the user that their holes are wound in the opposite way of their corresponding polygon.

(At the very least, we should fix the example app so the holes added to polygons are reversed so they work on the web correctly.)

Expected results:

Actual results:

This has been observed in a yet-unpublished version of the google_maps_flutter_web package: 0.1.0+10, merged here.