I'm having the same issue with the GMap3 API in FF 3.5.5 (appears to be working Safari)
http://aialosangeles.org/ Can anyone investigate this? -j.j. On Dec 1, 7:54 am, bratliff <[email protected]> wrote: > The group interface is clobbering URLs. The following link is an > example: > > www.polyarc.us/sparse > > Tile server reliability seems to have deteriorated recently. Some > tiles never arrive. Switching from/to the same zoom level does not > force reloading. Examining the DOM, the tile slot contains a > "transparent.png" place holder rather than an actual tile image. The > only way to load the tile is to reload the application. > > Perhaps the optimizer is being a bit too clever. If the API thinks > the tile is already loaded, it will not attempt to load it again. > Well, I believe it is a horrible idea. If the tile is already loaded, > it will be served quickly enough from the browser cache. If the tile > never arrived, it ought to be requested again. Every zoom change > ought to reload every tile. A slight delay is preferrable to an > incomplete map. > > It is unclear why "transparent.png" is even being used. If it is to > disguise progressive rendering, it can be achieved in the onload/ > onerror event handlers with "this.style.display" or > "this.style.visibility". The use of a "background-image" is another > option. > > A "watchdog" thread might improve reliability. Periodically, it could > look for lazy tiles. If a tile has exceeded a resonable waiting > period, the request could be reissued. > > this.src=this.src; > > will do the trick. -- 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.
