> Which cache are you referring to? Browser cache, that is the cache created and maintained by whatever web browser you are using. I'm only guessing, but the "works first time, fails second time" scenario strongly suggests your code works when search results are fetched (slowly) from a remote server, and fails when results come (quickly) from the cache.
> Is there a general solution for this? Yes, find the error and fix it. It's not easy; generally the code writer has made some assumption about the order that events will happen in, that doesn't always hold true. Much of the Maps API works asynchronously, which can often lead to such assumptions. Finding the assumption without a good understanding of what the code is supposed to do, will be difficult. As I said, I can't read your code and there is an awful lot of other stuff to trawl through that won't be relevant to this issue. It would help to identify the functions involved when the 'dealer search' is executed. It would help to simplfy out the other stuff for a test case. > May be setup a IE7 specific > timer before calling an API that could generate this error? If you like ; I'm not sure what you have in mind but there isn't a magic bullet. -- 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.
