You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1.
Load multiple KML files (in my case 4 files of ~1.2 MB) using parse(urls:Array)
in Browser IE >= 7 or Firefox (No issue in Google Chrome)
2.
Problem: sometime you get an alert: log:Unable to retrieve file....
I tested this situation with both local links and network links to files. No
difference.
3.
Looks like XHR is breaking down or timeout, while reading/waiting for
ResponseXML. As I said, this happens only in IE and FF.
What is the expected output? What do you see instead?
No alert of file not found should be there.
What version of the product are you using? On what operating system?
Google Maps API v3, in IE 7 or 8, FF 3.6
Please provide any additional information below.
Also performance with multiple KML is not good in IE > 7.
Original issue reported on code.google.com by DeepBhar...@gmail.com on 11 Feb 2011 at 3:41
The text was updated successfully, but these errors were encountered:
1. Please provide a link to a map that exhibits the problem.
2. Please contact Microsoft regarding problems with IE.
What version of geoxml3 are you using? (trunk, network_link or polys)?
Original comment by geocodezip on 12 Feb 2011 at 3:51
potential example of issue:
http://www.geocodezip.com/geoxml3_test/v3_geoxml3_utah-hunt_linkto.html
Problem seems to be only one timeout. Will cause issues if more than one
xmlHttpRequest is sent.
Original comment by geocodezip on 19 Feb 2011 at 8:20
Thanks Larry, thank you very much. For IE, nothing can be done I suppose, I
used IE9 there it renders perfectly so it has nothing to do with geoxml3.
and kudos for this excellent work.
Regards,
SSA
Original comment by DeepBhar...@gmail.com on 20 Feb 2011 at 10:49
Original issue reported on code.google.com by
DeepBhar...@gmail.com
on 11 Feb 2011 at 3:41The text was updated successfully, but these errors were encountered: