We have a v3-based setup, and it's used by a number of different parties on different hosts completely independent of each other. At some point tonight, everyone's installation went a little bit haywire. Since I doubt everyone managed to break their own html/js in the same way at the same time (and considering that most of these installations don't get touched at all) I'm wondering what might be up.
The only real oddity about our implementation is that our tiles are 384x384, instead of the normal 256x256. What appears to be happening is that the images are being assumed as 256x256 and thus the layout is getting borked. It looks like the last modified header on main.js was a few hours ago, which would coincide with what we're seeing. Here's a demonstration of the problem, with a debug layer turned on to show expected tile boundaries. Load up a tile on it's own to see that it is, in fact, 384x384. http://skylands.goonskins.com/SL_Overview/ Thanks in advance for any help on the issue. I don't know if it's a break in main.js, or if our code was assuming something it shouldn't have been, and that was recently altered, or what. :) -- 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.
