Prior to deployment, Google ought to check out every release on a slow dial-up connection. Preferrably not one with an ISP located just a few miles away. A five minute cursory test is not enough. Clear cache. Do a lot of dragging, panning , zooming & map type switching. You will see lost tiles. Once a tile is lost the API will never attempt to load it again. It is easy to detect. The DOM will contain "transparent.png" rather than real images. If at least one valid tile exists for a particular zoom level currently in view, you ought to assume the other tiles are just "lazy" rather than missing.
Also, please provide a mechanism to revert to a known stable version. I am not asking for access to every prior version just one good one. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
