Closed GoogleCodeExporter closed 9 years ago
Before you ask me to make an MCE, please let me know if the bad.kml file should
even trigger failedParse, by the parser's own design?
If it SHOULD... let me know and I can create an MCE.
Original comment by car...@bumpnetworks.com
on 8 Oct 2014 at 5:11
Reproduced in both branches. Looks like the error handling on the XML parser
failures has changed.
http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmztest_parseFail_linktoB.html
?filename=http://www.geocodezip.com/geoxml3_test/kml/bad.kml
http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmztest_parseFail_linktoB.html
?filename=http://www.geocodezip.com/geoxml3_test/kml/bad.kml
Original comment by geocodezip
on 10 Oct 2014 at 5:56
Cool, glad I helped catch this
Original comment by car...@bumpnetworks.com
on 11 Oct 2014 at 4:50
fixed polys branch revision #118
Original comment by geocodezip
on 23 Dec 2014 at 3:23
[deleted comment]
Test page for polys branch:
http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmltest_parseFail_linktoB.html
?filename=http://www.geocodezip.com/geoxml3_test/kml/bad.kml
Original comment by geocodezip
on 23 Dec 2014 at 4:19
fixed in kmz branch revision #121
test page for kmz branch:
http://www.geocodezip.com/geoxml3_test/v3_geoxml3_kmztest_parseFail_linktoB.html
?filename=http://www.geocodezip.com/geoxml3_test/kml/bad.kml
Original comment by geocodezip
on 23 Dec 2014 at 7:27
Original issue reported on code.google.com by
car...@bumpnetworks.com
on 8 Oct 2014 at 5:07